Accesing Network resources on a WLAN

Active Directory
Microsoft Access
Microsoft Office
Microsoft Windows
Network protocols
Networking services
Patch management
SQL Server
I created a small office network between five computers (a WLAN actually), four of which I installed from scratch. The fifth, which I didn't install the OS (Windows XP) myself, can be seen in the workgroup under Microsoft Windows Networks form other computer, but an attempt to access it fails, with "The network path not found" prompt. On this system itself, the workroup can be seen but an attempt to access it gives this prompt: "//XXXXHOME is not acessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions" "The list of servers for this workgroup is not currently available". How do I get to acess the workgrup from this computer? I'm using an administrative account!

Answer Wiki

Thanks. We'll let you know when a new response is added.

(1) Have you activated file/printer sharing for any resources on the workstation in question? At least one folder needs to be designated as a shared resource so you can attach to it.
(2) If file sharing doesn’t resolve the problem, I would try connecting to it via a wired connection first just to prove whether it’s the workstation or the wireless network that’s causing the problem. Since the other devices share wirelessly, I’d be more inclined to expect a problem on the workstation.

Help us all learn from your experience – please be sure and let us know what you discover!
–Bob Young

Discuss This Question: 6  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • BobYoung
    Second response: Lance01, I just read your message again, and I see that you also can't seem to join the workgroup from that pesky workstation. Sometimes this problem can be resolved by changing its workgroup, restarting the computer, changing the workgroup back to the correct one, and restarting again if necessary. --Bob Young
    0 pointsBadges:
  • Joco1141
    turn on file sharing and disable the firewall for the vpn connection. are you using a radius server on the vpn or pptp ? check the config just because you got an ip address down't mean you can still access the computer till you share resources with the others and create an account you can log in with
    0 pointsBadges:
  • Richl01
    things to check 1. Firewall turn off for TS 2. does it have a IP Address and is it the same network. 3. is the NIC functional with correct drivers. 4. the version of winXP 5. can you conect to the admin share servernamec$ check these and tell us if they work.
    0 pointsBadges:
  • J88tru
    On W2000, WS2003 and XP, you must be an authorized user on the target PC. Before you can access a resource on another computer using Windows Networking, file/printer sharing must be on, and the computers must have the same Workgroup ID. Sometimes, even after you do this, you still will be unable to reach resources in an established Workgroup. This is fairly common. Workgroups use NetBIOS, and the tables must simply be populated. Occasionally, this can be cured by "joining" a new faux workgroup on the problem computer, rebooting, and then joining the correct workgroup again (with the required reboot). Are you using a 3rd Party personal firewall, such as Zone Alarm - if so, go to "Firewall"/Zones tab and make sure your Ethernet card is in the "trusted" zone ... If it is in Internet Zone, LEFT click Internet and change it to "trusted". ZA and similar products often block ports (such as port 139) that are associated with NetBIOS. If that does not work, make a note of the IP address of one of the computers that has joined the workgroup. Go to a Command prompt (Start/Run cmd). Make sure you can ping it from your problem PC, "ping 'ip address'>". (If not you may have connectivity or firewall issues on either machine.) Next, type the command, "nbtstat -A 192.168.1.xx" (where the correct IP address has been substituted for 192.168.0.xx). (Rarely, you may need to do this from the target PC, just use the problem PC's IP address.) Another trick that can bypass the workgroup name issue altogether is to open Windows Explorer and in the address line, type the "name" of the remote computer and the share resource, thus: "OthrPCSharedFolder". In a few cases, typing the ip address directly will work: (or .whatever). In either case, you will be prompted for your user/password credentials. Be sure to check the "remember password" box to avoid this annoyance, or uncheck it for better security. (I know you are surely behind at least a NAT router for security.) Hope this helps. NetBIOS issues like this are really maddening. One last tip: sometimes NetBIOS discovery takes a little time to propagate. Eventually, as your problem machine is added to the NetBIOS tables, you will have total access. Good Luck. JTRU
    0 pointsBadges:
  • Paul144hart
    As a sanity check, ping one of the other computers by its IP address, it there is an error pinging, you'll need to solve the connection first. -Paul
    0 pointsBadges:
  • Ouobacrsbf
    you must check some certain things like: 1.ensure that the computer is in the same Workgroup as the others 2.the network in which the computer is, must correspond to the current network on the others copmuters. 3.Also,your WLAN, in which mode does it work? infrastructure or ad'hoc. 4. there is another important thing, this is common in Win XP peer 2 peer network; there are local policies which prevent access from and to a computer. you must set these policies. go to Administrative Tools and open Local Security Policy, under security settings select Local policies then user right assignment and enable "access this computer from network" also in security options,scroll down you will see many entries :network access.... you can make changes and allow to browse your workgroup.
    0 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: