[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 335
  • Last Modified:

Takes forever to log on and log off after name change

I have had to change the name of a windows 2003 server and since doing so the server now takes hours to log on to the domain and hours to log off, I have checked to make sure that the server has an entry in the DNS server and a computer account in active directory it has both.  I am also unable to RDP to the server even though RDP is enabled.
0
HelenRR
Asked:
HelenRR
  • 9
  • 6
  • 5
  • +3
1 Solution
 
Firmin FrederickSenior IT ConsultantCommented:
I notice in the tag it says "Microsoft, Windows Server 2003, SP2" can you confirm SVP2? Also is the server a DC with active directory or standalone/member?

DNS may well be an issue and with netlogon (which is likely to be the hold-up) - if you have the support tools installed try using netdiag to find possible problems and ADSEDIT (hope i spelt it right lol!) to root out old name reference if you're using active directory.

The event log on the slow log on server will have ample entries that microsoft have resolutions for.

Why not copy one or two (X) event log entries? DNS, system, application, FRS etc. so we can look with you? ;)
0
 
debuggerauCommented:
suspect the profile to be referring to the old server name, how about try another profile?
Just login as another user and see if its different, if so , just remove and recreate the other profile.

0
 
David Scott, MCSENetwork AdministratorCommented:
did you try rdp to the server via the server's ip address? if you can by ip and not name then there is a dns issue.  

is the server a domain controller?  or a member server?

has the old name been removed from dns?

anything in the error logs?

you could enable verbose logging that will give more detail as to what portion of the login/logoff process is hanging.

http://support.microsoft.com/kb/325376
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
HelenRRAuthor Commented:
The server is running service pack 2, it is not a DC but a member of the domain. With regards to DNS I have basically gone through AD and DNS searching for any references to the old name and then deleted them when I have found them.  The old name was quite old as the server has had another name change since.

I would love to attach some event log items however the server is still logging off, this has been going for 3 hours !!!
0
 
HelenRRAuthor Commented:
I cannot RDP either by IP or name, server is only a member server, I have removed the old name from both DNS and AD, unable to access error logs due ot machine taking hours to log off
0
 
PlaceboC6Commented:
Whenever you have a system taking a long time to boot or log off,  try inplugging the nic cable to see if it speeds by.
0
 
HelenRRAuthor Commented:
okay after waiting 5 hours for the logoff to complete I have given up and powered off the server. I have rebooted and managed to run windows into safe mode, the event viewer provides no clues as to the cause of this problem.

I have then rebooted into standard windows and after 20 minutes the server still says applying computer settings. I expect that it will take hours again before I can even log in.  Does anyone have any suggestions as to the cause of this. If I could at least get the machine to start up it would help.
0
 
HelenRRAuthor Commented:
I have now unplugged the lan cable and the machine booted up really quickly. any thoughts ?
0
 
ryansotoCommented:
Usually that means its a DNS issue.
In TCPIP properties your server's DNS server is pointing to your DNS server NOT an ISP DNS server correct?
0
 
HelenRRAuthor Commented:
yes that is correct, I have also run nslookup and it is going to the correct dns server
0
 
ryansotoCommented:
There is no alternate server right?  If there is thats fine as long as it again points to an internal server.
0
 
HelenRRAuthor Commented:
no alternative server
0
 
HelenRRAuthor Commented:
further, I have found that if I disconnect lan cables it will boot up quickly but cannot RDP to either IP address or computer name, can log server onto domain however ?
0
 
David Scott, MCSENetwork AdministratorCommented:
is the windows firewall on?  if so turn it off.  

stuck at applying computer settings...very well could be a dns issue as mentioned earlier.  I had a server that i created an alias for and it caused slow log off/on issues.  

look for the ip of that server in your dns and make sure there are not two host records in the forward and reverse lookup zones.  

look at the logs on your domain controller....any errors regarding that server?

take another look at your event logs--are there are any errors ?

also, run a netdiag on the server and see what you get
0
 
PlaceboC6Commented:
Helen,

You could have a third party service causing the problem.

You can try booting into Windows.

