NetBIOS Name resolution failure

D

Douglas

I am receiving NetBT error 4321 when I start one of the
PCs on my LAN (description of this problem below) and
this machine can access other machines only by ping, not
by computer name.

I have examined the Local NetBIOS Name tables on three
machines on the network and found that all of the
machines on the network have the following entries:

PARALLAX <00> GROUP Registered
PARALLAX <1E> GROUP Registered


but only two of the machines (including the problem
machine) have the following entry:

PARALLAX <1D> UNIQUE Registered

This is also the name that appears in the NBT 4321 error
message, so I think it is directly related the problem.

PARALLAX is the Workgroup name for all of the computers
on the LAN, and is not shared by any workstations on the
network.

I have also noticed that the problem workstation is the
only one without an Internet Gateway entry on the Network
Connections page.

Any ideas how to correct this problem would be greatly
appreciated.

Problem previously described:

NetBT error 4321

"The name "PARALLAX :1d" could not be registered on
the Interface with IP address 192.168.1.51. The machine
with the IP address 192.168.1.2 did not allow the name to
be claimed by this machine."

PARALLAX is the workgroup to which all the PCs on the
network belong. 192.168.1.51 is the machine that I am no
longer able to ping after this error. 192.168.1.2 is the
only machine on the network with a fixed IP address.

When I search on this error, I find:

We're sorry
There is no additional information about this issue in
the Error and Event Log Messages or Knowledge Base
databases at this time. You can use the links in the
Support area to determine whether any additional
information might be available elsewhere

Any ideas?

Problem previously described:

I have two Windows XP Pro machines networked via a
 
S

Steve Winograd [MVP]

"Douglas" said:
I am receiving NetBT error 4321 when I start one of the
PCs on my LAN (description of this problem below) and
this machine can access other machines only by ping, not
by computer name.

I have examined the Local NetBIOS Name tables on three
machines on the network and found that all of the
machines on the network have the following entries:

PARALLAX <00> GROUP Registered
PARALLAX <1E> GROUP Registered


but only two of the machines (including the problem
machine) have the following entry:

PARALLAX <1D> UNIQUE Registered

This is also the name that appears in the NBT 4321 error
message, so I think it is directly related the problem.

PARALLAX is the Workgroup name for all of the computers
on the LAN, and is not shared by any workstations on the
network.

I have also noticed that the problem workstation is the
only one without an Internet Gateway entry on the Network
Connections page.

Any ideas how to correct this problem would be greatly
appreciated.

Problem previously described:

NetBT error 4321

"The name "PARALLAX :1d" could not be registered on
the Interface with IP address 192.168.1.51. The machine
with the IP address 192.168.1.2 did not allow the name to
be claimed by this machine."

PARALLAX is the workgroup to which all the PCs on the
network belong. 192.168.1.51 is the machine that I am no
longer able to ping after this error. 192.168.1.2 is the
only machine on the network with a fixed IP address.

When I search on this error, I find:

We're sorry
There is no additional information about this issue in
the Error and Event Log Messages or Knowledge Base
databases at this time. You can use the links in the
Support area to determine whether any additional
information might be available elsewhere

Any ideas?

The <1D> entry identifies a computer as the master browser for the IP
subnet, and there can only be one master browser.

To prevent the problem computer from trying to become the master
browser, disable the Computer Browser service:

1. Right click My Computer, and click Manage.
2. Double click Services and Applications.
3. Double click Services.
4. Double click Computer Browser. If the Service status is Started,
click Stop.
5. Set the Startup type to Disabled.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
D

Douglas

I have disabled the computer browser service on all
machines on the LAN except for one. I am no longer
receiving the NetBT 4321 message on the problem machine.

However, this machine can still not see the other
machines on the LAN by NetBIOS name, only by IP address.

So problem machine can ping other machines on the network
by IP address but not by name. Other machines cannot
ping problem machine by IP address or name.

I am not running ICF on problem machine, and node type on
problem machine is set to Unknown.

Any further thoughts?

-----Original Message-----
 
S

Steve Winograd [MVP]

"Douglas" said:
I have disabled the computer browser service on all
machines on the LAN except for one. I am no longer
receiving the NetBT 4321 message on the problem machine.

However, this machine can still not see the other
machines on the LAN by NetBIOS name, only by IP address.

So problem machine can ping other machines on the network
by IP address but not by name. Other machines cannot
ping problem machine by IP address or name.

I am not running ICF on problem machine, and node type on
problem machine is set to Unknown.

Any further thoughts?

Make sure that NetBIOS over TCP/IP is enabled on all computers, as
shown here:

Enable NetBIOS Over TCP/IP (NetBT)
http://www.practicallynetworked.com/sharing/troubleshoot/netbt.htm

On the problem computer, run "ipconfig /all" and look at the "Node
Type" at the beginning of the output. If it says "Peer-to-Peer"
(which should actually be "Point-to-Point") that's the problem. It
means that the computer only uses a WINS server, which isn't available
on a peer-to-peer network, for NetBIOS name resolution.

If that's the case, run the registry editor, open this key:

HLM\System\CurrentControlSet\Services\Netbt\Parameters

and delete these values if they're present:

NodeType
DhcpNodeType

Reboot, then try network access again.

If that doesn't fix it, open that registry key again, create a DWORD
value called "NodeType", and set it to 1 for "Broadcast" or 4 for
"Mixed".

For details, see these Microsoft Knowledge Base articles:

Default Node Type for Microsoft Clients
http://support.microsoft.com/default.aspx?scid=kb;en-us;160177

TCP/IP and NBT Configuration Parameters for Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314053
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
D

Douglas

I have changed the node type on 2 machines to none and on
the problem machine to none, Broadcast, and Mixed - the
results are all the same:

1. No more Nbt error in event viewer.
2. Machine A and B cannot ping Machine C (problem
machine) by IP address or name.
3. When machine C first starts up, it can see Machines A
and B in Parallax workgroup and can also ping machine B
by name and IP address and Machine A by IP address only
(not name).
4. After a few minutes, Machine C loses the ability to
access Parallax workgroup with error message: "Parallax
is not accessible. You might not have permission..." At
the same time it loses the ability to ping Machine B by
name.

Any further ideas? I am really stuck here.


-----Original Message-----
 

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


Top