In news:c9143664-5782-4443-a480-(E-Mail Removed),
john <(E-Mail Removed)> typed:
> I have as small network (4 computers), running 2k3. Its been running
> fine for the past year. Now all of a sudden , when I try to go to
> Active Directory Users and Computers, it tells me " Naming information
> cannot be located. Workstation driver is not installed"
> I have not changed anything and haven't altered any settings.
> The server now cannot see any clients. All computers can ping each
> other with name and address.
> Any ideas what is happenning? Would appreciate any help.
Difficult to tell without configuration information of your server and a
sample client. This is usually caused by DNS misconfiguration, but then
again, the Workstation driver not installed' message is unusual. That may be
caused by a few things, such as unchecking File and Print Services,
unchecking Client For Microsoft Networks, possibly disabling the DHCP Client
Service on the DC (a required service even though the DC has a static
address), or some third party software, such as antivirus, WIndows Defender
blocking something, or another antispyware or third party firewall blocking
it. Also multihomed DCs can cause similar issues. IT could also mean an
update or something else was installed and a reboot is required but hasn't
been rebooted yet. So you see, it could be a host of different things.
See if htis helps (even though it says for Windows 2000 SBS, it applies to
2000 and 2003 SBS and non-SBS)
Removing Client for Microsoft Networks Removes Other Services:
http://support.microsoft.com/default.aspx?kbid=322267
If the above information wasn't helpful, please post the following in order
to better assist and eliminate guesswork on our part. Your help will help us
help you.
1. Unedited ipconfig /all from two of your DCs, and one of your clients..
2. The exact zone name spellng in DNS and whether updates are allowed on the
zone.
3. The AD DNS domain name as it shows up in ADUC.
4. If the SRV records exist under your zone.
5. Any errors in the Event logs on the DC under System, Replication Service
and Directory Services (post the Event ID# and Source names please)
6. Dcdiag /v /fix > c:\dcdiag.txt (post the dcdiag.txt as an attachment)
(The Windows Support tools need to be installed from the CDROM for this
command to be available.)
7. Netdiag /v /fix > c:\netdiag.txt (post the dcdiag.txt as an attachment)
(The Windows Support tools need to be installed from the CDROM for this
command to be available.)
8. More than one subnet?
9. Forwarder(s) configured?
10. net start > c:\netstart.txt, and copy/paste the results (this tells us
what services are actually running).
Thank you,
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer
Infinite Diversities in Infinite Combinations