Unable to RDP or Map a drive to a wireless PC in different subnet, but same domain.
Unable to RDP or Map a drive to a wireless connected Windows 7 PC in different subnet, but same domain. Following are things I have done attempting to fix this problem: 1. Confirmed RDP was enabled on the PC firewall (port 3389 for RDP and 445 for mapping drive). 2. Confirmed DNS on the domain controller reflected the correct IP in the SRV record for this PC. 3. Enabled GPO: “allow inbound Remote Desktop exceptions for IP: 192.168.0.141/24. 4. Executed “gpupdate /force. The user and computer policy update completed successfully. 5. I'm able to Map to a drive share and RDP from the wireless Windows 7 PC to other domain PC's without problem. In advance, any and all help with this problem will be appreciated.
April 5th, 2011 3:22pm

Back to basics. Can you ping the PC you are hoping to RDP to from a PC in the different subnet? Can you ping the PC you are hoping to RDP to from another PC in the same subnet? What device is routing between subnets? Is this device allowing traffic between subnets on the desired ports? It may be useful for you to provide a copy of your routing tables from the source and destination PCs, and also your routing device if you are unable to ping.Alan Moseley
Free Windows Admin Tool Kit Click here and download it now
April 7th, 2011 6:03am

Alan, thank you for your reply. I’ve been delayed responding trying to figure-out how to navigate this site and add screen prints as an attachment. The screen prints were visuals of selective desktop routing tables. I have not figured it out yet so I’m responding with text only. The computer with the named (Windows7-3) is the wireless PC in subnet (192.168.0). Windows7-3 is the problem computer that I’m unable to RDP or map to drive shares on this device. Windows7-3 is the only computer in subnet (192.168.0). This computer connects to a wireless router (Cisco E2000). In addition to the desktop routing tables there is a routing table entry in the router setup web page that I had attempted to attached to my reply. From the command prompt on (Windows7-3) I can ping it's localhost, NetBIOS,IP and FQDN. All other devices in the domain as an example (Windows7-1) desktop are in subnet (192.168.1). I'm able to ping from the wireless computer to devices in subnet (192.168.1). I also have internet connectivity from the wireless computer, I can RDP, and map to drive shares from the wireless to all other computers in subnet (192.168.1). Again, the wireless computer is the problem, I'm unable to ping it from subnet (192.168.1). If you know of a way I can send the screen prints of the routing tables would you let me know? Thanks, again for your help. Aubrey
April 11th, 2011 2:21pm

The wireless router you have will, by default, be blocking traffic originating from the the 192.168.1.x subnet, this is one of the main jobs that a router is supposed to perform. Are you able to disable the firewall function of this device? I guess the router has both a 192.168.0.x address and a 192.168.1.x address. If you are unable to disable the router firewall you could setup port forwarding on it and forward port 1723 to the 192.168.1.y address of the wireless PC, then when you need to RDP to it you would use the 192.168.1.x address of the router in place of the wireless PC's address. Why are you using a router to connect this wireless PC to your main network? I would suggest that you actually need an access point to perform this task unless you are specifically needing to keep the wireless computer on a separate subnet for some reason.Alan Moseley
Free Windows Admin Tool Kit Click here and download it now
April 14th, 2011 7:17am

Alan, thanks again for your help. Your port forwarding suggestion on the wireless router fixed both access problems (RDP and Drive mapping to folder shares) on the wireless computer in a different subnet. The point you raised about an access point verses wireless router was an excellent point. I had not even contemplated that approach, and it seems that would have been a less complicated solution in my case in retrospect. Thank you for all your help with this issue. We can conclude that issue is resolved. Aubrey
April 14th, 2011 2:44pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics