SP4

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I installed Service Pack 4 on a Windows 2000 Terminal Services server and now logging in (either locally or from a remote client) takes an absurdly long time. I removed the service pack so now the server is at SP2, but the problem remains
What can I do to fix this
Many thanks in advance
 
Logging on locally (i.e. to the local SAM) or to Active Directory/NT4 Domain
Are you using roaming profiles? If so does the logon take forever using an account w/o roaming profile, i.e. local administrator account
Can you check to see if the NIC got switched to an incompatible duplex setting, i.e. Switch is set to 100 Full-Duplex and NIC is set to 100 Half-Duplex

Errors in event logs

If all else fails restore from backup or do a clean install

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- Simon wrote: ----

I installed Service Pack 4 on a Windows 2000 Terminal Services server and now logging in (either locally or from a remote client) takes an absurdly long time. I removed the service pack so now the server is at SP2, but the problem remains
What can I do to fix this
Many thanks in advance
 
Thanks
Logging on locally seems ok, and we don't use roaming profiles.
Are you suggesting the install process changed the NIC settings
Is it common for SP4 to adversley affect a Terminal Services server?
 
Well if your system is hosed, then you should restore from backup and figure out what the problem is afterwards, by doing testing on a non-production machine, i.e. on a spare server or a workstation setup as a test Terminal Server

On the test machine you can test the exact same scenario, i.e. applying SP4 to your current setup as well as doing an integrated install w/ SP4 to see if there is a difference

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- simon wrote: ----

The NIC is set to aut

I have removed SP4 and reapplied both SP2 and SP3 and applied the hotfix 324446, all to no avail
I can map a drive to the C$ directory, but logging in just doesn't happen
I didn't get any messages about conflicts when installing SP4.
 
Sorry it had to come to that, but it's the fastes method to get things back to normal, while you investigate your problem. Let me know if I can be of further assistance

At least it sounds like you have a good backup

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- simon wrote: ----

Thanks, that is the route we've gone down
cheers
 
Back
Top