old problem cannot share files on simple home network.

[-keevill-]

I have a very simple yet thoroughly frustrating problem with three computers
or running Windows XP pro. They are all part of the same workgroup -- I have
even re-made the workgroup name to ensure it is exactly the same. I have
enabled sharing on each computer for a test directory in each. They are all
in the same subnet range 192.168.0.xx

With one machine I am able to get a little bit further in that I am able to
browse the workgroup and see the other computers by name but when I try to
access the computer is I get the following error message "workgroup is not
accessible. You might not have sufficient permissions.the list of servers
for this workgroup is not currently available."

With the other machines, I cannot even see the other computers in the
workgroup. I get the above error message when I try to drill down into the
workgroup.

I have disabled the Windows firewall. (On all machines)

Each machine is connected to a small six port Switch via the normal RJ 45
LAN cables. There is no external virus software running. I can ping each
computer successfully. I am logged on as admin on each computer.

I read something about there needing to be an account of the same name with
the same password on each machine so I went ahead and made one for example
John/John.

This is real beginners stuff yet for the life of me, I cannot find the
solution.

 

[John Wunderlich]

I have a very simple yet thoroughly frustrating problem with three
computers or running Windows XP pro. They are all part of the same
workgroup -- I have even re-made the workgroup name to ensure it
is exactly the same. I have enabled sharing on each computer for a
test directory in each. They are all in the same subnet range
192.168.0.xx

With one machine I am able to get a little bit further in that I
am able to browse the workgroup and see the other computers by
name but when I try to access the computer is I get the following
error message "workgroup is not accessible. You might not have
sufficient permissions.the list of servers for this workgroup is
not currently available."

On each subnet, one computer is elected to serve as "Browse Master".
This computer maintains the list of computers on that subnet. This
message indicates that either no computer was elected as browse master
or the list that it maintains is not available. Usually errors of this
sort are traced back to a computer running a firewall. Sometimes
firewalls are hidden. For example, the CISCO VPN Client contains a
firewall that is enabled even when the client is not.

Also, make sure that at least one computer is running the "Computer
Browser" service (usually all of them are).

On each machine, bring up a command prompt window and enter the
command:
ipconfig /all
Make sure the "Node Type" is NOT P-Type (Point-to-Point)

If you have XP Pro with Simple Filesharing enabled (or XP Home), make
sure that the Guest account is enabled:
net user guest /active:yes

Try connecting from a command prompt. Sometimes the error messages are
more helpful:
net use * \\computername\sharename

To test connectivity, from a command prompt, enter the command:
nbtstat -a computername
where "computername" is the name of a networked computer (no '\\' in
front of name). Each should respond with a few lines. One (the master
browser) should contain a line with "..__MSBROWSE__." in it.
If a machine doesn't respond, look for a firewall or MS File Sharing
not being enabled.

I read something about there needing to be an account of the same
name with the same password on each machine so I went ahead and
made one for example John/John.

This would apply if you have XP Pro with Simple Filesharing disabled.
(Double-click "My Computer"-> Tools -> Folder Options -> View [Tab]
Scroll down, the last setting is "Simple File Sharing".)

If this is the case, there are two permission levels that must be met.
1) Right-click on your shared folder -> Properties -> Sharing Tab
Click on "Permissions" button and make sure the appropriate users
have permissiors.
2) Right-click on your shared folder -> Properties -> Security Tab
Make sure the appropriate users have permission to the folder.

HTH,
John

 

[-keevill-]

On each subnet, one computer is elected to serve as "Browse Master".
This computer maintains the list of computers on that subnet. This
message indicates that either no computer was elected as browse master
or the list that it maintains is not available. Usually errors of this
sort are traced back to a computer running a firewall. Sometimes
firewalls are hidden. For example, the CISCO VPN Client contains a
firewall that is enabled even when the client is not.

Also, make sure that at least one computer is running the "Computer
Browser" service (usually all of them are).

On each machine, bring up a command prompt window and enter the
command:
ipconfig /all
Make sure the "Node Type" is NOT P-Type (Point-to-Point)

If you have XP Pro with Simple Filesharing enabled (or XP Home), make
sure that the Guest account is enabled:
net user guest /active:yes

Try connecting from a command prompt. Sometimes the error messages are
more helpful:
net use * \\computername\sharename

To test connectivity, from a command prompt, enter the command:
nbtstat -a computername
where "computername" is the name of a networked computer (no '\\' in
front of name). Each should respond with a few lines. One (the master
browser) should contain a line with "..__MSBROWSE__." in it.
If a machine doesn't respond, look for a firewall or MS File Sharing
not being enabled.

