pitchford
asked on
Windows 2003 no network
We suffered from a spoiler error on our printer server, which is also domain controller, dns, and dhcp servers. One of our techs rebooted the server but after several minutes it was not pingable. We went to the server and found it was at the login screen, it was rebooted.
When we logged it we were unable to ping anything on the network. I could however ping itself. Nothing could ping it either. I checked physical connections and all was fine. The windows reported it had a network connection. For lack of other ideas we rebooted again. Now everything went back to normal.
My question is what would cause an issue where after a boot the network wouldn't work but after another boot it works fine?
We have to write 2 RCA reports and as far as why the network failed I don't have a clue.
When we logged it we were unable to ping anything on the network. I could however ping itself. Nothing could ping it either. I checked physical connections and all was fine. The windows reported it had a network connection. For lack of other ideas we rebooted again. Now everything went back to normal.
My question is what would cause an issue where after a boot the network wouldn't work but after another boot it works fine?
We have to write 2 RCA reports and as far as why the network failed I don't have a clue.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.