Event viewer error message... 3

[dpeno]

I have a WIN2000 file server and a WIN2000 exchange 5.5 server. The exchange server is running WINS, DHCP, DNS, and exchange. The file server is running WINS, DNS as a backup. The exchange server is the primary on everything, I know not a good idea, but that is what I was presented with when I was hired. The problem is I am getting and error message on the file server that "Windows cannot obtain the domain controller name for your computer network. Return value (59)" Event ID 1000. This shows up in the app log every 5 minutes. Everything seems to work fine, email, web browsing, logins, both computers can see the other computers drives, etc. Does anyone know what the problem is? Any help would be greatly appreciated.

Dave

 

[vbrocks]

So which computer is your domain controller?
Are they both DCs?

 

[dpeno]

Yes, they are both Domain Controllers.

Dave

 

[pherr]

Assuming that the exchange box has an exterenal connection, check to see that it is not listed in dns as the address for that box(the external address). If this happens the other box can not reach the address on the network. You have to make some changes in your dns if this is the case. I have my exchange box force to the internal address to avoid this issue. If this is the case repost and I may be able to talk you through the correction.

ph

 

[dpeno]

I think DNS is setup correctly, but here it is to be sure.

Exchange server
IP 192.168.168.70
mask 255.255.255.0
gateway 192.168.168.65
DNS 192.168.168.70
WINS 192.168.168.70
forwarders are setup correctly and all outbound works fine.
Server is running: Exchange, DNS, WINS, DHCP ( I know, too much, lol)

File Server
IP 192.168.168.75
mask 255.255.255.0
gateway 192.168.168.65
DNS 192.168.168.70
DNS 192.168.168.75
WINS 192.168.168.70
Server is running: DNS and WINS

 

[vbrocks]

Each dns server in it's tcpip properties should list itself as the primary dns server and the other as the secondary.
(Change the fileserver to reflect this.)

Also check this out for the event ID 1000 every 5 minutes.......

http://support.microsoft.com/default.aspx?scid=kb;en-us;271213

 

[pherr]

Does the exchange have an external NIC or are you using a deticated proxy?

ph

 

[dpeno]

Both servers now point to themselves for DNS and the other one for secondary DNS. After making the change to the DNS on the file server the errors continue. Event ID 1000 is attached to a bunch of problems and the link from vbrocks does not describe the problem I am having. I have tried in vain to find a microsoft solution to my exact problem. The exchange server sits behind a router firewall and incomming mail is redirected to it.

Dave

 

[pherr]

Do you have any firewalls on the DC's themselves. Also, are there any 4.0 BDC in the Domain?

ph

 

[pherr]

Check the srv records in the DNS to ensure that they are there and correct for your DC's.

ph

 

[vbrocks]

Have you checked the fismo roles of the DCs, and do you have a global catalog server that is also an infrastructure master? If you do, the pdc (root server) should be the global catalog server and the other should hold the infrastructure master role, You can transfer the role pretty easily. You should have the 5 roles in your domain.... split between the two DCs.
PDC
Schema Master role
Domain Naming Master role
PDC emulator Master role
*Global Catalog Server*

Other DC
RID Master role
Infrastructure Master role

If a role is missing it could cause weird stuff like this to happen...

 

[xmsre]

It's the infamous DNS island problem.

"Exchange server
IP 192.168.168.70
mask 255.255.255.0
gateway 192.168.168.65
DNS 192.168.168.70
WINS 192.168.168.70
forwarders are setup correctly and all outbound works fine.
Server is running: Exchange, DNS, WINS, DHCP ( I know, too much, lol)

File Server
IP 192.168.168.75
mask 255.255.255.0
gateway 192.168.168.65
DNS 192.168.168.70
DNS 192.168.168.75
WINS 192.168.168.70
Server is running: DNS and WINS"


Note that each server points to itself for DNS. On startup, the netlogon service tries to register before DNS has started. This results in no records registered for the server. For right now, restart the netlogon service, ipconfig /registerdns, and nbtstat -RR. This will get the proper records registered. In the future, have the two DCs point to each other for DNS.

 

[dpeno]

Hmmmm Strange. The email server points to itself and is not getting this message. The file server gets the message when it points to itself and when it points to the email server. I rebooted the server, restarted the netlogon service. No change. I get an error file could not be found message when I try to /registerdns, /displaydns works fine. nbtstat -RR works fine. But I am still getting the error message.

Also if I have active directory running do I need WINS and NetBios?

Dave

 

[vbrocks]

Did you ever check the fismo roles as I suggested?
Have you tried shutting off the dns service (in services) on the bad server, and have that server point to the other for dns? And vice versa .... Maybe you can do without one.
I would try to free up the exchange server as much as I could.
You only need WINS if your dealing with NT4 and earlier versions of windows. It does speed things up when you browse the Network...
Be carefull of removing netbios some older applications use it....

 

[vbrocks]

There are soooo many things that could cause this problem it is not funny......

I think a wise decision would be to run network monitor and find out what is really going on ....

It could be caused by a firewall
It could be caused by the second ping failing when it tries to find the dc......

etc .... etc .....

 

[dpeno]

Sorry I have been out had to fill in at a client site. Anyway, I have not checked the fismo roles, what is that? How do you check?

I have been trying to clear off the exchange server, but since everything was setup before I got here I am going slow so not to destroy anything.

I will shut down the DNS on the problem machine and see what that does, everything is still pointing to the dns on the exchange server so it should be fine.

Thanks for the help.

Dave

 

[dpeno]

Well its gone now, yea! I shutdown dns on problem server, and also messed around with browser issues. rebooted a few times and now its gone. I dont really know what did it, I guess I could start dns backup to see if it was that or a browser issue, anyway I am going to let it sit for the weekend. Thanks so much for everyones help.

Dave