Naming information cannot be located; Server not operational on Win2k3

[Ben Scaithe]

Having a problem with a Windows 2003 Server all of a sudden where everyone
loses access to the printers shared from the server. If I open Active
Directory Users and Computers at the server console, I get the following
message:

Naming information cannot be located for the following reason:
The server is not operational.

If you are trying to connect to a domain controller running Windows 2000,
verify that Windows 2000 Server Service Pack 3 or later is installed on the
domain controller, or use the Windows 2000 administration tools. For more
information about connecting to domain controllers running Windows 2000, see
Help & Support.

Rebooting the server returned things to normal, but it happened again the
very next day.

I looked in the KB and found a similar issue addressed in article 323542.
It says it applies only to Windows 2000, though, and we don't have any
TCP/IP filtering turned on at the server. Considering that I'm getting this
at the console, I don't think filtering would apply, anyway.

It first showed up right after a thunderstorm rolled through, so obviously I
suspect that's not coincidental. It's just an awful specific problem to see
for something meteorologically related.

Any thoughts?

Thanks!

- Ben

[Chriss3 [MVP]]

The first thing to do is to ensure that there is no incorrect DNS entry's in
the TCP/IP DNS Servers list at clients, servers as well at the domain
controllers. Make sure only dc's or servers with the active directory domain
dns zone is in the dns list.

--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services

No email replies please - reply in the newsgroup
------------------------------------------------
http://www.chrisse.se - Active Directory Tips

"Ben Scaithe" <quixo...@hotmail.com> skrev i meddelandet
news:%23RKQ2Ym...@TK2MSFTNGP09.phx.gbl...

[brkymc]

Could you solve that problem? Now I have the same problem exactly...

--
brkymc
------------------------------------------------------------------------
brkymc's Profile: http://forums.techarena.in/members/202779.htm
View this thread: http://forums.techarena.in/active-directory/257595.htm

http://forums.techarena.in

[Meinolf Weber [MVP-DS]]

Hello brkymc,

You are replying to a posting older then 90 days and so this is removed from
the microsoft newsgroup. Please give a complete description about your problem
including OS version and amount of DCs in use, what happened or you have
changed before.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Could you solve that problem? Now I have the same problem exactly...
>

> http://forums.techarena.in
>

[Ace Fekay [MVP-DS, MCT]]

"brkymc" <brkymc...@DoNotSpam.com> wrote in message news:brkymc...@DoNotSpam.com...

I suggest to post a new thread stating your exact problem. As Meinolf indicated, it's difficult for us to see what you are talking about, since all we see is what you see above. This is because the Microsoft newsgroups retire posts after 90 days. Techarena pusshes/pulls post from the MS newsgroup, hence where they get ALL of their posts. Funny they make you log in to be able to use it, yet the MS newsgroups are *FREE*.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.

[Ace Fekay [MVP-DS, MCT]]

"brkymc" <brkymc...@DoNotSpam.com> wrote in message news:brkymc...@DoNotSpam.com...
>

Thinking about this further, and I apologize for not offering suggestions in my earlier post, is an error like this will arise usually with a DNS mis-configuration. If the DCs, or any other machines in the domain for that matter, are using some other DNS server other than the internal DC/DNS servers, such as an ISP's DNS address in their IP properties, or the router's IP address as a DNS server in their IP properties, it can cause numerous issues. DNS is used to locate AD services and resources. If a DC or workstation queries the router or the ISP's DNS asking where the internal domain is, they do not have that answer. Various error messages will result, one of which is this subject line.

Other scenarios that will cause this:
1. Single label DNS domain name (AD DNS domain name is "DOMAIN" rather than a similar format of domain.local, domain.corp, domain.com, domain.something, etc.

2. The domain controller is multihomed. This means it has more than one NIC with an IP address on each, one NIC with multiple IP addresses, and/or RRAS installed (possibly for VPN use). All the additional IP addresses will register into DNS (provided it's not a single label name), and cause numerous problems.

I hope that helps.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.