I recently got a BT connection so replaced by netgear with homehub 4. Everything seems to be fine and my home network is connected. I have a PC on LAN and a couple of other laptops on wifi. There is a remote desktop enabled on LAN PC and I used to access that through my laptops connected via wifi. But since connected via homehub I can no longer access the LAN PC through remote connection. I can access shared drives etc but not RDP. I have tried disabling all firewalls etc, DMZ, uPNP, even 5GHz wifi but did not help. (I am having similar issue using xbmc/kodi remote (KORE) Any advices would help.
NOTE: This is not RDP access via internet rather internal on home network
There should be nothing to stop wired and wireless devices connecting. Any traffic between them should not even touch the firewall on the router.
When you have a laptop on WiFi can you ping the IP address of the wired PC? The other tool you could try is psping which, rather than ICMP, can "ping" an IP address but on a specific TCP port. For Microsoft RDP that would be port 3389 as shown below.
C:\Users\smf22>psping 192.168.1.89 3389 PsPing v2.01 - PsPing - ping, latency, bandwidth measurement utility Copyright (C) 2012-2014 Mark Russinovich Sysinternals - www.sysinternals.com Pinging 192.168.1.89 with 32 bytes of data: 5 iterations (warmup 1) ping test: Reply from 192.168.1.89: 2.65ms Reply from 192.168.1.89: 1.46ms Reply from 192.168.1.89: 6.47ms Reply from 192.168.1.89: 1.40ms Reply from 192.168.1.89: 1.41ms Ping statistics for 192.168.1.89: Sent = 4, Received = 4, Lost = 0 (0% loss), Minimum = 1.40ms, Maximum = 6.47ms, Average = 2.68ms
If the laptops have an Ethernet NIC can you connect that to one of the yellow LAN ports on the Home Hub and try both ping and RDP?
Have tried using ps ping and it fails for RDC port (or any other port actually except 80, tried smtp 25 and ftp), both on Ethernet and LAN. Correction to original post, I cannot RDP LAN to LAN either.
You check the "open" ports on the Windows PC with the netstat command as follows:
C:\Users\smf22>netstat -a | find "LISTEN" TCP 0.0.0.0:135 win71:0 LISTENING TCP 0.0.0.0:445 win71:0 LISTENING TCP 0.0.0.0:554 win71:0 LISTENING TCP 0.0.0.0:2869 win71:0 LISTENING TCP 0.0.0.0:3389 win71:0 LISTENING [..]
You should then be able to use psping to any of the ports shown e.g., 135, 445, 554, 2869 and 3389. Your PC may be listening on different ports.
You don't say whether just a simple ping worked, but it sounds as if psping to port 80 worked. Is the Windows PC still running the Remote Desktop?