Workgroup Computers Not Accessible by Name - only IP Address

[Doug]

I am attempting to attach to an existing workgroup with a
new wired laptop. I can see the workgroup and have
Internet access, but upon clicking on the workgroup
accessing receive the error ""workgroup" is not
accessible. You might not have permission..." I can ping
each workstation's IP address within the workgroup, but
if I ping the computer name, I can't access them. If I
type "\\ipaddress" in the run box I see the individual
workstation's shared info, but typing "\\name" gives
error "The network path is not found"

I have tried everything in article 314067 and have reset
the IP from article 299357. The correct
service "Computer Browser" is running, and have tried
disabling IPSec. I have shared everything. Other
computers and wireless laptops attaching to the access
point this laptop is using have access, eliminating any
outside hardware devices possibly causing the issue.

It seems there may be some corruption somewhere, and am
considering reinstalling Windows XP Home on top of the
existing install, but I don't want to go this route and
reinstall all updates, only to find this won't solve the
issue.

Any ideas, you gurus out there? Thanks friends...

 

[Ron Lowe]

I am attempting to attach to an existing workgroup with a
new wired laptop. I can see the workgroup and have
Internet access, but upon clicking on the workgroup
accessing receive the error ""workgroup" is not
accessible. You might not have permission..." I can ping
each workstation's IP address within the workgroup, but
if I ping the computer name, I can't access them. If I
type "\\ipaddress" in the run box I see the individual
workstation's shared info, but typing "\\name" gives
error "The network path is not found"

I have tried everything in article 314067 and have reset
the IP from article 299357. The correct
service "Computer Browser" is running, and have tried
disabling IPSec. I have shared everything. Other
computers and wireless laptops attaching to the access
point this laptop is using have access, eliminating any
outside hardware devices possibly causing the issue.

It seems there may be some corruption somewhere, and am
considering reinstalling Windows XP Home on top of the
existing install, but I don't want to go this route and
reinstall all updates, only to find this won't solve the
issue.

Any ideas, you gurus out there? Thanks friends...

1) Ensure NetBIOS over TCP/IP is enabled on the machine;

2) Go to a command prompt, and do an "ipconfig /all"
and report the 'Node Type'.

 

[Ron Lowe]

< takes liberty of copying e-mail reply to the group >
Best to reply to the newsgroup.

Anyways,

The node type is listed as "Peer-to-Peer"

This is the 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.

Then re-boot.

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