Networking & wireless forum: Workgroup is not accessible. You might not have permission

Bob, thnx for the reply. I realise I haven't been complete in my description of the problem:
Normally when you try to to browse a workgroup in the network, at the very least you can see the machine you're working currently from, if you have declared it as a member of the workgroup, that is, which I have done. Well, I cannot even see myself, because I cannot get access to the workgroup at all. So to be clear, it's not just that I cannot access from another pc in the network, I cannot get access to the workgroup from the main pc in the house.

The other thing I'd realised is that there is an additional piece of information that may be relevant. The complete error message when I try to open up the workgroup from the main pc is:

"<Workgroup> is not accessible. You might not have permission to use this resource. Contact the administrator of this server to find out if you have access permissions.

Incorrect function."

Does that ring a bell with anyone?

Bob, far be it from me to try your patience on accounts or anything else for that matter. To go thru you points:
- Firewall: has been completely disabled in my desperation, even tho' the network worked fine earlier with it enabled
- WIFI: it's one of the wire connected pcs that's the problem here
- Services: have been reset to default
- Where do I go to find out about accounts? NB: I haven't tinkered wiht any account anywhere, but my file & printer sharing ceased to work overnight anyway

http://www.astahost.com/info.php/Disable-Password-Expiration-Xp_t8082.html

Sorry but I can't find where you completed the login test on the machine you want to connect to the share.

As to why your machine does not show, tell the forum about the share you created.
Bob

Bob,

To be specific: I have 3 machines

- 1 is called Study4 and runs XP Pro SP3; it is connected to the workgroup FAMILY
- 1 is called Playroom_3 and runs XP Pro SP3; it is connected to the workgroup FAMILY
- 1 is called Pieps; it runs Vista and it is connected to the workgroup FAMILY
- Pieps and Playroom_3 have complete file and printer sharing
- Pieps and Playroom_3 can see that a machine called Study4 exists in the workgroup FAMILY but there's no way they can get at it
- Study4 can see that a workgroup called FAMILY exists in Microsoft Windows Network, but it cannot penetrate inside the workgroup, not even to see itself there

Bob,

I didn't think this could be the issue, simply because it already fails at the first test: the machine itself is not visible in Microsoft Windows Networking in its own Windows Explorer window. So you don't need to go to another machine to test whether you can see it when everyone is logged in under the same name, when the machine cannot even see itself.

Also, previously, networking worked just fine when I was logged in as 'Frank' on 'Study4', my wife was logged in as 'Caroline' on 'Playroom_3' and my youngest daughter was logged in as 'Eline' on 'Pieps'.

Nevertheless, I did as you suggested, but no joy I'm afraid. The result is exactly the same as before.

I don't understand why I need to go to other machines when the machine cannot even see itself! I would understand if the machine _could_ see itself, but could not be detected from other nodes in the network, but that is not the case here.

Anyway, where do I find the MASTER BROWSER?

The command we try next is NET VIEW (read http://www.ss64.com/nt/net_share.html )

As we spent so much time on getting the password and account check done I must reduce my replies to short as possible.
Bob

Norton. You claim you disabled the firewall but was Norton ever on this machine? Actually any expired protection software or damaged "stack" will provoke this error. Yes, Mcafee has done this too.

Research how to remove and reinstall TCPIP in XP. Here's some starter material.

Be aware I also know of trouble with SFCure and other such things. Share if you tried such.

There are dozens of reasons for this failure. Let's nail down one common cause. No "localhost". Try this.

ping localhost on a command line and if it fails, fix your hosts file.
Bob

Pinging localhost removed a few items.

That net view failure is the best clue. The most common cause is a hijacked winsock (tcpip stuff.)

http://www.google.com/search?hl=en&q=xp+remove+reinstall+tcpip
Bob

I followed this one:

"Everyone having this problem should follow this...
You must have administrator rights to do this.
Enable the IPX/SPX protocol and follow all instructions.
To enable file and print sharing on the IPX/SPX protocol
Only perform this procedure if your home or small office computers are connected directly to the Internet through individual connections or using a DSL or cable modem connected to an Ethernet network hub.

1. Open Network Connections.
2. In Local Area Network, Right click on top of your connection and select Properties, click Install.
3. In Select Network Component Type, click Protocol, and then click Add.
4. Click NWLink IPX/SPX/NetBIOS Compatible Transport Protocol, click OK, and then click Close.
5. In Network Connections, on the Advanced menu (on top menu bar), click Advanced Settings.
6. On the Adapters and Bindings tab, under Connections, click the local area connection on which you are enabling IPX/SPX file and print sharing.
Under Bindings for Local Area Connection, under File and Printer Sharing for Microsoft Networks, clear the Internet Protocol (TCP/IP) check box, and then click OK."

and it seems to have done the trick! I'm going to keep my fingers crossed and hope it lasts.

Thanx for the advice, hope I haven't bored you too much.