Link to home
Start Free TrialLog in
Avatar of BLEEPINGNETWORK
BLEEPINGNETWORKFlag for United States of America

asked on

Conecting to a shared file access denied.

My environment is as follows.
Server 2003 domain.
Xp Pro workstations sp3

The file is being shared from a XP workstation (computerB) and I am attempting to connect with another xp workstation (computerA).

The Domain admin is able to map the shares.
Users are not.

I recieve the error whether using IP or system name.

I checks share permissions and the user has read, write, change permissions on the folder.

I am recieving the following error.
"The mapped network drive could not be created because the following error has occurred.
An Extended Error has occured."

Event Type:      Failure Audit
Event Source:      Security
Event Category:      Logon/Logoff
Event ID:      534
Date:            3/17/2011
Time:            5:04:34 AM
User:            NT AUTHORITY\SYSTEM
Computer:      ComputerB
Description:
Logon Failure:
       Reason:      The user has not been granted the requested
             logon type at this machine
       User Name:      chester
       Domain:            cheetoes
       Logon Type:      3
       Logon Process:      NtLmSsp
       Authentication Package:      MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
       Workstation Name:      ComputerA
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



WHat more information is needed and how do I trouble shoot and resolve this issue?
ASKER CERTIFIED SOLUTION
Avatar of Netman66
Netman66
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of BLEEPINGNETWORK

ASKER

whooooooooooot!!!!tyvm THAT WORKED! it only had administrators! TYVM 500points to you and my eternal gratitude!
Netman66 ROCKS!
Thanks!

Keep in mind, that if this setting is made on a Domain Policy somewhere and only lists Administrators then it will likely change back at next policy refresh (in 90 minutes).  

You'll need to address this issue differently if that is the case.