Network access issues after power failure

Posted on 2009-02-09
Last Modified: 2013-12-23
UPS failed after surge, causing power failure and reboot of domain controller.
- After reboot, none of the clients can access the DC.
- During reboot, the following error is reported: The system has detected an IP address conflict with another system on the network. The local interface has been disabled.
- The App event log has only 2 errors, both: USERENV / 1000
   - windows cannot access the file gpt.ini for gpo
   - windpws cannot query for the list of gp objects
- DHCP is handled by a Firewall. The DC is one of 4 computers with static IPs, the remainder are dynamic
- Although the DC local adapter has been disabled, I can ping the IP address assigned for that box
- The server and firewall have been restarted
- Most computers have access to internet, but the DC does not.
I need to restore network to normal operation ASAP. THanks
Question by:ironkernel

    Expert Comment

    Sounds like you just need to determine which device on your network is picking up this IP.  Perhaps you could c$ into the system to determine which it is and from there ensure it isn't able to pick up this address?

    Maybe just try a start\run\  \\\C$ or just a \\  You might also try typing the address in questino into a web browser - I've had issues on occasions with printers latching onto reserved addresses and causing similar problems.

    Obviously the IP range would be your range, not necessarily  
    LVL 4

    Expert Comment

    Ensure that your statically assigned IP addresses are not part of your DHCP scope in your firewall. Even though the DC's address is static, if it is part of the pool, a client can pick up the IP address thus causing the IP conflict.
    LVL 1

    Accepted Solution

    Your DC will never start if it detects an IP address conflict.
    Make sure that the scope of the DHCP is not service IP addresses that could conflict with your DC and if so, make 'reservations' so a PC will never be assigned the same Ip as your DC.

    After chacking that, the simplest way is to reboot your ethernet switch which will force all your ethernet (workstations) to get a new IP address from your DHCP server. If you have an extra switch, you can ping and move connections one at a time intil you can no longer ping the workstation that has the duplicate IP.

    You could also change the IP if the DC temporarily, but you would also have to set your DHCP server to the new IP of your DC, especially if your DC is also your DNS and possible a WINS server. You could easily reset your clients by powering off your hub of switch. That's a rough way to do it, and if you have routes, DHCP agent relays and such from remote nets, then this would not be the way to go.

    LVL 11

    Expert Comment

      If you had a power outage like that there is a good chance that any little internet router (maybe you main one) or access point got reset to its factory defaults and is now conflicting with the static IP address on the server.
    LVL 7

    Expert Comment

    use psshutdown from the sysinternals package to shut down the system which is holding the IP, then you should be able to get your DC online.  Then, wait for the call from the person saying "my computer just shut off, and it said to call you"
    LVL 3

    Expert Comment

    I ran into this last week .. I fixed it by shutting down the server and unplugging all peripherals except for the monitor mouse keyboard and network card.. I found that the USB from the UPS was causing a conflict... wierd I know but it worked.

    Author Closing Comment

    I'm not 100% sure why this worked, but the DC was reset to a different IP to get back online. The original IP was still in use but couldn't be tied back to any hardware even after cycling router. Cycled switch and the IP cleared. Still clearing some minor issues, but back in business. Thanks

    Featured Post

    What Is Threat Intelligence?

    Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

    Join & Write a Comment

    A common practice in small networks is making file sharing easy which works extremely well when intra-network security is not an issue. In essence, everyone, that is "Everyone", is given access to all of the shared files - often the entire C: drive …
    Here's a very brief overview of the methods PRTG Network Monitor ( offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
    In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor ( If you're interested in additional methods for monitoring bandwidt…

    731 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    18 Experts available now in Live!

    Get 1:1 Help Now