XP Cannot connect to workgroup

[Jay]

This is my exact problem, yet the fix didn't help one bit.

You cannot access shared files and folders or browse
computers in the workgroup
Applies To
This article was previously published under Q318030
SYMPTOMS
On Windows XP-based computers that are configured as
members of a workgroup in a peer-to-peer network
environment, you may experience one or more of the
following behaviors:
You cannot access shared folders or files.
You cannot locate other computers in the workgroup.
You receive the following error message when you double-
click the workgroup in My Network Places:

Workgroup Name is not accessible. You may not have
permission to use this network resource.
CAUSE
This behavior may occur if both the following conditions
are true:
NetBIOS over TCP/IP is not turned on (enabled) on one or
more computers in the workgroup.
The Computer Browser service is not started or is turned
off on one or more computers in the workgroup.
RESOLUTION
To resolve this issue, make sure that NetBIOS over TCP/IP
is turned on and the Computer Browser service is running
on each computer in the workgroup. To do this, follow
these steps.
Step 1: Turn on NetBIOS over TCP/IP
Click Start, click Control Panel, and then click Network
and Internet Connections.
Click Network Connections.
Right-click Local Area Connection, and then click
Properties.
Click Internet Protocol (TCP/IP), and then click
Properties.
Click the General tab, and then click Advanced.
Click the WINS tab.
Under NetBIOS setting, click Enable NetBIOS over TCP/IP,
and then click OK two times.
Click Close to close the Local Area Connection Properties
dialog box.
Close the Network Connections window.
Step 2: Start the Computer Browser service
Click Start, right-click My Computer, and then click
Manage.
Double-click Services and Applications.
Double-click Services.
In the right pane, right-click Computer Browser, and then
click Start.
Close the Computer Management window.
MORE INFORMATION

 

[Hans-Georg Michna]

This is my exact problem, yet the fix didn't help one bit.

Workgroup Name is not accessible. You may not have
permission to use this network resource.

Jay,

yes, that KB article names only a few possible causes, but there
are more.

Please have a look at http://www.michna.com/kb/wxnet.htm.

Hans-Georg

 

[Chuck]

This is my exact problem, yet the fix didn't help one bit.

Jay,

In addition to checking the items listed in Q318030, you should also check
authentication / authorisation and firewalls.

Your statement is a bit vague, I understand your frustration, but you really
should supply some details about your setup, and your problem.

How to Compose a Good Newsgroup Post


How to Act Smart on Usenet


Getting Your Post Noticed - and Answered
http://www.microsoft.com/presspass/features/2001/Mar01/Mar27pmvp.asp

Your solution could vary, depending upon what OS is on the computers on your
LAN.

On any XP Pro computer, check to see if Simple File Sharing (Control Panel -
Folder Options - View - Advanced settings) is enabled or disabled. With XP Pro,
you need to have SFS properly set on each computer.

With XP Pro, and SFS disabled, check the Local Security Policy (Control Panel -
Administrative Tools). Under Local Policies - Security Options, look at
"Network access: Sharing and security model", and ensure it's set to "Classic -
local users authenticate as themselves".

With XP Pro, and SFS disabled, if you set the above Local Security Policy to
"Guest only", enable the Guest account, using Start - Run - "cmd" - type "net
user guest /active:yes" in the command window. If "Classic", setup and use a
common non-Guest account on all computers. Whichever account is used, give it
an identical, non-blank password on all computers.

For XP Home, and for XP Pro with Simple File Sharing enabled, make sure that the
Guest account is enabled, on each computer. Enable Guest with Start - Run -
"cmd" - type "net user guest /active:yes" in the command window.

Do any of the computers have a software firewall (ICF / WF, or third party)? If
so, you need to configure them for file sharing, by opening ports TCP 139, 445
and UDP 137, 138, 445, by enabling the File and Printer Sharing exception, and /
or by identifying the other computers as present in the Local (Trusted) zone.
Firewall configurations are a very common cause of (network) browser, and file
sharing, problems.

And Jay, please don't contribute to the spread and success of email address
mining viruses. Learn to munge your email address properly, to keep yourself a
bit safer when posting to open forums. Protect yourself and the rest of the
internet - read this article.
http://www.mailmsg.com/SPAM_munging.htm

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Guest]

Hi I had a similar problem try this site it has information to install Netbuei
http://www.wown.com/articles_tutorials/winxpnet.html

 

[Chuck]

Hi I had a similar problem try this site it has information to install Netbuei
http://www.wown.com/articles_tutorials/winxpnet.html

Gordon,

Windows networking is built around TCP/IP, and uses NetBIOS Over TCP/IP as an
interface to file and printer sharing.

If there's a problem with TCP/IP, or with NBT, NetBEUI will provide a
workaround. But it will also add needless complexity, and may cause long term
stability problems.

If the problem experienced by the OP is caused by authentication /
authorisation, NetBEUI won't resolve anything.

Fix the problem. Don't add to it.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.