Re: Name resolution Issue after changing nic
- From: "Kurt" <lorentzenkurt@xxxxxxxxxxxxxxxxxx>
- Date: Sun, 20 Aug 2006 13:59:16 -0700
This does not make sense at all. If you do an nslookup from a workstation
what is returned? What server returns it? Do you have only your AD DNS
server as a resolver? The obvious guess is that the workstations failed to
contact the server during/after changing NICs and began using a non-local
alternate.
....kurt
"not1035" <not1035@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:617316FB-72B3-4539-A0C4-67250CB0ABF9@xxxxxxxxxxxxxxxx
I disabled the nic in my Win2K server and replaced it with a newer GigE
network card. This server takes care of DNS, DHCP, AD. I assigned the
same IP values from the old nic to the new nic once it was installed
and the original nic was disabled. What's happening now is machines
that are not members of the domain (roughly 10-30 of various
workgroups) cannot ping the server by Name only. They are resolving
the server name to a random IP address that is not at all related to
the IP scheme we are using. They can ping the server by its actual IP
address and can release and renew their IP addresses through the server
with no problem. The name resolution problem didn't occur until I
installed the new nic. This is affecting their access to share's,
etc... I tried flushing the DNS on the workstations but still have the
same issue. Any advice would be greatly appreciated. Thank you in
advance!!!
Steve
.
- Prev by Date: Re: Briefcase Problem
- Next by Date: Re: Internet access control queston?
- Previous by thread: Briefcase Problem
- Next by thread: MS network Monitor on the command line
- Index(es):
Relevant Pages
|
