 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Windows NT / Terminal Server / November 2006terminal server (2003) constant denial of RDP connections
Our newest terminal server constantly drops the ability for users to connect via RDP. If the machine is rebooted, it starts working again, but it requires a reboot at least daily, often more frequently. I have done the workaround described in the KB article 898060 (which is what everyone suggests to do for this problem), but it doesn't not stop the problem. For constant access, the server now is set to reboot 3 times a day, but I need to find a better solution to the problem then this. Any suggestions? What is the *exact* error message when users cannot connect? Are existing users thrown out, or can they continue to work? Are you able to logon to the physical console when this happens? If you can, have you looked at the available resources on the server, with Task Manager and Performance Manager? Is there anything in the EventLog? Can you still connect to shared drives on the server when it refuses rdp connections? Are you running SP1 on the server? _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net ___ please respond in newsgroup, NOT by private email ___ =?Utf-8?B?am9lcA==?= <joep@discussions.microsoft.com> wrote on 17 jul 2006 in microsoft.public.windowsnt.terminalserver.connectivity: > Our newest terminal server constantly drops the ability for > users to connect via RDP. If the machine is rebooted, it [quoted text clipped - 5 lines] > but I need to find a better solution to the problem then this. > Any suggestions? The exact error message is below this paragraph. Sometimes existing users are thrown out, but not all of the time. I can physically log into the console at all times. This is never affected. Everything else on the server works (though this is a dedicated server and is only used for terminal services) fine. I have looked through the event log and checked the performance monitor, but i cannot figure this problem out. I do have sp1 installed, and I have installed the 898060 fix on it. It doesn't help. error message: the client could not connect to the remote computer. remote connections might not be enabled or the computer may be too busy to accept new connections. It is also possible that network problems are preventing your connection. please try again later. if the problem continues to occur, contact your administrator. Then I would suspect a network problem first (all other problems, like licensing) would generate EventIDs). I'd run Network Monitor and check for dropped packets. _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net *----------- Please reply in newsgroup -------------* =?Utf-8?B?am9lcA==?= <joep@discussions.microsoft.com> wrote on 18 jul 2006: > The exact error message is below this paragraph. Sometimes > existing users are thrown out, but not all of the time. I can [quoted text clipped - 16 lines] > please try again later. if the problem continues to occur, > contact your administrator. I am having a very similar problem, the Windows 2003 R2 server (2 or them actually-built at same time) running in remote admin mode stop accepting rdp connections until being rebooted. While monitoring the server network port it is observed that the server is ackowledging ACK the connection attempt on port 3389, but then resetting the connection RST. Has anyone seen this before or have any ideas? > Then I would suspect a network problem first (all other problems, > like licensing) would generate EventIDs). [quoted text clipped - 29 lines] > > please try again later. if the problem continues to occur, > > contact your administrator. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.