I'm having trouble with my remote desktop since I moved into a new house and I don't know where else to turn. I'm running CenturyLink and I first tried it with the Actiontec Q1000 modem/router combination. I set up port forwarding to both of the computers I use for RDP. One is set for port 3389 and the other for port 3390. Remote Desktop worked over the LAN, but would not work over WAN. Tried turning UPnP off, modem firewall off, even tried setting one of the computers in DMZ mode which wouldn't work either. ISP isn't blocking the port as www.canyouseeme.com was able to see both of them.
So after I couldn't get that modem router to work I went out and bought a Belkin N600 straight up router. I set the modem into bridge mode and hooked up the router to that. Confirmed local computer IP's through both DHCP and Ipconfig and forwarded the correct ports to the correct IP. Turned off router firewall. (Windows Firewall has been off this whole time as well). Restored both modem and router to factory settings and started over. Still would not work. Tried turning off UPnP again. Power cycled modem and router and restarted computers. Turned off port forwarding and set a computer in DMZ. DMZ again wouldn't take effect.
So I'm out of ideas with this one. It worked fine before I moved, but there is something stopping it now and I have no idea what. Any ideas would be appreciated.
interesting issue. I know it may be a silly question but your computers aren't going into sleep mode are they? also where are you attempting to establish a rdc connection from? I would also try to specify the port number when entering your connection ip
No, I have sleep mode disabled. I've tried connecting to the 3389 computer from the 3390 computer over the WAN and vice versa. I've even remotely logged into a computer at work and then tried RDPing from that (different WAN that way). The 3390 has to have the port at the end since the RDP default is 3389: 35.535.214.234:3390 which fails or via LAN 192.168.2.2:3390 which works fine (From the 3389 computer). I've tried the 3389 both ways: 35.535.214.234:3389 and just straight 35.535.214.234. They both fail. 192.168.2.5 and 192.168.2.5:3389 works fine.
One interesting thing is that if I use the correct destination I get the "Could not connect" error immediately after hitting connect. If I use a gibberish IP it times out before saying it can't connect. So it's like it can hit the router fine, but the ports aren't being forwarded.