Windows Setup Notes
name and address
created oct 18, 2010

Windows problem: You might not have permission to use this network resource

You might not have permission to use this network resource.

This is probably the most common Windows networking problem. Generally, it means that Windows cannot figure out how to reach the desired location. There are many possible causes for this. Unfortunately, the solutions are slightly different for each version of Windows. The solutions below are for XP with Service Pack 3.

The first step in Windows is always to reboot. The steps below assume you've tried this, and it didn't help.

The network settings might have changed

A change to the network settings on Windows or a change in the network itself invalidates the path Windows wants to take. For example, your network administrator might have changed the gateway address, or a server may be down.

Solution

  1. Check the Network Settings (Start - cmd - ipconfig) to make sure that each network card has an IP address, default gateway, and subnet mask that make sense. If they're wrong, fix them in the control panel. If your Default Gateway is blank or incorrect, your computer will not be able to reach the destination.
  2. Make sure you're in the correct workgroup (In XP: Control panel - System - Computer name).
  3. In My Network Places, click Refresh, then View workgroup computers. If the path is bad, it should disappear.
  4. Create the new Network Place (Network Connections - My network places - Add a network place) Where the Add Network Place Wizard says "Internet or network address:", browse for the location or type the Share Name (e.g., \\syphilis\shared or \\diarrhea\home ).
  5. If this doesn't work, enter the IP address of the computer you want to connect to (e.g., \\192.168.1.2\home or \\10.2.2.2\homes ). If this works but the name doesn't, it means you have the wrong DNS server in your network configuration, or your DNS server is not working.
  6. Reboot the Windows machine.

Access might be blocked

Solution

Disable Windows firewall and Norton firewall if present.

A Windows update might have changed your configuration.

Solution

This is from http://support.microsoft.com/kb/913628

  1. Click Start, Run, type regedit in the Open box, and then click OK.
  2. Locate and then double-click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
  3. In the right pane, double-click restrictanonymous.
  4. Make sure that the value in the Value data box is set to 0, and then click OK.
  5. Close Registry Editor.
  6. Restart the computer so the new setting takes effect.

Your DNS might have gotten messed up.

Solution

  1. Start - run - cmd
  2. Type ipconfig /flushdns and hit Enter.
  3. Type ipconfig /registerdns and hit Enter.

Permissions might be wrong

Solution

  1. Control Panel - Administrative Tools - Computer Management - Storage - Disk Management
  2. Right click on the drive causing a problem
  3. Choose Properties and click the Security tab
  4. Click the Everyone User Group. If there is no Everyone group, create one. Make sure the Permissions for Administrators boxes are checked.
  5. Click on the Allow - Full Control box and click Apply.
  6. Click OK.

The other computer might be restricting access.

This is common on XP computers that have not gotten Service Pack 2.

Solution

  1. Admin tools - Local Security Policy - Local Policies
  2. Lick on Admin Tools - Local Security Policy - Local Policies - User Rights Assignment - Access this computer from the network
  3. Add Everyone (this must be typed in explicitly).

Windows misconfiguration

Solution According to http://support.microsoft.com/default.aspx?scid=kb;en-us;318030 , any one of the following can prevent access to shared files.

  1. NetBIOS over TCP/IP is off This is essential if you're running a small private network with no name server. To activate NetBIOS over TCP/IP, do the following:
    1. Control Panel - Network Connections
    2. Right-click on the network interface icon that represents the network your destination is on (there will be one icon for each network card or virtual interface).
    3. Properties
    4. Scroll down in the menu to Internet Protocol (TCP/IP) or TCP/IP version 4 (not 6). Click on it until it turns blue.
    5. Properties - Advanced - WINS
    6. NetBIOS Setting: Enable NetBios over TCP/IP
  2. The Computer Browser service is not running on one or more computers in the network. Administrative Tools - Services - Computer Browser - Should be Automatic. If not, click "Start the service" .
  3. File and Print Sharing for Microsoft Networks is not installed. Control panel - Network connections - Right click on the appropriate network interface icon - File and Printer Sharing for Microsoft Networks in the list should be checked. If not, highlight it and click Install.

Other

Unlikely as it may seem, it could also actually be a password or permissions problem. Windows always sends a username and password, whether you enter one or not. Often, Windows guesses wrong. See linuxsetup38c.html. If you're on a Samba network, your system administrator will be able to tell from the logs if your computer is sending bad passwords.

Also, check the obvious: make sure the folder you're trying to access is a shared folder. Right-click on folder icon - Sharing and Security - Follow the instructions in the Sharing Properties window that pops up.

Back