Question Locked

(Yet another) Server 2003 RDP failure question

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

A possible twist in the tale here.

Server 2003 SP2. Symantec Endpoint 11. Sitting behind a Netgear WNR3500 router.

Remote desktop is enabled on the server and port 3389 is forwarded on the router.

Problem: Until a week or so ago I was able to RDP to my server from outside my network. Just recently my connections started to fail, with the familiar "The client could not connect to the remote computer" error.

The server appears to be listening on 3389 and I can connect using RDP from INSIDE MY NETWORK.

It is looking like a router issue. If I attempt to Telnet on 3389 (from outside my network) the connection fails.

The router is new and, as I said, has been working just fine until a week or so ago. There have not been any new firmware updates added to it and I haven't made any changes on the server side.

I tried restoring the router from a backup I made of the settings and rebooted it. Still no luck.

I had my Wife try to connect from her corporate network, just in case my company is filtering RDP. She couldn't connect either.

Before I do a 30-30-30 reset on the router is there anything else I should consider/look at ?

Thanks in advance.

5 replies

by techgeekone

I have a similar setup and it works for me on a Linksys router. I use the 'Applications & Games' section and added a port range forwarding for port 3389 TCP to forward to my PC (an internal PC--i.e. 192.168.1.100). Application Name 'RDP'.

When I need to connect (with MSTSC/RDC client) remotely I use the public IP assigned to my router, which I check before leaving home. ;-)

Hope this helps.

by techgeekone

btw, it's possible your corporate network is blocking RDP outbound. you might want to check that.

by thelizardbloke

Hi,

Thanks for your reply.

I can confirm that port forwarding is enabled correctly on the router, as it had previously worked using the same settings.

It's possible our IT folks are blocking RDP outbound, so I had my Wife try through her company network (she works for a comms company, so they have a lot of allowed protocols for testing. She got the same error.

I had a chance to run a few port scanners earlier on and they confirm that 3389 is open on the router ???

So, it would seem that the router may be in a 'limbo' state where 3389 is open but not forwarding.

I know the server is listening and RDP is working because I can RDP to it from inside my network just fine.

One thing I just thought of that may be related. I had a Lingo VoIP ATA that used to sit in front of my router. I recently brought it inside the firewall and put it in the DMZ. RDP used to work just fine when it was in front of the router. Is there any reason it would start filtering things once inside the firewall ?

Cheers.

by thelizardbloke

Well, it was a router issue. Last night I did a 30-30-30 reset on the router, restored from my backup settings and everything is now working just as it did previously.

In case anyone else has these issues, I found a review posted for this router that states "When the router does an automatic update (firmware) it breaks the network connection. Not completely, but you'll start to experience network errors. I had to reboot to fix this."

For me, a reboot didn't do the job but the 30-30-30 worked just fine.

Hope this helps someone

This discussion is closed to new replies.