I read something about there needing to be an account of the same
name with the same password on each machine so I went ahead and
made one for example John/John.

This would apply if you have XP Pro with Simple Filesharing disabled.
(Double-click "My Computer"-> Tools -> Folder Options -> View [Tab]
Scroll down, the last setting is "Simple File Sharing".)

If this is the case, there are two permission levels that must be met.
1) Right-click on your shared folder -> Properties -> Sharing Tab
Click on "Permissions" button and make sure the appropriate users
have permissiors.
2) Right-click on your shared folder -> Properties -> Security Tab
Make sure the appropriate users have permission to the folder.

HTH,

This is what finally worked for me.
To solve the problem you must add:

"NWLink IPXSPXNetBIOS Compatible Transport Protocol" to the "Network
Properties" list on each computer of the network.

The error message is misleading in that it has nothing to do with
permissions or servers or logging on as administrator. Note: To add "NWLink
IPXSPXNetBIOS Compatible Transport Protocol" open your Network Connections
as explained below:

1 - Go to Control Panel, and select "Network Connections";

2 - Right-click with your mouse your Network Connection and select
"Properties";

3 - On the "Connection Properties" screen, select the "Install" tab;

4 - On the "Select networking Component" screen select "Protocol"
double-click the Add..." Tab;

5 - On the "Select Network Protocol" screen, select "NWLink IPXSPXNetBIOS
Compatible Transport Protocol" and click the "OK" tab to install the
protocol. The steps above have to be repeated on every computer present in
the Network.


-keevill-

 

[John Wunderlich]

On each subnet, one computer is elected to serve as "Browse
Master". This computer maintains the list of computers on that
subnet. This message indicates that either no computer was
elected as browse master or the list that it maintains is not
available. Usually errors of this sort are traced back to a
computer running a firewall. Sometimes firewalls are hidden.
For example, the CISCO VPN Client contains a firewall that is
enabled even when the client is not.

Also, make sure that at least one computer is running the
"Computer Browser" service (usually all of them are).

On each machine, bring up a command prompt window and enter the
command:
ipconfig /all
Make sure the "Node Type" is NOT P-Type (Point-to-Point)

If you have XP Pro with Simple Filesharing enabled (or XP Home),
make sure that the Guest account is enabled:
net user guest /active:yes

Try connecting from a command prompt. Sometimes the error
messages are more helpful:
net use * \\computername\sharename

To test connectivity, from a command prompt, enter the command:
nbtstat -a computername
where "computername" is the name of a networked computer (no '\\'
in front of name). Each should respond with a few lines. One
(the master browser) should contain a line with "..__MSBROWSE__."
in it. If a machine doesn't respond, look for a firewall or MS
File Sharing not being enabled.

I read something about there needing to be an account of the
same name with the same password on each machine so I went ahead
and made one for example John/John.

This would apply if you have XP Pro with Simple Filesharing
disabled. (Double-click "My Computer"-> Tools -> Folder Options
-> View [Tab] Scroll down, the last setting is "Simple File
Sharing".)

If this is the case, there are two permission levels that must be
met. 1) Right-click on your shared folder -> Properties ->
Sharing Tab Click on "Permissions" button and make sure the
appropriate users have permissiors.
2) Right-click on your shared folder -> Properties -> Security
Tab Make sure the appropriate users have permission to the
folder.

HTH,

This is what finally worked for me.
To solve the problem you must add:

"NWLink IPXSPXNetBIOS Compatible Transport Protocol" to the
"Network Properties" list on each computer of the network.

The error message is misleading in that it has nothing to do with
permissions or servers or logging on as administrator. Note: To
add "NWLink IPXSPXNetBIOS Compatible Transport Protocol" open your
Network Connections as explained below:

1 - Go to Control Panel, and select "Network Connections";

2 - Right-click with your mouse your Network Connection and select
"Properties";

3 - On the "Connection Properties" screen, select the "Install"
tab;

4 - On the "Select networking Component" screen select "Protocol"
double-click the Add..." Tab;

5 - On the "Select Network Protocol" screen, select "NWLink
IPXSPXNetBIOS Compatible Transport Protocol" and click the "OK"
tab to install the protocol. The steps above have to be repeated
on every computer present in the Network.


-keevill-

I suppose adding another transport is one way to solve the problem...
Although if NetBIOS-over-TCPIP (NetBT) is enabled on all machines, this
approach shouldn't be necessary.

-- John