"Steve Winograd [MVP]" wrote:

> In article <OdymRZE9EHA.2***@TK2MSFTNGP14.phx.gbl>, "Eric Cross [MVP]"
> <encr***@eudoramail.com> wrote:
> >"Diane" <Di***@discussions.microsoft.com> wrote in message
> >news:F827BE35-78D7-4BA5-91AF-4B877F4B20E0@microsoft.com...
> >>I have a home network that has four PCs (all XP) attached.  PC#1 has a
> >> printer attached that I would like to access from the pther three PCs.
> >> Although I can "see" PC#1 from the other PCs, when trying to access PC#1
> >> from
> >> any other PC by clicking on it in the the Computers Near Me area in My
> >> Network Places, I get an error message
> >>
> >> "PC#1 is not accessible.  You might not have permission to use this
> >> network
> >> resource.  Contact the administrator of this server to find out if you
> >> have
> >> access permissions.
> >>
> >> Logon failure: the user has not been granted the requested logon type at
> >> this computer"
> >>
> >> I have definately "shared" the printer, but I guess I missed another step
> >> somewhere - and I cannot remember what i did to get the other three PCs to
> >> see each other (the all work fine).
> >>
> >> Any help would be greatly appreciated.
> >>
> >> Regards,
> >> Diane
>
> >Greetings Diane,
> >
> >Are you running Windows XP Pro?
> >
> >Check the Group Policy settings on the XP Pro computer.
> >
> >1. Run secpol.msc.
> >
> >2. Click Local Policies.
> >
> >3. Click User Rights Assignments.
> >
> >4. Click "Access this computer from the network" and make sure that the
> >Everyone group is included.
> >
> >5. Click "Deny access to this computer from the network" and make sure that
> >the Everyone group is NOT included.
>
> The problem is on PC#1.  If it runs XP Professional, follow the steps
> that Eric gave.  If it runs XP Home Edition:
>
> 1. Download and install the Windows 2003 Server Resource Kit Tools
> from http://go.microsoft.com/fwlink/?LinkId=4544 .
>
> 2. Click Start | All Programs | Windows Resource Kit Tools | Command
> Shell.
>
> 3. Type these lines at the command prompt.  The second and third
> commands are case-sensitive, so type them exactly as shown.  Note the
> "+r" in the second one and the "-r" in the third one:
>
>    net user guest /active:yes
>    ntrights +r SeNetworkLogonRight -u Guest
>    ntrights -r SeDenyNetworkLogonRight -u Guest
> --
> Best Wishes,
> Steve Winograd, MS-MVP (Windows Networking)
>
> Please post any reply as a follow-up message in the news group
> for everyone to see.  I'm sorry, but I don't answer questions
> addressed directly to me in E-mail or news groups.
>
> Microsoft Most Valuable Professional Program
> http://mvp.support.microsoft.com
>

>Hi, I have a similar issue: My laptop can ping my desktop and visa versa.  I
>see "Mshome" under "Microsoft Windows Network" on the laptop.  When I double
>click on it  I get the following error: "Mshome is not accessible. 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 network path
>was not found".
>
>The Desktop is Windows XP Home and the Laptop XP Pro.
>
>I followed the instructions above on using the windows resource kit but this
>isn't solving the problem.  I ran regedit and set restrictanonymous to "0". 
>I even re-ran the home network wizard and am still getting the same error.
>
>Now what?

"Chuck" wrote:

> On Sat, 9 Dec 2006 11:41:00 -0800, Keith <Ke***@discussions.microsoft.com>
> wrote:
>
> >Hi, I have a similar issue: My laptop can ping my desktop and visa versa.  I
> >see "Mshome" under "Microsoft Windows Network" on the laptop.  When I double
> >click on it  I get the following error: "Mshome is not accessible. 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 network path
> >was not found".
> >
> >The Desktop is Windows XP Home and the Laptop XP Pro.
> >
> >I followed the instructions above on using the windows resource kit but this
> >isn't solving the problem.  I ran regedit and set restrictanonymous to "0". 
> >I even re-ran the home network wizard and am still getting the same error.
> >
> >Now what?
>
> Your symptoms are not at all the same as the Oops.  One of the most common
> causes of your problem would be a misconfigured or overlooked personal firewall,
> or other security component. There are several other possibilities too, and any
> might be the cause of your problem. Read this article with an open mind.
> <http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
> http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html
>
> For more direct help, provide "browstat status",  "ipconfig /all", "net config
> server", and "net config workstation", from each computer, and diagnose the
> problem.  Read this article, and linked articles, and follow instructions
> precisely (download browstat!):
> <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
> http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp
>
> --
> Cheers,
> Chuck, MS-MVP [Windows - Networking]
> http://nitecruzr.blogspot.com/
> Paranoia is not a problem, when it's a normal response from experience.
> My        email         is          AT         DOT
>    actual       address    pchuck       mvps        org.
>

>"Chuck" wrote:
>
>> On Sat, 9 Dec 2006 11:41:00 -0800, Keith <Ke***@discussions.microsoft.com>
>> wrote:
>>
>> >Hi, I have a similar issue: My laptop can ping my desktop and visa versa.  I
>> >see "Mshome" under "Microsoft Windows Network" on the laptop.  When I double
>> >click on it  I get the following error: "Mshome is not accessible. 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 network path
>> >was not found".
>> >
>> >The Desktop is Windows XP Home and the Laptop XP Pro.
>> >
>> >I followed the instructions above on using the windows resource kit but this
>> >isn't solving the problem.  I ran regedit and set restrictanonymous to "0". 
>> >I even re-ran the home network wizard and am still getting the same error.
>> >
>> >Now what?
>>
>> Your symptoms are not at all the same as the Oops.  One of the most common
>> causes of your problem would be a misconfigured or overlooked personal firewall,
>> or other security component. There are several other possibilities too, and any
>> might be the cause of your problem. Read this article with an open mind.
>> <http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
>> http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html
>>
>> For more direct help, provide "browstat status",  "ipconfig /all", "net config
>> server", and "net config workstation", from each computer, and diagnose the
>> problem.  Read this article, and linked articles, and follow instructions
>> precisely (download browstat!):
>> <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
>> http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp


>Chuck,
>Thanks I finally had time again to mess with this and I'm not sure what
>exactly solved the problem but it's working again.  After a re-boot
>everything started working.  I had already done several things per the
>previous email and then started looking at the suggestions you made.  I also
>did a re-boot part way through so maybe something I tried needed the reboot
>to go into effect.  In any case all is working now.  Thanks for all the help,
>
>Keith