Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

terminal server (2003) constant denial of RDP connections

1 view
Skip to first unread message

joep

unread,
Jul 17, 2006, 10:38:01 AM7/17/06
to
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?

Vera Noest [MVP]

unread,
Jul 17, 2006, 5:29:41 PM7/17/06
to
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==?= <jo...@discussions.microsoft.com> wrote on 17
jul 2006 in
microsoft.public.windowsnt.terminalserver.connectivity:

joep

unread,
Jul 18, 2006, 9:44:02 AM7/18/06
to
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.

Vera Noest [MVP]

unread,
Jul 18, 2006, 10:05:24 AM7/18/06
to
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==?= <jo...@discussions.microsoft.com> wrote on 18
jul 2006:

Lyndsay

unread,
Nov 7, 2006, 2:59:02 PM11/7/06
to
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?
0 new messages