Start
Run
MSCONFIG
Go to services tab
Check the box at bottom to hide all MS services
Then clear all the remaining boxes.

Shut down server.
Plug in network cable
Boot again and see if it boots faster.

If it boots fast,  then one of the third party services you disabled is causing the issue.
Then you can simply enable one at a time until it gets slow again and you'll know who is at fault.
0
 
Firmin FrederickSenior IT ConsultantCommented:
I'm now at the edge of my seat waiting to see what the problem is, I also read someone else's post elsewhere where he was experiencing some wierd problems and it turned out to be his ethernet cable.

Now this may not really apply to you but the interesting thing is a faulty network cable can transmit enough information intermittently to allow things like joining a domain or authorising a name change but hang on log-in. It merely depnds on the amount of data required to perform the task and how many dropped packets are considered acceptable before the request times out.

Seeing as you've done everything else above you've nothing to lose by swapping cables, NIC, or even your switch.  At least you can then rule that out by process of elimination.
0
 
Firmin FrederickSenior IT ConsultantCommented:
PS: logged in...if you are...ping another IP address (preferrably the DC) and monitor the responses over a period of time e.g ping -t 192.168.x.x ideally you should have TTL <1ms on a clean network, anything else needs further investigation.

OH I almost forgot!  A long time ago when 2003 was without a service pack netlogon used to hang pretty much like this due to a dependency on lanman browser, netlogon and dns...let me see,

http://support.microsoft.com/kb/832215/en-us

go straight to the "workaround" bit

sorry I'm still tired from last nite :(
0
 
Firmin FrederickSenior IT ConsultantCommented:
oh and get some sleep, no server is worth this much effort yawn :)
0
 
PlaceboC6Commented:
Well let us know how it goes.
0
 
HelenRRAuthor Commented:
Okay, weekend has now passed and I can comment on all the assistance above as follows:-

Have swapped network cables out, still no change machine takes forever if lan cables are plugged in. However once the machine boots up, I can plug the cables back in logoff and log on to the domain.

Netdiag tests all say passed

Profile names have been changed

I have changed the machine name back to what it needs to be, no change

I can now RDP to the server but this seems to be intermittent

I have checked the DNS and can only find 1 entry for the server, which has the correct name and IP address.

I cannot find any entries in the event logs of either the server itself or the domain controller which indicate any type of problem.

I guess I am now at the end, no idea where to go next, a number of posts suggest problems with DNS can anyone point me in the direction of what type of problem I am looking for and where I might be able to find it.  I am not a great authority on DNS

0
 
PlaceboC6Commented:
Did you try using the MSCONFIG to disable third party services as a test?
0
 
HelenRRAuthor Commented:
yep, found no odd 3rd party services at all, the server has practically nothing installed on it.
0
 
Firmin FrederickSenior IT ConsultantCommented:
I'd like to draw your attention to my entry before last as you made no reference to the points I listed. In addition, if you like, setup a "logmein" account add the server and send me a request to be a member on your logmein account. I can log in and help diagnose your problem - it's easier to have hands-on.
0
 
David Scott, MCSENetwork AdministratorCommented:
"a number of posts suggest problems with DNS can anyone point me in the direction of what type of problem I am looking for and where I might be able to find it.  I am not a great authority on DNS"

What are the dns settings in tcp/ip for this server?  it should be pointed to your DC for dns.  

try clearing your dns cache

be right back

0
 
David Scott, MCSENetwork AdministratorCommented:
sorry had to shut my system down.  anyway, clear the dns cache on your server....

cmd prompt, ipconfig/flushdns.  dns cache could have an incorrect entry or be corrupt.

i had a similar problem to yours with an 2003 R2 server.  I had created an alias in dns for the server and that was causing the issue.

since you renamed the server......you could try resetting the computer account.

also, you could try removing the server from the domain and then rejoining.  
0
 
David Scott, MCSENetwork AdministratorCommented:
PS-are you running APC powerchute software on this server?
0
 
PlaceboC6Commented:
Powerchute will definitely cause it,  but I told the asker to disable third party services and that should have been included.
0
 
David Scott, MCSENetwork AdministratorCommented:
that's true
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 9
  • 6
  • 5
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now