djaycee
asked on
Server 2003 RDP through Draytek NAT freezes
Hi all,
For some time I've been struggling with the following problem. This is my setup: Draytek Vigor 2820 with proper NAT setup, different port to internal port 3389 to a Terminal Server 2003. All is working great, remote users (max 8) can connect to it. DNS setup external so no IP address needed. All of a sudden no external connection is possible anymore. RDP sessions freezes, no connection can be made. If I connect locally, no problem, if I connect externally through a Lan to Lan connection (Draytek to Draytek) also no problem. But the moment I try to use the external connection through NAT, no connection possible. Sometimes it's just enough to reboot the Draytek router but other times I also have to reboot the server to establish a connection again. And even sometimes I just let it be and after a few hours, max a day, everything is working fine again.
Does anybody have any ideas?
Thx!
Hans
For some time I've been struggling with the following problem. This is my setup: Draytek Vigor 2820 with proper NAT setup, different port to internal port 3389 to a Terminal Server 2003. All is working great, remote users (max 8) can connect to it. DNS setup external so no IP address needed. All of a sudden no external connection is possible anymore. RDP sessions freezes, no connection can be made. If I connect locally, no problem, if I connect externally through a Lan to Lan connection (Draytek to Draytek) also no problem. But the moment I try to use the external connection through NAT, no connection possible. Sometimes it's just enough to reboot the Draytek router but other times I also have to reboot the server to establish a connection again. And even sometimes I just let it be and after a few hours, max a day, everything is working fine again.
Does anybody have any ideas?
Thx!
Hans
ASKER
Hi Netflo,
Thanks for your quick reply. The Draytek has the latest firmware and no limits are set.
Regards,
Hans
Thanks for your quick reply. The Draytek has the latest firmware and no limits are set.
Regards,
Hans
Can you perform a read only CHKDSK on your server, chances are it has found errors. When you get a maintenance window perform a CHKDSK /R to resolve those errors found. Can you also verify that your server hardware is fully up to date in accordance to vendor (HP/ Dell, etc) and Microsoft?
Be sure you have a full system backup before attempting the above!
Be sure you have a full system backup before attempting the above!
ASKER
Thx Netflo,
I think that everything is fine and up to date but I don't know for sure. I'm going to check that. It might take a while before I can answer because the first moment I can check this it will be friday... I'll let you know, thx.
Hans
I think that everything is fine and up to date but I don't know for sure. I'm going to check that. It might take a while before I can answer because the first moment I can check this it will be friday... I'll let you know, thx.
Hans
No problem, have a great new years.
Did you try to check if the RDP port listeners are working outside the network. Since RDP is working fine locally so there is no problem in RDP configuration. Its something in NAT configuration which may be causing the issue.
ASKER
Hi Ratnesh,
I did think about that but at first, everything is working fine and then all of a sudden it freezes. Only local connecions are possible and no more external. Sometimes a simple router reboot works but occasionally I have to reboot reboot the server also. Right now for example, no problems at all. Several external connections and no freezes. And I can't pinpoint the exact moment the connection drops. No events are recorded and the router doesn't give me any thing to work with.
I agree with you it almost is certain that it's a NAT problem, but what? And the strange behaviour of having to reboot the server to get thing working again through NAT puzzles me too.
Hans
I did think about that but at first, everything is working fine and then all of a sudden it freezes. Only local connecions are possible and no more external. Sometimes a simple router reboot works but occasionally I have to reboot reboot the server also. Right now for example, no problems at all. Several external connections and no freezes. And I can't pinpoint the exact moment the connection drops. No events are recorded and the router doesn't give me any thing to work with.
I agree with you it almost is certain that it's a NAT problem, but what? And the strange behaviour of having to reboot the server to get thing working again through NAT puzzles me too.
Hans
Do you have another router or firewall to eliminate the Draytek?
ASKER
Hi Netflo,
Checked everything, all up to date. The server is an oldie but that can't be the problem. It's a Poweredge 2950 (2008) Server 2003 Enterprise SP2. Just checked the BIOS and that's the only thing that could use an update. But can anyone tell me why a bios update can cause a NAT on a router stop working? Anyway, I'm going to install the update this week, maybe that helps.
Hans
Checked everything, all up to date. The server is an oldie but that can't be the problem. It's a Poweredge 2950 (2008) Server 2003 Enterprise SP2. Just checked the BIOS and that's the only thing that could use an update. But can anyone tell me why a bios update can cause a NAT on a router stop working? Anyway, I'm going to install the update this week, maybe that helps.
Hans
ASKER
Hi Netflo,
I have another Draytek, different DSL line, and tried to reroute the traffic through this router, exactly the same problem. This made me wonder if there was a problem with the Draytek firmware...
Hans
I have another Draytek, different DSL line, and tried to reroute the traffic through this router, exactly the same problem. This made me wonder if there was a problem with the Draytek firmware...
Hans
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Only succesful attempts was set, failed not. I've enabled this and am going to check this next couple of days. So far no failed attempts (only hald an hour). The ID's are all low, not above 10.
Hans
Hans
ASKER
Thanks for the help but we're going to upgrade the DSL line and Terminal Server in a few weeks. We deal with the problems until the new setup is finished. Thanks anyway.
Can you also confirm your 2820 is on the latest firmware?