DC name resolution issues

  • Thread starter Thread starter Nick B
  • Start date Start date
N

Nick B

Problem:

A few machines when trying to resolve the DC name are
getting an external ip address. Thus can't connect to
email or other things. Our internal ip sest is 192.x adn
it appears to trying to reach 64.x A simple fix I have
found is doing a ipconfig /release and /renew but the
error tends to still occur time to time.

Env: We have a 2000 server fully patched, and all machines
on the network are 2000 or xp. I have mainly seen the
issue in the 2000 machines as of right now.

Releated: About when this started was when our server NIC
card went poof and we had to replace it, changing all ip
addresses of the server in the original NIC to the new one.

I believe it has soemthing to do with the changing of the
server NIC but I am unsure of what to do about it. We have
set LMhosts among other attemped fixes. Any help would be
happy! :D
 
How many nics in the server? If 2 and you're using RRAS, make sure you've
done the regedits in 292822.
Does the ipconfig/all from the clients show that all is pointing to your
server-IP?

Marina
 
Hi,

a few shot in the dark questions.

regards,

SteveC
======
If at first you don't succeed, forget skydiving

Nick said:
Problem:

A few machines when trying to resolve the DC name are
getting an external ip address. Thus can't connect to
email or other things. Our internal ip sest is 192.x adn
it appears to trying to reach 64.x A simple fix I have
found is doing a ipconfig /release and /renew but the
error tends to still occur time to time.
Click to expand...
What's the 64.X ip address? Is it 64.94.110.11, or anything else
that refers to sitefinder.verisign.com?

Are SRV records being registered okay?
Env: We have a 2000 server fully patched, and all machines
on the network are 2000 or xp. I have mainly seen the
issue in the 2000 machines as of right now.
Click to expand...

Do you assign option 15 (DNS domain) in DHCP?
Do you assign internal DNS servers only in DHCP?
Releated: About when this started was when our server NIC
card went poof and we had to replace it, changing all ip
addresses of the server in the original NIC to the new one.
Click to expand...
Did you delete the original nic from the device manager before
replacing it?
 
yes it is 64.94.110.11, when we ping our server normally
it returns server (ip) when this issue occures it returns
server.domain.com (64.94.110.11)

Yes hosts, dns, wins all have the correct name-ip
configuration.

we assign our internal dns server which is the same as the
DC server so everything goes through this server.

We have not deleted the orginal nic yet but we made sure
to change the ip before diabling it so we would not have
the issue of the IP still joined to the NIC card.

Thanks
 
Nick said:
yes it is 64.94.110.11, when we ping our server normally
it returns server (ip) when this issue occures it returns
server.domain.com (64.94.110.11)
Click to expand...

The fact that you get 64.x means that your workstation is not able to
find server.domain.com. Normally, this would generate a failure, and
your workstations would use other means to find the DC.
Yes hosts, dns, wins all have the correct name-ip
configuration.
Click to expand...
Your workstations only have 1 DNS server listed, the internal one
right (as opposed to internal, ISP DNS1, ISP DNS2)? Just checking
cuz I don't know your network config.

Output of ipconfig /all from a workstation may be useful.
You can smudge the 1st two octets of any ip address, the last 2
octets are the ones that are meaningful.
we assign our internal dns server which is the same as the
DC server so everything goes through this server.
Click to expand...
Either the workstation DNS is broken, or the server DNS is broken.

Check that your SRV records are okay. MS KB article 241515
We have not deleted the orginal nic yet but we made sure
to change the ip before diabling it so we would not have
the issue of the IP still joined to the NIC card.
Click to expand...
Any subnets in your network?

regards,

SteveC
======
If at first you don't succeed, forget skydiving
 
Back
Top