Netbios name resolution problems (includes ipconfig and browstat info)

[Chris]

Here is the information from several computers that are having trouble
with NetBIOS resolution. shares do not work with Netbios names, but
they work OK with IP addresses. They are behind a Netgear WR614Gv4
wireless "router".

When trying to connect to a share on the other computer they report that
the machine was not found.


COMPUTER DJOLAB6:
-----------------

Windows IP Configuration



Host Name . . . . . . . . . . . . : djolab6

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Peer-Peer

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : gdcb.iastate.edu



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : gdcb.iastate.edu

Description . . . . . . . . . . . : 3Com 3C918 Integrated Fast
Ethernet Controller (3C905B-TX Compatible)

Physical Address. . . . . . . . . : 00-C0-4F-49-27-21

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.4

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 192.168.0.1

Lease Obtained. . . . . . . . . . : Thursday, April 06, 2006 3:
44:12 PM

Lease Expires . . . . . . . . . . : Sunday, April 09, 2006 3:44:
12 PM


Status for domain DJOLAB on transport \Device\NetBT_Tcpip_{7A729FD4-74E1-
499B-B6B5-15C7F20633C6}
Browsing is NOT active on domain.
Master name cannot be determined from GetAdapterStatus.


COMPUTER DJOLAB2:
-----------------





Windows IP Configuration



Host Name . . . . . . . . . . . . : djolab2

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Peer-Peer

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : gdcb.iastate.edu



Ethernet adapter Wireless Network Connection:



Connection-specific DNS Suffix . : gdcb.iastate.edu

Description . . . . . . . . . . . : NETGEAR WG311v2 802.11g
Wireless PCI Adapter

Physical Address. . . . . . . . . : 00-09-5B-BF-14-CB

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.12

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 192.168.0.1

Lease Obtained. . . . . . . . . . : Thursday, April 06, 2006 3:
39:29 PM

Lease Expires . . . . . . . . . . : Sunday, April 09, 2006 3:39:
29 PM


Status for domain DJOLAB on transport \Device\NetBT_Tcpip_{94B14D9C-9152-
43E3-84A5-45D56865BF7F}
Browsing is active on domain.
Master browser name is: DJOLAB2
Master browser is running build 2600
1 backup servers retrieved from master DJOLAB2
\\DJOLAB2
There are 2 servers in domain DJOLAB on transport \Device\NetBT_
Tcpip_{94B14D9C-9152-43E3-84A5-45D56865BF7F}
There are 1 domains in domain DJOLAB on transport \Device\NetBT_
Tcpip_{94B14D9C-9152-43E3-84A5-45D56865BF7F}

 

[Lanwench [MVP - Exchange]]

Here is the information from several computers that are having trouble
with NetBIOS resolution. shares do not work with Netbios names, but
they work OK with IP addresses. They are behind a Netgear WR614Gv4
wireless "router".

When trying to connect to a share on the other computer they report that
the machine was not found.

Install and use WINS - and dish out the WINS server IP (and node type 0x8)
to all clients in your DHCP scope.

 

[Chuck]

Here is the information from several computers that are having trouble
with NetBIOS resolution. shares do not work with Netbios names, but
they work OK with IP addresses. They are behind a Netgear WR614Gv4
wireless "router".

When trying to connect to a share on the other computer they report that
the machine was not found.

Chris,

As LanWench suggests, use a WINS server. Or fix the Node Type.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html#Peer-Peer>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html#Peer-Peer

Also, is NetBT explicitly enabled on all computers?
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components

 

[Chris]

Chuck,
That worked!!! Thanks a bunch!


-Chris

Chris,

As LanWench suggests, use a WINS server. Or fix the Node Type.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html#
Peer-Peer> http://nitecruzr.blogspot.com/2005/05/address-resolution-on-
lan.html#Peer-Peer

Also, is NetBT explicitly enabled on all computers?
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-
neighborhood.html#Components> http://nitecruzr.blogspot.com/2005/05/
troubleshooting-network-neighborhood.html#Components

 

[Chuck]

On Fri, 07 Apr 2006 16:41:48 -0700, Chris <> wrote:

Thanks for the feedback, Chris! What did you have to change?

 

[Chris]

I had to do the registry edit and enable NetBT that way. It took a
couple of reboots but after that everything worked perfectly.