XP does not use WINS - Maybe a BUG in Name Resolution Process?

I have a customer with a strange problem: If, in XP, they try to do a
reverse name resolution (PING -a xxx.xxx.xxx.xxx) of a name in the WINS
database, the name resolution fails, but in Vista works

When someone try to resolve a name that DOES NOT exist in DNS Zone, the
reverse resolution DON´T try via WINS, only Via Broadcasts and i could prove
it, by monitoring with NetMon 3.1 and capturing no packets directed to WINS
Servers to try to resolve the name. I could only capture DNS and after,
Broadcast packets tryingo to resolve teh name.

PC1 - DNSRV1 - AD DNS Zone and WINS(-R) Records created
PC2 - WINSRV1 - WINS Server with a WINS Server and a Databse full of
information
PC3 - XP clients pointing to DNSSRV1 and WINSRV1 in the TCP/Ip Settings
The environment, is a standard network, with XP, Vista Win2000, 2003
Servers, a AD 2003-based Domain with its default and common configurations

1) The DNS and WINS are integrated (there is a WINS and WINS-R DNS Records
created poiting to WINS Servers (WINS Record) and poiting to the AD domain
name (WINS-R record) in the Reverse lookup Zone

2) The XP (and Vista) workstations have TCP/IP are configure via DHCP with
Hybrid Node option (0x8) and default NetBIOS settings

3) The Serevrs are configured with the correct TCP/IP Settings (DNS and WINS
Servers)

Why the reverse name resolution is not working? Why in Vista works
perfectly? The customer will deploy and application that checks the XP host
name (not present in DNS, only in WINS) via Reverse name resolution after
receive a IP connection and needs to correcly identify the XP to allow the
connection

To have the XP in DNS database is out of question, the customers want to use
the name resolution process as stated in the general documentation of the
product (After DNS Cache, Hosts, DNS, try NetBios Cache, WINS (FIRTS),
Broadcast (AFTER) and LMHOSTS)

You may want to use netdiag to check any errors.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"FB" <(E-Mail Removed)> wrote in message
news:58727A1A-0011-4FC3-A7E9-(E-Mail Removed)...
>
> I have a customer with a strange problem: If, in XP, they try to do a
> reverse name resolution (PING -a xxx.xxx.xxx.xxx) of a name in the WINS
> database, the name resolution fails, but in Vista works
>
> When someone try to resolve a name that DOES NOT exist in DNS Zone, the
> reverse resolution DON´T try via WINS, only Via Broadcasts and i could
> prove
> it, by monitoring with NetMon 3.1 and capturing no packets directed to
> WINS
> Servers to try to resolve the name. I could only capture DNS and after,
> Broadcast packets tryingo to resolve teh name.
>
> PC1 - DNSRV1 - AD DNS Zone and WINS(-R) Records created
> PC2 - WINSRV1 - WINS Server with a WINS Server and a Databse full of
> information
> PC3 - XP clients pointing to DNSSRV1 and WINSRV1 in the TCP/Ip Settings
> The environment, is a standard network, with XP, Vista Win2000, 2003
> Servers, a AD 2003-based Domain with its default and common configurations
>
> 1) The DNS and WINS are integrated (there is a WINS and WINS-R DNS Records
> created poiting to WINS Servers (WINS Record) and poiting to the AD domain
> name (WINS-R record) in the Reverse lookup Zone
>
> 2) The XP (and Vista) workstations have TCP/IP are configure via DHCP with
> Hybrid Node option (0x8) and default NetBIOS settings
>
> 3) The Serevrs are configured with the correct TCP/IP Settings (DNS and
> WINS
> Servers)
>
> Why the reverse name resolution is not working? Why in Vista works
> perfectly? The customer will deploy and application that checks the XP
> host
> name (not present in DNS, only in WINS) via Reverse name resolution after
> receive a IP connection and needs to correcly identify the XP to allow the
> connection
>
> To have the XP in DNS database is out of question, the customers want to
> use
> the name resolution process as stated in the general documentation of the
> product (After DNS Cache, Hosts, DNS, try NetBios Cache, WINS (FIRTS),
> Broadcast (AFTER) and LMHOSTS)
>