Re: Periodic RDP connection refusal by Win2003

Tech-Archive recommends: Fix windows errors by optimizing your registry



I assume that you are running SP1 on the server?
Did the problem arise suddenly, from one day to the next, or has it
gradually increased over a longer time period?
Does it happen to random clients, or is there a pattern (same
connection, same switch, same ISP)?
Does it happen at random intervals, or is there a problem-free
period after each reboot?
Does it happen at random times, or is there a pattern (coincides
with office hours, large data transfer over the network, scheduled
activities like virus scan, backup)?

There are a number of post-SP1 hotfixes which resemble your problem
description.
Check if any of the details in the articles fit your situation.

811211 - Your multiprocessor Microsoft Windows 2000 Server-based
computer or multiprocessor Windows Server 2003-based computer may
stop responding, and the keyboard may not work correctly
http://support.microsoft.com/?kbid=811211

923630 - A Windows Server 2003-based terminal server stops
responding to new connection requests, and the logon window does
not appear
http://support.microsoft.com/?kbid=923630

883670 - FIX: The Terminal Services service stops responding in
Windows Server 2003 and you receive an "The RPC service is
unavailable" error message when you try to connect to the terminal
server by using the Remote Desktop Connection program
http://support.microsoft.com/?kbid=883670

898060 - Installing security update MS05-019 or Windows Server 2003
Service Pack 1 may cause network connectivity between clients and
servers to fail
http://support.microsoft.com/?kbid=898060

324446 - Terminal Server and connected Terminal Services clients
pause when a Terminal Services client logs on or logs off
http://support.microsoft.com/?kbid=324446
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Jimmy Madden <jimmy.madden@xxxxxxxxxxxx> wrote on 10 mar 2007 in
microsoft.public.windows.terminal_services:

In the last couple of weeks, we've seen our Win2003 server start
to refuse new RDP connections. Currently connected sessions
keep going along just fine. When attempting to connect from
WinXP you get "Remote Desktop Disconnected" "The client could
not establish a connection to the remote computer. The most
likely causes for this are: 1) Remote connections might not be
enabled at the remote computer 2) The maximum number of
connections was exceeded at the remote computer, 3) A network
error occurred while establishing the connection."

Number 1 is obviously not the problem if others are already
connected. Same for number 3. We have unlimited connections,
so the rules out number 2. We're also not running out of
licenses or memory, or hard disk space. I can ping the machine
, and I can telnet to the RDP port (3389), and it accepts my
connection. I've tested Microsoft's solution for a "black-hole
router" and that test passed.

Sometimes, after 5, 10, 15 or more minutes, it starts accepting
new connections again. Sometimes it requires a reboot. I
cannot find anything in the Event Viewer to give me any clues.

To recap: Win2003 Server, temporarily stops accepting new RDP
connections, current connections keep working fine. Calgon,
take me away! Anybody got any ideas? Many thanks in advance!

Jimmy Madden
Network Admin.
HSI
.



Relevant Pages

  • Re: CALs installed, but server still limited to 2 concurrent conne
    ... SBS2003 does not support terminal services in application mode. ... Your Terminal Services Security Website ... > this is on 2003 Small buiness Server standard edition. ... >>> appears to be restricted to 2 concurrent connections. ...
    (microsoft.public.windows.terminal_services)
  • Re: Disable automatic search for network printers in XP
    ... SBS 2003 does not have Application Mode terminal services, ... two Remote Administration connections plus one console session. ... server is three connections. ...
    (microsoft.public.windows.terminal_services)
  • Re: SBS 2003 IIS BASED SERVICES FAIL INTERMITTENTLY
    ... If I read your post correctly, you have a switch where the SBS ... Run DHCP server on your SBS, and set all client machine nics to dynamic. ... Once you have your nics configured, run the Connect to the Internet wizard, ... QUESTION1 - what is REFUSING CONNECTIONS? ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Exchange 2003: too many "Current Sessions" opened
    ... So far everything is good and now I'm just monitoring my exchange. ... get the SMTP service to stop hanging in the first place. ... won't have dead connections. ... work for now until I put into production new server hardware with sbs 2003 ...
    (microsoft.public.windows.server.sbs)
  • Re: Problems with DC and TS
    ... You should never run Terminal Services on a DC, ... MCSE, CCEA, Microsoft MVP - Terminal Server ... connections but there aren't anything. ... We have a windows 2003 domain whith several windows 2003 ...
    (microsoft.public.windows.terminal_services)