NetBios Browsing Issues

R

Rik

Issue: Cannot connect to another workgroup client using
NetBios name. Cannot view clients on a workgroup by
browsing network.

OS: Windows XP Pro SP1 with all current updates installed

Internet Connection Firewall is not enabled

File and Print Sharing is enabled

NetBios over TCP/IP Enabled

TCP/IP NetBios Helper Service is running

Workgroup is a DHCP environment receiving IP address from
Linksys router. Host file is not an option with DHCP.

·Successfully pinged all workgroup clients with IP address

· Cannot ping any workgroup clients with NetBios Name

· Ran command "nbtstat -A 192.168.1.x" and received
network clients NetBios Table

·Following command "nbtstat -A 192.168.1.x",(where X is
the clients ip address) I can successfully ping workgroup
clients NetBios name and browse clients resources though
Explorer.

· Still cannot display a list of clients in the workgroup
by browsing through My Network Places. Receive error
message "

·Upon reboot, issue returns and cannot resolve NetBios
names of clients.



EXAMPLE

C:\>ping AMACS1

Ping request could not find host AMACS1. Please check the
name and try again



C:\>nbtstat -A 192.168.1.3



Local Area Connection 4:

Node IpAddress: [192.168.1.5] Scope Id: []



NetBIOS Remote Machine Name Table



Name Type Status

---------------------------------------------

AMACT1 <00> UNIQUE Registered

WORKGROUP <00> GROUP Registered

AMACT1 <03> UNIQUE Registered

AMACT1 <20> UNIQUE Registered

WORKGROUP <1E> GROUP Registered



MAC Address = 00-B0-SW-84-DE-48

C:\ping amact1

Pinging amact1 [192.168.1.3] with 32 bytes of data:

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.1.3:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms
 
B

Bill Libodois

For netbios name resolution without a wins server and without a windows
server product (win2k server, win2003 server, winNT4 server) to work you
need for all machines to be on the same broadcast domain. Please verify that
all clients are on the same network because this is not clear from what you
are saying. If not you either have to use wins (recommended in small/medium
environments), a windows server (not recommended over wan) or rely to
dynamic dns registrations via win2k (but i am not quite sure if this works
without setting up active directory).

Kind regards

Issue: Cannot connect to another workgroup client using
NetBios name. Cannot view clients on a workgroup by
browsing network.

OS: Windows XP Pro SP1 with all current updates installed

Internet Connection Firewall is not enabled

File and Print Sharing is enabled

NetBios over TCP/IP Enabled

TCP/IP NetBios Helper Service is running

Workgroup is a DHCP environment receiving IP address from
Linksys router. Host file is not an option with DHCP.

·Successfully pinged all workgroup clients with IP address

· Cannot ping any workgroup clients with NetBios Name

· Ran command "nbtstat -A 192.168.1.x" and received
network clients NetBios Table

·Following command "nbtstat -A 192.168.1.x",(where X is
the clients ip address) I can successfully ping workgroup
clients NetBios name and browse clients resources though
Explorer.

· Still cannot display a list of clients in the workgroup
by browsing through My Network Places. Receive error
message "

·Upon reboot, issue returns and cannot resolve NetBios
names of clients.



EXAMPLE

C:\>ping AMACS1

Ping request could not find host AMACS1. Please check the
name and try again



C:\>nbtstat -A 192.168.1.3



Local Area Connection 4:

Node IpAddress: [192.168.1.5] Scope Id: []



NetBIOS Remote Machine Name Table



Name Type Status

---------------------------------------------

AMACT1 <00> UNIQUE Registered

WORKGROUP <00> GROUP Registered

AMACT1 <03> UNIQUE Registered

AMACT1 <20> UNIQUE Registered

WORKGROUP <1E> GROUP Registered



MAC Address = 00-B0-SW-84-DE-48

C:\ping amact1

Pinging amact1 [192.168.1.3] with 32 bytes of data:

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.1.3:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms
 
R

Ron Lowe

Issue: Cannot connect to another workgroup client using
NetBios name. Cannot view clients on a workgroup by
browsing network.

OS: Windows XP Pro SP1 with all current updates installed

Internet Connection Firewall is not enabled

File and Print Sharing is enabled

NetBios over TCP/IP Enabled

TCP/IP NetBios Helper Service is running

Workgroup is a DHCP environment receiving IP address from
Linksys router. Host file is not an option with DHCP.

·Successfully pinged all workgroup clients with IP address

· Cannot ping any workgroup clients with NetBios Name

· Ran command "nbtstat -A 192.168.1.x" and received
network clients NetBios Table

·Following command "nbtstat -A 192.168.1.x",(where X is
the clients ip address) I can successfully ping workgroup
clients NetBios name and browse clients resources though
Explorer.

· Still cannot display a list of clients in the workgroup
by browsing through My Network Places. Receive error
message "

·Upon reboot, issue returns and cannot resolve NetBios
names of clients.



EXAMPLE

C:\>ping AMACS1

Ping request could not find host AMACS1. Please check the
name and try again



C:\>nbtstat -A 192.168.1.3



Local Area Connection 4:

Node IpAddress: [192.168.1.5] Scope Id: []



NetBIOS Remote Machine Name Table



Name Type Status

---------------------------------------------

AMACT1 <00> UNIQUE Registered

WORKGROUP <00> GROUP Registered

AMACT1 <03> UNIQUE Registered

AMACT1 <20> UNIQUE Registered

WORKGROUP <1E> GROUP Registered



MAC Address = 00-B0-SW-84-DE-48

C:\ping amact1

Pinging amact1 [192.168.1.3] with 32 bytes of data:

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.1.3:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms







Sounds like NetBIOS name resolution failure.
Node Type is the key to this.

