Remote Desktop

[NewsTips]

I am attempting to do remote desktop on a new LAN. We are using these tp-link Widi WAPs. I was able to get them to work on a Spectrum LAN. Its a Windows 10 machine talking top a Windows 10 laptop. The lan address are 192.168.68.132 and the other is 192.168.132.116. So this is a LAN. The machines have no problem talking to a wireless HP Printer n this same LAN

Anyone know of any good outside Forums to get help with these kinds of problems as a substitute for an on -call IT pro?

 

[comfortably_numb]

Are you wanting to use the native Windows Remote Desktop between the two Windows machines?

If you're not married to that, Chrome Remote Desktop works well.

 

[b4pjoe]

Are these the actual lan address for each or is there a typo as they are presently on 2 different subnets? 192.168.68.132 and 192.168.132.116

 

[NewsTips]

Are these the actual lan address for each or is there a typo as they are presently on 2 different subnets? 192.168.68.132 and 192.168.132.116

TYPO
192.168.68.132 and the other is 192.168.68.116 Sorry
Never seen that 3rd octet so high but its still in the LAN range I think

 

[NewsTips]

Are you wanting to use the native Windows Remote Desktop between the two Windows machines?

If you're not married to that, Chrome Remote Desktop works well.

YES Native. I don't get it..worked before.

 

[NewsTips]

I am attempting to do remote desktop on a new LAN. We are using these tp-link Widi WAPs. I was able to get them to work on a Spectrum LAN. Its a Windows 10 machine talking top a Windows 10 laptop. The lan address are 192.168.68.132 and the other is 192.168.132.116. So this is a LAN. The machines have no problem talking to a wireless HP Printer n this same LAN

Anyone know of any good outside Forums to get help with these kinds of problems as a substitute for an on -call IT pro?

Yeah wow theres a LOT of typos in my post.

I am attempting to do remote desktop on a new LAN. We are using these tp-link Wifi mesh WAPs. I was able to get these Windows PCs to work on a Spectrum LAN. It is a Windows 10 machine talking to a Windows 10 laptop. The LAN addresses are 192.168.68.132 and the other is 192.168.68.116. The machines have no problem talking to a wireless HP Printer on this same LAN.

I think the airwaves are different here in W. Michigan.

 

[Pepper]

Pro or better required for native RDP in Windows.
Firewall rules might be getting in the way, do you have remote enabled?

 

[harshness]

I am attempting to do remote desktop on a new LAN. We are using these tp-link Widi WAPs. I was able to get them to work on a Spectrum LAN. Its a Windows 10 machine talking top a Windows 10 laptop. The lan address are 192.168.68.132 and the other is 192.168.132.116. So this is a LAN. The machines have no problem talking to a wireless HP Printer n this same LAN

Most DHCP servers aren't set up to give that broad a subnet. 192.168.68.x/24 simply can't talk to 192.168.132.x/24.

I'd suggest using something like Tailscale or Netbird to create an "overlay network" (get them VPNed together). This would give some control over who can traverse the subnets.

The other solution would be to turn all of the WAPs into wireless bridges so that everything is on the same subnet.

Then again, real mesh networks are getting cheaper by the quarter and don't require all this fussing, fiddling and network design background.

 

[Foxbat]

I noticed that the old “new” Remote Desktop App has been renamed to Windows and uses the light blue Windows logo instead of the orange overlapping >< icon.

I’m with Pepper and think it could be a firewall or version issue. Of course, I’m out of the Windows game so it could be something entirely different. Microsoft had locked down RDP some time ago, so checking that the Remote Desktop is enabled on the target is one thing to check.

The other is whether your computers identify your LAN as Private or Public. Public networks are hardened against outside access, so maybe the first question to ask is can you PING the laptop from the desktop. Since you said you have a new network, check to see it isn’t characterized as Public.

 

[harshness]

I’m with Pepper and think it could be a firewall or version issue.

It isn't a firewall or even a Windows issue. It is uniquely a subnet issue created by having multiple DHCP servers.

A WAP running in WAP mode (or a router running in router mode) must serve up a subnet that isn't the same as the one it is getting its DHCP assignment from.

 

[Foxbat]

It isn't a firewall or even a Windows issue. It is uniquely a subnet issue created by having multiple DHCP servers.

Read his later posts. Both nodes are in the same 192.168.68.0/24 subnet.

 

[comfortably_numb]

Most DHCP servers aren't set up to give that broad a subnet. 192.168.68.x/24 simply can't talk to 192.168.132.x/24.

They're on the same subnet.. his first post was a typo

 

[harshness]

Read his later posts. Both nodes are in the same 192.168.68.0/24 subnet.

Ah, that's a pretty gross error that I missed the correction to.

RDP is typically punched through the Windows firewall upon its installation (which can happen by add/remove Windows features or enabling remote access) but it wouldn't hurt to check (it will be mentioned by name).

Also notable is that there must be a Windows password (or equivalent Microsoft account) on the destination machine and remote access must be explicitly enabled in the settings.