Re: No DNS Lookup after Hive Recovery

http://support.microsoft.com/kb/285034

or if the problem persists, you'll likely need to perform an in-place upgrade.

How to Perform an In-Place Upgrade of Windows 2000
http://support.microsoft.com/default.aspx?kbid=292175

What an In-Place Windows 2000 Upgrade Changes and What It Does Not Change
http://support.microsoft.com/default.aspx?kbid=306952

Be sure to apply these to your repair install before connecting to any network. Internet included. (sasser, msblast)
http://download.microsoft.com/download/E/6/A/E6A04295-D2A8-40D0-A0C5-241BFECD095E/W2KSP4_EN.EXE
http://www.microsoft.com/technet/security/bulletin/MS03-043.mspx
http://www.microsoft.com/technet/security/bulletin/MS03-049.mspx

Then

Rollup 1 for Microsoft Windows 2000 Service Pack 4
http://www.microsoft.com/downloads/details.aspx?amp;displaylang=en&familyid=B54730CF-8850-4531-B52B-BF28B324C662&displaylang=en





--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Barry" wrote:

I have restored a recent SYSTEM file from a Hive backup and can get on now as Administrator. The main problem is there appears to be no DNS lookup available...

1. I can ping Google OK by its IP address and get to it by IP addres but not get there by name.
2. Anything in the HOSTS file that is out on the internet also pings OK.
3. NSLOOKUP gives ***Default servers are not available.
4. Currenty operating on DHCP but have tried specifying fixed IP with Primary/Seconday DNS Servers; this gives the same answer - NSLOOKUP cannot see the servers.
5. I can ping the router gateway on 192.168.0.1 and it is there as other PCs on the subnet can see it and are working through it.
6. Tried NETDIAG and this yields...

Adapter : LAN1
Netcard queries test . . . : Passed
Host Name. . . . . . . . . : charlie
IP Address . . . . . . . . : 192.168.0.2
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.0.1
Dns Servers. . . . . . . . : 192.168.0.1
IpConfig results . . . . . : Failed
Pinging DHCP server - not reachable
WARNING: DHCP server may be down.
AutoConfiguration results. . . . . . : Passed
Default gateway test . . . : Failed
No gateway reachable for this adapter.
NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenger Service', <20> 'WINS' names is missing.
WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.

Any help appreciated.
Barry.




.

Relevant Pages

  • Re: AD Upgrade Question
    ... new servers and have Windows 2003 Server running on them. ... servers as 2k3 CD's and decommisioning the existing 2 DC's. ... the Infrastructur Master from the GC server). ... You should upgrade the machine that holds the token for the the Schema ...
    (microsoft.public.win2000.active_directory)
  • Re: AD Upgrade Question
    ... new servers and have Windows 2003 Server running on them. ... servers as 2k3 CD's and decommisioning the existing 2 DC's. ... the Infrastructur Master from the GC server). ... You should upgrade the machine that holds the token for the the Schema ...
    (microsoft.public.win2000.active_directory)
  • Re: Cant access add-remove
    ... tried to open add-remove. ... If the problem persists, you'll likely need to perform an in-place ... How to Perform an In-Place Upgrade of Windows 2000 ...
    (microsoft.public.win2000.general)
  • Re: NT to AD Migration Help Please!
    ... am in fear that NT is no longer supported and these are old Servers. ... You cannot join a DC running AD to a Windows NT ... Upgrade your NT4 Domain. ... and putting NT4 on it and make it a BDC in the NT4 Domain. ...
    (microsoft.public.win2000.active_directory)
  • 6702 merrors in dns event log
    ... Two DC's, both running Windows 2003. ... At the time of the upgrade, ... Domain functional level is Windows 2000 native, Dns is Ad integrated. ... Every day, though, I get 6702 errors in the dns logs on both servers. ...
    (microsoft.public.windows.server.dns)