12 minute delay to reconnect after rebooting server

B

Bill Zak.

I have a few W2K servers that have terminal server running on them.
If I use a "ping servername -t" to watch the NIC, I can see that after
about 30 seconds the connection is lost, the connection stays down for
about 20 seconds, then the connection to the NIC is made again -- this
is exactly as I would expect when the server is rebooted.

However, I cannot connect in through the Terminal Services on a client
for apprx 12 minutes. I have no idea what could be causing this
delay. I have other W2K servers on the same network that can be
connected to apprx 1 minute after the reboot.

What could be causing this?

Bill
 
R

Ronan Condon

Hi Bill,

I posted today about a TermServ connection problem aswell, to which I
dont have a solution, however they may be related, as my clients could
get back in somewhere in the region of 15 mins after I restarted
Terminal Services Licensing Manager. If you figure out a solution
could you post a follow up?
Thanks, Ronan
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Unable to reconnect using remote desktop connection 1
Can anybody help with this problem? This is my 4th try 5
Connect delay 6
Windows XP Reconnecting to Windows Server 2003 1
Terminal Server License Server 1
Using 2 NICS On Terminal Server To Separate Traffic 2
Cannot reconnect to a network drive 1
Remote Connections Time out and cannot reconnect 2

Top