Re: Problems accessing shares between Xp Pro and Xp Home

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Steve Winograd [MVP] (winograd_at_pobox.com)
Date: 12/09/04


Date: Thu, 09 Dec 2004 12:15:12 -0700

In article <70C87595-D377-4A71-A763-BDF1D19A85A5@microsoft.com>,
"Macelaru" <Macelaru@discussions.microsoft.com> wrote:
>>>The error msg is : "\\Comp-Name 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.
>>>Login failure: the user has not been granted the requested logon type at
>>>this computer"
>>>I have one computer with Windows Xp Proffesional and the other with Windows
>>>Xp Home Ed. connected through a small switch . Both of the computers have
>>>unique Ip and both are working on the Internet . I can ping them, I can see
>>>them but when I try to access through the network I get this error msg.
>>>And I tryed the following :
>>>- Making new users ( both with admin rights and on both of the computers the
>>>same users )
>>>- I`ve made the network again with the microsoft Network Setup Wizard
>>>- Modified the registry entry from HLM\System\CurrentControlSet\Control\LSA
>>>"restrictanonymous" seting it to "0"
>>>- Reinstalled both network cards
>>>
>>>NOTHING WORKED
>>>
>>>Pls. HELP
>>
>>The problem and the solution are on the computer that can't be
>>accessed. If that computer runs Windows XP Professional:
>>
>>1. Click Start | Run, type "secpol.msc" in the box, and click OK.
>>2. Click Local Policies.
>>3. Click User Rights Assignment.
>>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.
>>
>>If the computer that can't be accessed runs Windows XP Home Edition,
>>the "secpol.msc" program isn't available. To make the required user
>>rights assignments:
>>
>>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
>
>Thanks a lot for everything. Finaly it worked with what Steve told me ( thx
>again man ) . The only thing that I had to do was to disable "Accounts: Limit
>local account use of blank passwords to console logon only " from " Security
>Options" in "Local Security Settings" ( accessed by runing the command
>"secpol.msc"). But this was because I had the user " User" with no password
>on both of the computers.
>
>So THX again

You're welcome. I'm glad that my suggestion helped you solve the
problem. Thanks for the report.

By default, Windows XP Professional denies network access from a user
account that doesn't have a password, and the setting that you found
changes that.

I don't know why, but when I try network access from a user that
doesn't have a password, I get a different error message than the one
that you got. I get:

   Logon failure: user account restriction. Possible reasons are
   blank passwords not allowed, logon hour restrictions, or a policy
   restriction has been enforced.

-- 
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


Relevant Pages

  • Re: Connecting to win2k Server with Windows 7 Ultimate
    ... We purchased a Windows 7 Ultimate upgrade, entered the product key and the upgrade was downloaded and installed via internet. ... Network access: Let Everyone permissions apply to anonymous users ...
    (microsoft.public.windows.server.networking)
  • Re: Network WinXP to Win 98SE- Access problems
    ... Which version of Windows does the desktop run? ... What are you typing or clicking to try to transfer files from the ... > the error message? ... > Please post any reply as a follow-up message in the news group ...
    (microsoft.public.windowsxp.network_web)
  • Re: Network WinXP to Win 98SE- Access problems
    ... Which version of Windows does the laptop run? ... Which version of Windows does the desktop run? ... the error message? ... Please post any reply as a follow-up message in the news group ...
    (microsoft.public.windowsxp.network_web)
  • Re: Pathworks 6.0C Windows 2003k AD Domain, making it work.
    ... you mentioned to get the trust to work properly. ... Require strong (Windows 2000 or later) session key ... Network access: Do not allow anonymous enumeration of SAM accounts ... > I installed the new 2003 machine as a AD Server, ...
    (comp.os.vms)
  • Re: Migration for NT 4.0 to Windows Server 2008 Domain Controller
    ... we can establish the trust relationship between ... Windows NT4 to Windows 2008. ... Network access: Do not allow anonymous enumeration of SAM accounts ... Domain member: Digitally encrypt secure channel data ...
    (microsoft.public.windows.server.migration)