Server disconnects itself from the network

[robertwj]

One of our clients running server 2003 had a power failure over the weekend and the UPS did not last long enough and the server shut down unexpectedly.

Since then if i try to remote log in the server brings up the screen to give a reason why it shut down. If i choose any one it proceeds to log in then disconnects me from the remote desktop connection and then no one on the network can access anything. If i reboot its working with all the links but as soon as i try log in again.. BAM. Link lost.

I'm not really sure what to do from here

 

[Creepster]

One of our clients running server 2003 had a power failure over the weekend and the UPS did not last long enough and the server shut down unexpectedly.

Since then if i try to remote log in the server brings up the screen to give a reason why it shut down. If i choose any one it proceeds to log in then disconnects me from the remote desktop connection and then no one on the network can access anything. If i reboot its working with all the links but as soon as i try log in again.. BAM. Link lost.

I'm not really sure what to do from here

It is not happy with how it was treated.Send it for some counseling and then leave it alone.Pc's have feelings too

 

[InvisibleJim]

One of our clients running server 2003 had a power failure over the weekend and the UPS did not last long enough and the server shut down unexpectedly.

Since then if i try to remote log in the server brings up the screen to give a reason why it shut down. If i choose any one it proceeds to log in then disconnects me from the remote desktop connection and then no one on the network can access anything. If i reboot its working with all the links but as soon as i try log in again.. BAM. Link lost.

I'm not really sure what to do from here

Sounds like you're probably going to have to get on site if it's kickingyou out remotely like that. From your description, maybe a service like Routing and Remote Access or Ipsec might be giving a problem during logon and the timing suggests to me that a problem with a startup script or program. Also, have you tried logging on to the server with more than one account in case it is something to do with the profile you are using.

If you have physical access to the server and can log in, you can look in the event logs for services that have failed or other app errors. If you can't log in normally, maybe try logging in in safe mode - if this works, you can look at the event logs and temporarily disable startup programs and try booting normally. Also try logging in with a different user/admin account