Connect delay

  • Thread starter Thread starter Jeff Mackeny
  • Start date Start date
J

Jeff Mackeny

Hello everybody,

I just put up a brand new state of the art Dell server that also serves as a
terminal server, for some reason there about a minute delay between clicking
connect on the remote desktop client and getting the log on to windows
screen, the logon process as well as actually working on the TS is lighting
fast, this new Dell box is replacing an old clone server, the same process
on the old server took about 5 seconds, with the old TS I would hit connect
and not even 5 seconds I was already at the log on to windows screen. Same
problem for LAN or WAN users.

Thanks
 
Anything in the EventLog on the client or the server?

You cloned this server, right? Have you used SIDwalker or some other
utility that produces a unique SID for the new server?

Did you re-use the NetBIOS name or IPnumber from the old server? Have
you checked if your DNS records have been updated?

If you don't find something obviously wrong in your DNS server or IP
configuration on the server, you could try to remove the server from
the domain, delete the computer account for the server from the
domain and then re-join the domain again.
 
Nothing in the event log, I did not clone this server, I simply transferred
all roles from the old server to this new server, then DCPromo'd the old
server to demote the old server before I pulled the plug, the new server is
not using the same NetBios name and it's the only DC in the domain, the
server is hosting all five roles, a netdiag /f passes all tests including DNS
 
ok I found some entries referencing the old server, I removed all of them, I
think its a little better, but now I noticed that I have a much more serious
problem, the server drops the connection every now and then on a random
basis and the client will see a computer network icon with a red X flashing
on the upper right hand corner, which basically means that its
AutoReconnecting, I think that after my above changes it doesn't drop so
often but still drops, I configured RDP to never disconnect when idle, I
basically set everything to never, it also drops even while you work. It's
really frustrating, a brand new server with so many issues, WHY??
 
OK, I bet that if you turn on the old server again, the problem is
gone. There's probably some reference to the old server left in
the registry. You could do a complete search of the registry as
well.
Or is the problem located on the clients? How are they configured?
Are they still searching for the old server?

FileMon and RegMon and a network sniffer might show you what is
taking such time.

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*
 
Replacing the only DC in an AD domain is not a trivial operation.
Since your problem has nothing to do with Terminal Services, I
would post to an active directory newgroup. You will probably get
much better advice there.

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*
 
Back
Top