Hey guys,
I had a buddy call me about his server because it taking 45 minutes to an hour to boot. It is a dell server running windows 2000 server, arcserve backup and norton antivirus server. When I looked at it, the reason it was taking so long was the lanmanserver service was disabled. This of course caused all the dependent services to fail and that was the reason for the long boot time.
What I havent been able to figure is why that service was disabled. Every time we set the service to automatic start, it still got reset to disabled. I tried putting a registry monitor on the computer to see what was changing the registry key that held the information about that service. The log showed services.exe was setting the value of that registry key so the service was set to disabled instead of automatic. This doesnt stop the service from running while the computer is on and the service is already running, but when this service doesnt start at boot up the machine takes forever to boot and this is the problem. There does not seem to be any specific time this happens either. It happens at random times throughout the day.
I cant figure out why this is happending. Has anyone seen anything like this before?
Thanks
Earl![[yinyang] [yinyang] [yinyang]](/data/assets/smilies/yinyang.gif)
I had a buddy call me about his server because it taking 45 minutes to an hour to boot. It is a dell server running windows 2000 server, arcserve backup and norton antivirus server. When I looked at it, the reason it was taking so long was the lanmanserver service was disabled. This of course caused all the dependent services to fail and that was the reason for the long boot time.
What I havent been able to figure is why that service was disabled. Every time we set the service to automatic start, it still got reset to disabled. I tried putting a registry monitor on the computer to see what was changing the registry key that held the information about that service. The log showed services.exe was setting the value of that registry key so the service was set to disabled instead of automatic. This doesnt stop the service from running while the computer is on and the service is already running, but when this service doesnt start at boot up the machine takes forever to boot and this is the problem. There does not seem to be any specific time this happens either. It happens at random times throughout the day.
I cant figure out why this is happending. Has anyone seen anything like this before?
Thanks
Earl
![[yinyang] [yinyang] [yinyang]](/data/assets/smilies/yinyang.gif)