DNS Corrupted By Power Failure - What To Do?

[Tuttle@discussions.microsoft.com Keith Tuttle]

Running Windows Small Business Server 2003
Usink Linksys Wireless-G Broadband Router (that contains the DHCP - did not
use the WIndows DHCP)

Everything worked fine. Then a power failure. Now...
- (Server Mgmt->Adv Mgmt->Computer Mgmt->Services & Applications->DNS->IRON;
(IRON is name of server); double click on IRON icon; error "Cannot contact
DNS server"
- Tried to start DNS server; Error 1222: Network not present or not started
(When I restarted the server, after the failure, I got a similar error mesg -
i.e. the network was not operational)
- Pings to router and the server (initiated from the server) fail
- dcdiag.exe displayed below
Testing server: Default-First-Site-Name\IRON
Starting test: Connectivity
The host b1d4b56b-05e0-446c-8fba-ccf45e4b2622._msdcs.WestminsterBuilder
s.local could not be resolved to an IP address. Check the DNS server, DHCP,
server name, etc
Although the Guid DNS name

(b1d4b56b-05e0-446c-8fba-ccf45e4b2622._msdcs.WestminsterBuilders.local)
couldn't be resolved, the server name
(iron.WestminsterBuilders.local)
resolved to the IP address (127.0.0.1) and was pingable. Check that the IP
address is registered correctly with the DNS server.
......................... IRON failed test Connectivity

I have tried and cannot get the network/DNS to operate. My conjecture is
that the power failure corrupted, and that I need to either re-build or
startover.

Any help, guidance, direction would be appreciated. It has embarassed me;
and it is costing the company.

[Todd J Heron [MVP]]

Sounds like the IP Stack got corrupted. You have already re-initialized the
stack by re-starting the server and that didn't help so start examining your
system log and post any errors back to us. BTW, have you run a chkdsk /f /r
yet?

--
Todd J Heron, MVP Windows Server - Networking
MCSE - Windows Server 2003/2000/NT; CCA

"Keith Tuttle" <Keith Tut...@discussions.microsoft.com> wrote in message
news:FB9B4A21-54BC-4CC2...@microsoft.com...

[Keith Tuttle]

Actually - and I know what this sounds like - running chkdsk /f /r fixed the
problem. When the server came back up, the DNS server was there. This
thread is closed, and I thank you Todd