Electronics & Computers Deals here!
Networking & wireless: Workgroup is not accessible. You might not have permission
Workgroup is not accessible. You might not have permission
by Recoloniser - 6/2/09 6:02 AMI have the following problem:
- I have a home network which consists of 3 desktops
- 2 of the units run XP Pro SP3, 1 unit runs Vista
- 2 of the units, the XP machines, are connected by wire to a router; the Vista machine is wirelessly connected to the router
- all 3 units connect to the internet w/o a hitch
- 1 XP desktop and the Vista unit can see each other in the workgroup I've defined and can share files and printers w/o any problems at all
- the other XP desktop can see the workgroup, but cannot open it; you get the error message as in the subject title of this thread
- unfortunately, this is the main machine in the house and most of the peripheral hardware (B&W laserprinter, colour inkjet printer, 1TB external HDD) is connected to it, which means that all of that stuff is inaccessible to the other users!
I'm more or less at my wits' end. It all used to work seamlessly and suddenly, from one day to the next, it went pear-shaped. I'm running virus and spyware scans from just about every package I can lay my hands on to discover whether that causes the problem, so far completely w/o any success at all.
Can anybody please, please, shed some light on this?
Just the basics.
by R. Proffitt
- 6/2/09 6:10 AM
In reply to: Workgroup is not accessible. You might not have permission by Recoloniser
I see you have browsing of the network working but no where did I see you write about the accounts.
IN SHORT -> If your account is called bob then bob must have an account on the machine he wants to attach to or that message should occur.
In closing. Its a common issue so let's see what you are doing about accounts.
Bob
Accounts
by Recoloniser - 6/2/09 6:30 AM In reply to: Just the basics. by R. Proffitt
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?
So browsing is dead?
by R. Proffitt - 6/2/09 6:39 AM
In reply to: Accounts by Recoloniser
That's a sign of a firewall. Again my reading of the post does not find what firewall is in use. And I will not offer how to configure your firewall to allow network shares and browsing (well discussed area.)
There is also issues if you are doing this over WIFI. Let me toss out the name of this so you can say it's not or is in play. "Client Isolation."
There are also SERVICES that must be running for all this to work and the firewall in the router set to allow browsing and network shares.
I know it sounds cruel or short but I can't ask all the questions as this is not tech support. This is more like someone that stopped to help you change the tire. They may not know where the spare tire is so you go get it for them.
-> Yes it's a common headache of networking with a long list of things to check. The problem I'm running into today is that many owners tinker with services, run registry cleaners and install firewalls (that they don't know how to configure.) Here's the drill:
1. Set services back to default. Read http://www.blackviper.com/WinXP/servicecfg.htm
2. Set the firewall to allow networking. (sorry, but as there are dozens of firewalls and versions of each I ask you to figure this out.)
3. Set the name of the network to be a single word.
4. KNOW the accounts issue. This is also a stumbling block for many new networkers as it can be the cause of the browse issue. My patience is getting thin on the accounts issue.
Bob
Accounts
by Recoloniser - 6/7/09 7:20 AM In reply to: So browsing is dead? by R. Proffitt
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
Accounts is simple.
by R. Proffitt - 6/7/09 7:45 AM
In reply to: Accounts by Recoloniser
You are logged in as "somebody". Now over at the other machine you log in as that somebody.
As many forget these accounts can expire and then what worked before stops working. This is why we do the log in test.
-> Have you done the log in as "somebody" test? And repeat for each account name that you use.
Bob
PS. To disable password expiring.
by R. Proffitt - 6/7/09 7:56 AM
In reply to: Accounts is simple. by R. Proffitt
http://www.astahost.com/info.php/Disable-Password-Expiration-Xp_t8082.html
Accounts
by Recoloniser - 6/7/09 10:07 AM In reply to: Accounts is simple. by R. Proffitt
Rob, thanx. However, I'm a bit puzzled. I cannot even see myself on my own machine in the network and since I'm always logged in as myself on my own machine, there can hardly be any confusion about my user name can there?
The browser service and more.
by R. Proffitt - 6/7/09 11:37 AM
In reply to: Accounts by Recoloniser
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
Just so we're clear.
by R. Proffitt - 6/7/09 11:48 AM
In reply to: Workgroup is not accessible. You might not have permission by Recoloniser
The network browsing could be as simple as the MASTER BROWSER is not your machine and your account on the other PC has an expired password.
It would be a shame to go so long without testing if you can login on each machine that is on the network.
There is another item and that is these firewalls. It is not good enough to disable some like Zone Alarm as I've caught them still working even when they are disabled. I never offer how to configure a firewall as that would be duplicate web pages and manuals. The short answer here is to allow local traffic.
Bob
Shares etc
by Recoloniser - 6/7/09 12:21 PM In reply to: Just so we're clear. by R. Proffitt
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
Which I can duplicate this error with ease.
by R. Proffitt - 6/7/09 1:02 PM
In reply to: Shares etc by Recoloniser
Either you have a firewall up (router or somewhere), someone turned on client isolation (see google) or it's the same old account issue.
I'm a little dazed here. Why isn't the login check done on each machine?
To recap.
Let's say I'm bob on my machine. I walk to each machine in the workground and log out who's there then log in as bob for a test. Seems simple yet I've seen 20 and more posts in long drawn discussions and this one simple test is avoided.
Why is that?
Bob
Accounts
by Recoloniser - 6/7/09 1:43 PM In reply to: Which I can duplicate this error with ease. by R. Proffitt
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.
Sorry.
by R. Proffitt - 6/7/09 2:04 PM
In reply to: Accounts by Recoloniser
There is the issue of the Master Browser which may not be on your machine. I have offered a simple test and it appears it will not be done.
Again, the master browser (a windows networking thing) may not be on your machine so the account issue can be still in play.
I'll unsubscribe and let others try.
Good luck,
Bob
I don't understand!
by Recoloniser - 6/7/09 6:04 PM In reply to: Sorry. by R. Proffitt
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?
| Forum legend: | |
 |
Locked thread |
 |
Moderator |
 |
CNET staff |
 |
Samsung staff |
 |
Norton Authorized Support team |
 |
AVG staff |
 |
Windows Outreach team |
 |
Dell staff |
 |
Intel staff |