Just to go over some basics again:

From a broken machine, go to a command prompt and try to ping
another machine by IP address and then by name.
Eg:

ping 192.168.0.10
ping OtherBox

If the first works, but the second fails then this indicates
NetBIOS name resolution failure.

1) Ensure all firewalls are disabled or preferably un-installed
as per the mfr's instructions prior to any fault-finding.

2) Go to TCP/IP properties, advanced button, WINS tab
and ensure NetBIOS-over-TCP/IP is enabled;

3) Go to a command prompt, and issue the command:
IPCONFIG /ALL.
Look at the Node Type.
If it's P-to-P, that's a problem.

In this case, go to Start | Run | regedit.
Go to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netbt\Parameters

If either of the following values are present, delete them:

NodeType;
DhcpNodeType.

This should cause the node type to default correctly.
( the node type will report as 'Unknown' in the default case. )

For futher details, see this article:
Default Node Type for Microsoft Clients
http://support.microsoft.com/default.aspx?scid=kb;en-us;160177


Post back with what you find...
 
R

Rik

Ron,

After running REGEDIT I found DHCPNodeType with a value
of 8 in the Netbt\Parameters. I deleted it, restarted my
machine and the issue was resolved.

Thanks so much for your assistance. I spent a lot of
time in an attempt to solve this issue and spoke with a
lot of people who were juste as baffled as I was.

Thanks again.
-----Original Message-----
Issue: Cannot connect to another workgroup client using
NetBios name. Cannot view clients on a workgroup by
browsing network.

OS: Windows XP Pro SP1 with all current updates installed

Internet Connection Firewall is not enabled

File and Print Sharing is enabled

NetBios over TCP/IP Enabled

TCP/IP NetBios Helper Service is running

Workgroup is a DHCP environment receiving IP address from
Linksys router. Host file is not an option with DHCP.

·Successfully pinged all workgroup clients with IP address

· Cannot ping any workgroup clients with NetBios Name

· Ran command "nbtstat -A 192.168.1.x" and received
network clients NetBios Table

·Following command "nbtstat -A 192.168.1.x",(where X is
the clients ip address) I can successfully ping workgroup
clients NetBios name and browse clients resources though
Explorer.

· Still cannot display a list of clients in the workgroup
by browsing through My Network Places. Receive error
message "

·Upon reboot, issue returns and cannot resolve NetBios
names of clients.



EXAMPLE

C:\>ping AMACS1

Ping request could not find host AMACS1. Please check the
name and try again



C:\>nbtstat -A 192.168.1.3



Local Area Connection 4:

Node IpAddress: [192.168.1.5] Scope Id: []



NetBIOS Remote Machine Name Table



Name Type Status

---------------------------------------------

AMACT1 <00> UNIQUE Registered

WORKGROUP <00> GROUP Registered

AMACT1 <03> UNIQUE Registered

AMACT1 <20> UNIQUE Registered

WORKGROUP <1E> GROUP Registered



MAC Address = 00-B0-SW-84-DE-48

C:\ping amact1

Pinging amact1 [192.168.1.3] with 32 bytes of data:

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.1.3:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms







Sounds like NetBIOS name resolution failure.
Node Type is the key to this.

Just to go over some basics again:

From a broken machine, go to a command prompt and try to ping
another machine by IP address and then by name.
Eg:

ping 192.168.0.10
ping OtherBox

If the first works, but the second fails then this indicates
NetBIOS name resolution failure.

1) Ensure all firewalls are disabled or preferably un- installed
as per the mfr's instructions prior to any fault-finding.

2) Go to TCP/IP properties, advanced button, WINS tab
and ensure NetBIOS-over-TCP/IP is enabled;

3) Go to a command prompt, and issue the command:
IPCONFIG /ALL.
Look at the Node Type.
If it's P-to-P, that's a problem.

In this case, go to Start | Run | regedit.
Go to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netbt
\Parameters

If either of the following values are present, delete them:

NodeType;
DhcpNodeType.

This should cause the node type to default correctly.
( the node type will report as 'Unknown' in the default case. )

For futher details, see this article:
Default Node Type for Microsoft Clients
http://support.microsoft.com/default.aspx?scid=kb;en- us;160177


Post back with what you find...



--
Best Regards,
Ron Lowe
MS-MVP Windows Networking


.
Click to expand...
 
H

Hans-Georg Michna

Rik said:
After running REGEDIT I found DHCPNodeType with a value
of 8 in the Netbt\Parameters. I deleted it, restarted my
machine and the issue was resolved.
Click to expand...

Rik,

thanks a lot for reporting this.

I don't understand why it worked, as 8 means Hybrid and should
work. When the client finds no WINS server, it should broadcast.
My computers here also have that value, and they work just fine
in the absence of any WINS servers.

Ron, are you around and know more?

Hans-Georg
 
R

Ron Lowe

Hans-Georg Michna said:
Rik,

thanks a lot for reporting this.

I don't understand why it worked, as 8 means Hybrid and should
work. When the client finds no WINS server, it should broadcast.
My computers here also have that value, and they work just fine
in the absence of any WINS servers.

Ron, are you around and know more?

Hans-Georg
Click to expand...

I'm around ( slightly sporadically at the moment.. ).

I agree that a node type of 8 ( hybrid) means:
" Try WINS first, then fall back on broadcast".

I can't explain why this fixed it in this case.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

XP - Ping one way but not other? 0
XP - Ping one way but not other? 8
Cannot map any shared drives available on the network 1
when I ping my own computer's netbios name... 4
Cannot connect XP Pro SP2 to Windows ME 2
File and print sharing problems 6
Cannot access local network - pings successfully + can access by I 4
Network only working one way? 4

Top