Two machines connected to a switch: WLADIMIR (XP Home SP3) and DAGO (Win7 Pro).
WLADIMIR has received 192.168.33.130 via DHCP, DAGO has received 192.168.33.156. They can ping each other by IP address.
Now, I'd like to get the NetBIOS names to work as well. However, "host not found", both ways.
Okay, I can temporarily fix that by issuing the following command on WLADIMIR:
nbtstat -A 192.168.33.156 REM This fetches DAGO's names and puts them into the cache. ping dago REM Successful ping! nbtstat -c REM Shows names in the cache. They'll stay for ten minutes.
Here's the netstat output for WLADIMIR (XP):
:: netstat -ano | findstr 130:13 TCP 192.168.33.130:139 0.0.0.0:0 ABHÖREN 4 UDP 192.168.33.130:137 *:* 4 UDP 192.168.33.130:138 *:* 4
And for DAGO (Win7):
TCP 192.168.33.156:139 0.0.0.0:0 ABHÖREN 4 UDP 192.168.33.156:137 *:* 4 UDP 192.168.33.156:138 *:* 4
Excerpt from the services file:
netbios-ns 137/tcp nbname #NETBIOS Name Service netbios-ns 137/udp nbname #NETBIOS Name Service netbios-dgm 138/udp nbdatagram #NETBIOS Datagram Service netbios-ssn 139/tcp nbsession #NETBIOS Session Service
Hmm, 137/tcp isn't open. Possible cause?
On the WINS tab of my LAN connection, the LMHOSTS box is checked and the NetBIOS setting is set to "standard" on both machines.
Here's a good article from 2003 on NetBIOS name resolution.
(1) I guess NetBIOS names are designed to work automatically, without me intervening to call nbtstat. How do I enable this? Any services the functionality depends upon? Any firewall interference?
(2) It doesn't work the other way round, that is Win7 pinging XP by name. The nbtstat -A appears to only succeed after the same command has been issued from XP; failing that, an empty table seems to be transferred. (Sort of like: Won't show you mine unless I've seen yours.) And even after transfer of the actual table, ping WLADIMIR still won't work.