2003 DC suddenly died 1

[hydruid]

Ok so out of no where our 2003 dc died today.

I got a report that something was up so I went to log into the dc through rdp, but it timed out. Tried to ping it, serverdc, and instead of getting the normal 172.16.0.3 response I got a response from 64.195.235.200.

I have no idea what 64.195.235.200 is but thats the response i get when dns is dead on the dc or it's turned off.

I tried to log in through vnc to the dc but that also died.

It seems like it's stopping incoming connections. It will respond if i ping the ip but vnc/dns/rdp are all dead.

any ideas?

Correctly asked questions will receive a better answer.

 

[58sniper]

can you get log info? That might show you some more info.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[Roadki11]

Can you reboot it?



RoadKi11

"This apparent fear reaction is typical, rather than try to solve technical problems technically, policy solutions are often chosen." - Fred Cohen

 

[itsp1965]

It may not be that your server is actually down but there is some routing issue that is affecting you getting to your server. Is your server possibly NATed behind this 64.x.x.x IP address. Check your networking first to see if there is anything amiss.

 

[hydruid]

the windows firewall turned itself on, out of nowhere.

any ideas why it might have turned itself on?

Correctly asked questions will receive a better answer.

 

[58sniper]

GPO? I'd run the SCW and configure a policy so that the firewall can stay on, but the server can do its job.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/