RDP of one server stops and not accessible from outside the network
We have 15 servers running on Windows server 2003 standard R2 with SP2 on same hardware Dell 2950. But our File and Print server have problem of RDP. It stops accessing from outside of network with Remote Desktop. But when we reboot this server it starts working and accessible via RDP but same problem occur after 3-5 days. SAV 10.1 corporate version is running on this server without any scheduled scanning.
thecomputerdocs
Does it still work from within the network?
Seems, it is dying out on RDP connection being hit on the box.
Perfmon can help us analyze what and how is going on.
At the time when those RDP connections do not make through - what are the events those appear on the box ?
Perfmon can help us analyze what and how is going on.
At the time when those RDP connections do not make through - what are the events those appear on the box ?
Can you list the events here? Do you have any firewall software on the box?
If windows firewall is enabled, ensure you have removed and reset the except for port 3389 on it.
If windows firewall is enabled, ensure you have removed and reset the except for port 3389 on it.
ASKER
No We don't have any software firewall installed on any of the server. If we reboot the server then RDP starts working without any change. We also didn't see any event error related to RDP. When we try to connect RDP simply it brings back to same screen i.e. where we enter computer name. So no error occured at that time even you try as many as try. Problem remain same until reboot of the server.
Use the tool port query to check if the server is open to accept connection on port 3389 from remote client - like wise if the server rejects - at the moment use the same tool to run a test for the network firewall to check if the network firewall is at fault. This way you would back-track and check who is not allowing you to have the connection setup.
How about uninstalling Terminal Services, rebooting, and reinstalling it. Crude, but worth testing.
Wow, never heard of this troubleshooting step as above - not sure however, please do post the results if you tend to follow it.
As I said, it's crude, but if TS is only used for remote access, it shouldn't be too hard to do.
ASKER
We are using Terminal Service which come default with Server i.e. max 2 RDP connections allowed. We didn't install terminal server separately on this server for multiple user access through Remote Desktop.
Do you want me to install terminal server and check for the problem?
Do you want me to install terminal server and check for the problem?
If you are running it in remote administration mode, you aren't having to deal with licensing.
Shouldn't be too hard to uninstall, reboot, and reinstall.
Shouldn't be too hard to uninstall, reboot, and reinstall.
ASKER
Ok, let we will try it. Second, I checked with port query tool for 3389 port and right now it is showing listening. So, we will check this again when we will get the problem again because right not RDP is accessing.
Great. Thanks.
Anxious to find out how it goes......
ASKER
Hi
Haven't faced this issue since 13th. Will close this if we do not face it 1 day more.
Thanks veryone.
Haven't faced this issue since 13th. Will close this if we do not face it 1 day more.
Thanks veryone.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Since the issue has not re-surfaced for quite some time without we making any change, we will be closing this case. Thank you for your help.