Version: 2008
Advanced Search
advertisement
advertisement
Click Here

Forum display:

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

by Recoloniser - 6/2/09 6:02 AM
Post 16 of 23

Test

by Recoloniser - 6/7/09 6:08 PM In reply to: Sorry. by R. Proffitt Moderator

Bob, BTW I _did_ perform the test you suggested, but it didn't do any good.

Post 17 of 23

The next test is to open a command line.

by R. Proffitt Moderator - 6/7/09 6:12 PM In reply to: Test by Recoloniser

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

Post 18 of 23

Result

by Recoloniser - 6/7/09 6:22 PM In reply to: The next test is to open a command line. by R. Proffitt Moderator

NET VIEW yields:

"System error 1 has occurred.

Incorrect function."

Post 19 of 23

I only encountered that one years ago with

by R. Proffitt Moderator - 6/7/09 6:38 PM In reply to: Result by Recoloniser

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

Post 20 of 23

In sequence

by Recoloniser - 6/7/09 6:48 PM In reply to: I only encountered that one years ago with by R. Proffitt Moderator

I'll take those in sequence:

- Norton has never been near this machine, nor has McAfee; the machine has seen security products from AVG, PCTools & NOD32
- Do you want me to remove TCP/IP & re-install?
- Never heard of SFCure; hasn't been anywhere near this machine
- pinged localhost: no problems there

Post 21 of 23

That's progress.

by R. Proffitt Moderator - 6/7/09 6:58 PM In reply to: In sequence by Recoloniser

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

Post 22 of 23

More reading.

by R. Proffitt Moderator - 6/7/09 6:20 PM In reply to: Workgroup is not accessible. You might not have permission by Recoloniser

I offer the usual that I encounter today. This error happens to more people than you can imagine with about 100 solutions. Be sure you are reading from the first hit at http://www.google.com/search?hl=en&q=%22Workgroup+is+not+accessible.%22&aq=f&oq=&aqi=g7 to see what you think you would like to try.

Post 23 of 23

I followed up on the reading you suggested

by Recoloniser - 6/7/09 6:54 PM In reply to: More reading. by R. Proffitt Moderator

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.

Forum legend:
Locked Locked thread
Moderator Moderator
CNET staff CNET staff
Samsung staff Samsung staff
Norton Authorized Support team Norton Authorized Support team
AVG staff AVG staff
Windows Outreach team Windows Outreach team
Dell staff Dell staff
Intel staff Intel staff
Powered by Jive Software