Re: RDC's can't connect until after reboot

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Can the users access other resources from across the WAN? Have you sniffed
the traffic to see what is going on?

Jeff Pitsch
Microsoft MVP - Terminal Server

Forums not enough?
Get support from the experts at your business
http://jeffpitschconsulting.com

"thadpole" <thadpole@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E78F9BCA-39DE-4364-9FB2-1EDAA3FABD12@xxxxxxxxxxxxxxxx
Tried the suggestions from http://support.microsoft.com/?kbid=898060 and
it
did not solve the problem. After 3 or 4 days, the terminal server does
not
accept connections from outside the LAN. It must be rebooted.
In other posts, I read about similar problems caused by a memory leak.
But
that problem doesn't seem like it would differentiate between WAN and LAN
connections.
Any ideas?
Thank you!


"Vera Noest [MVP]" wrote:

Check if this applies:

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
_________________________________________________________
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?dGhhZHBvbGU=?= <thadpole@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 13 jul 2006 in
microsoft.public.windows.terminal_services:

I have several construction foremen that connect to our Windows
2003 Terminal Services to do their reports at the end of the day
thru the internet. At seemingly random times, they will get the
message "The client could not connect to the remote computer.
Remote connections might not be enabled or the computer might be
too busy..."

At this point, they cannot get connected, even if I log out
everyone else. However, anyone connected to the local network
can still get into TS just fine. Only after I reboot the
terminal server can the TS users outside the local network get
connected. Then, this only lasts a couple days before it
happens again.

Any help would be greatly appreciated. Thank you!



.

Relevant Pages

  • error connecting to terminal server
    ... I have terminal server licenses and few not ... Troubleshooting terminal server issues "The terminal server has ... exceeded the maximum number of allowed connections" "Terminal Server ... Remote logins are currently disabled" ... ...
    (microsoft.public.windows.terminal_services)
  • Re: Per User Cals
    ... cannot have your 15 administrators connect with a Per user license. ... then per user licensing is fine. ... concurrent Administration connections. ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: Allowing terminal server access to all internally, but only to a select few externally.
    ... access control line that allows access to the terminal server via the ... use tscc.msc to have the default RDP-Tcp connections to use nic1, ... Create a new local user group say 'TS Internet Users', ...
    (microsoft.public.windows.terminal_services)
  • Re: Emergency! Cannot Remote Logon Terminal Server
    ... Have you checked the number of allowed connections in the Network ... MCSE, CCEA, Microsoft MVP - Terminal Server ... The Client Could not establish a connetion to the remote ...
    (microsoft.public.windows.terminal_services)
  • Re: router - firewall
    ... Adzap, VPN, OpenSwan, ... but because most users will have slow internet connections when ... the connection is to the Terminal Server, ... We setup most offices with a VPN into a firewall appliance, ...
    (microsoft.public.windows.server.sbs)