Networking Forums

Networking Forums > Computer Networking > Windows Networking > Name resolution problem - WINS to blame?

Reply
Thread Tools Display Modes

Name resolution problem - WINS to blame?

 
 
Andre
Guest
Posts: n/a

 
      07-18-2005, 01:12 PM
Strange issue on our network:

When I ping machine A, it responds with an IP address. However, it
turns out that machine A is offline, and another machine B is using
this IP address. When I ping machine B, I also get the same IP
address. So basically, whether I ping machine A or machine B, I get
the same IP address.

Needless to say, it's a problem. My network admins tell me that this
is because of WINS and how it stores the records, and there's nothing
they can do about it. The WINS interval settings are:

Renew interval: 6 days
Extinction interval: 4 days
Extinction timeout: 6 days
Verification interval: 24 days

Any ideas on what's going on here?

Our network environment:

Servers: Windows Server 2003
Client: Windows 2000, XP

DHCP enabled, Active Directory, Cisco switches, 2 WINS servers (1
primary, 1 secondary), WINS proxy disabled. Two DNS servers reside at
the same IP addresses as the WINS servers. DHCP lease: 4 hours.

 
Reply With Quote
 
 
 
 
Neteng
Guest
Posts: n/a

 
      07-18-2005, 01:42 PM
There is no reason to run WINS if you're running WIN2K and above. What they
are referring to is tombstoning which was an issue in the NT4 days. You can
clear them through WINS Admin. (or you could in NT4).

"Andre" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> Strange issue on our network:
>
> When I ping machine A, it responds with an IP address. However, it
> turns out that machine A is offline, and another machine B is using
> this IP address. When I ping machine B, I also get the same IP
> address. So basically, whether I ping machine A or machine B, I get
> the same IP address.
>
> Needless to say, it's a problem. My network admins tell me that this
> is because of WINS and how it stores the records, and there's nothing
> they can do about it. The WINS interval settings are:
>
> Renew interval: 6 days
> Extinction interval: 4 days
> Extinction timeout: 6 days
> Verification interval: 24 days
>
> Any ideas on what's going on here?
>
> Our network environment:
>
> Servers: Windows Server 2003
> Client: Windows 2000, XP
>
> DHCP enabled, Active Directory, Cisco switches, 2 WINS servers (1
> primary, 1 secondary), WINS proxy disabled. Two DNS servers reside at
> the same IP addresses as the WINS servers. DHCP lease: 4 hours.
>



 
Reply With Quote
 
Jetro
Guest
Posts: n/a

 
      07-19-2005, 11:52 AM
I would increase DHCP lease time and check DNS servers 'cause the ping
command tries to resolve the names using DNS.

 
Reply With Quote
 
Jason Gurtz
Guest
Posts: n/a

 
      07-21-2005, 06:01 PM
On 7/18/2005 09:42, Neteng wrote:
> There is no reason to run WINS if you're running WIN2K and above.


....except if you have multiple subnets and want to browse across them.


OP:
You can clear the NB cache on clients by doing nbtstat -R followed by
nbtstat -RR However, it's my understanding that 2k and XP clients will
query DNS first before resorting to WINS. That would point to a dynamic
registration problem in DNS.

~Jason

--
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
XP does not use WINS - Maybe a BUG in Name Resolution Process? FB Windows Networking 1 07-11-2008 10:18 PM
WINS resolution Dheeraj Windows Networking 1 04-25-2007 05:06 AM
Odd WINS VPN name resolution problem Jerry Paquette Windows Networking 1 02-26-2004 12:12 PM
DNS WINS resolution wrong address RRAS Roland Klein Overmeer Windows Networking 3 12-10-2003 11:54 AM
WINS, DNS And name resolution in general MJC Home Networking 3 09-06-2003 05:18 PM



1 2 3 4 5 6 7 8 9 10 11