Re: Can't access shared folders

From: uzieagle (uzieagle_at_discussions.microsoft.com)
Date: 12/08/04


Date: Wed, 8 Dec 2004 12:35:02 -0800

I tried your suggestions and I have the same problem. What I find realy
strange about this situation is that I can access the root of C on the
machine I need access to. I can even edit anything in the root directory.
However, when I try to access a subfolder is when I get that error.

"Chuck" wrote:

> On Wed, 8 Dec 2004 09:01:05 -0800, "uzieagle"
> <uzieagle@discussions.microsoft.com> wrote:
>
> >Here is my situation:
> >
> >We have three machines. Two had XP Pro and one was running Win98se. All
> >computers could see each other and access all shared drives. We recently
> >rebuilt the Win98 machine and put a fresh install of XP Pro Sp2 on it. The
> >new machine can see the other two and access their shared drives. However,
> >the other two cannot access the new machine's shared drives. We can see the
> >drive and access the root folder but we cannot access any of the subfolders.
> >We get an error that states "\\Front\C\Peach is not accessible. You might not
> >have permission to use this networ resource. Contact the administrator of
> >this server to find out if you have access permissions. Access is denied."
> >
> >I have tried with and without Simple TCP/IP enabled. All machines have SP2
> >installed (which is where I think my first mistake may have been). We have
> >no other software firewalls installed. We use a Lynksys router/hub. All
> >machines have access to the internet.
>
> Maybe by "Simple TCP/IP" you mean Simple File Sharing? SFS is not completely
> simple - you need to make other settings too.
>
> On XP Pro with SFS disabled, check the Local Security Policies (Control Panel -
> Administrative Tools). Under Local Policies - Security Options, look at
> "Network access: Sharing and security model", and ensure it's set to "Classic -
> local users authenticate as themselves".
>
> On XP Pro with SFS disabled, if you set the above Local Security Policy to
> "Guest only", enable the Guest account, using Start - Run - "cmd" - type "net
> user guest /active:yes" in the command window. If "Classic", setup and use a
> common non-Guest account on all computers. Whichever account is used, give it
> an identical, non-blank password on all computers.
>
> On XP Pro with Simple File Sharing enabled, make sure that the Guest account is
> enabled, on each computer. Enable Guest with Start - Run - "cmd", then type
> "net user guest /active:yes" in the command window.
>
> On XP Pro, if you're going to use Guest authentication, check your Local
> Security Policy (Control Panel - Administrative Tools) - User Rights Assignment,
> on the XP Pro computer, and look at "Deny access to this computer from the
> network". Make sure Guest is not in the list.
>
> Does the problem computer have Windows Firewall enabled? If so, you need to
> configure it for file sharing, by enabling the File and Printer Sharing
> exception. Firewall configurations are a very common cause of (network)
> browser, and file sharing, problems.
>
> Also, look at registry key [HKLM\System\CurrentControlSet\Control\Lsa], value
> restrictanonymous, on each computer.
> <http://www.microsoft.com/windows2000/techinfo/reskit/en-us/default.asp?url=/windows2000/techinfo/reskit/en-us/regentry/46688.asp>
> <http://www.jsifaq.com/subf/tip2600/rh2625.htm>
> http://support.microsoft.com/?id=246261
> http://support.microsoft.com/?id=296403
>
> The above articles refer to Windows 2000. Remember WinXP is NT V5.1, and Win2K
> is NT V5.0.
>
> Have you used the Registry Editor before? If not, it's a scary tool, but it's
> pretty simple once you get used to it. Here are a couple articles that might
> help:
> <http://www.microsoft.com/windowsxp/home/using/productdoc/en/default.asp?url=/windowsxp/home/using/productdoc/en/tools_regeditors.asp>
> <http://www.annoyances.org/exec/show/registry>
>
> Just remember to backup the key (create a registry patch) for
> [HKLM\System\CurrentControlSet\Control\Lsa] before making any changes, if
> appropriate.
>
> From the Annoyances article:
> You can create a Registry patch by opening the Registry Editor, selecting a
> branch, and choosing Export from the File menu. Then, specify a filename, and
> press OK. You can then view the Registry patch file by opening it in Notepad
> (right-click on it and select Edit). Again, just double-click on a Registry
> patch file (or use Import in the Registry Editor's File menu) to apply it to the
> registry.
>
> --
> Cheers,
> Chuck
> Paranoia comes from experience - and is not necessarily a bad thing.
>



Relevant Pages

  • Re: Cant access shared folders
    ... >> On XP Pro with SFS disabled, if you set the above Local Security Policy ... >> configure it for file sharing, by enabling the File and Printer Sharing ... >> Have you used the Registry Editor before? ... >> You can create a Registry patch by opening the Registry Editor, ...
    (microsoft.public.windowsxp.network_web)
  • Re: XP unable to access networked computer
    ... >lost access to the network and file sharing. ... Have you used the Registry Editor before? ... You can create a Registry patch by opening the Registry Editor, ...
    (microsoft.public.windowsxp.network_web)
  • Re: MSHOME -You do not have access rights, ask admin
    ... >Laptop either hardwired to Linksys or wireless connection. ... If XP, Home or Pro? ... check to see if Simple File Sharing (Control Panel - ... Have you used the Registry Editor before? ...
    (microsoft.public.windowsxp.network_web)
  • Re: Network domain usernames and passwords
    ... Security stuff has been all setup and works great. ... Is your XP computer XP Pro? ... On XP Home, and on XP Pro with Simple File Sharing enabled, make sure that the ... Have you used the Registry Editor before? ...
    (microsoft.public.windowsxp.network_web)
  • Re: view workgroup computers--workaround
    ... > Are your XP computers running Simple, ... > uses the Guest account, as a backup to a matching non-Guest account with ... > On XP Home, and on XP Pro with Simple File Sharing enabled, make sure that the ... > Have you used the Registry Editor before? ...
    (microsoft.public.windowsxp.network_web)

Loading