can't map share folder

[Guest]

Hi all. I have 1 pc that have problem mapping a share folder that exists on a
domain controller. It require administrator user name and password to map the
share folder. This should not be the case as i have set the user to have full
access rights to the shared folder. The client pc is also joined to the
correct domain. The user also have admin rights to his client pc. So why does
the user still have to key the admin username and password when mapping the
share folder? Other users have no such problems. Thks in advance.

 

[Pegasus \(MVP\)]

Hi all. I have 1 pc that have problem mapping a share folder that exists on a
domain controller. It require administrator user name and password to map the
share folder. This should not be the case as i have set the user to have full
access rights to the shared folder. The client pc is also joined to the
correct domain. The user also have admin rights to his client pc. So why does
the user still have to key the admin username and password when mapping the
share folder? Other users have no such problems. Thks in advance.

You need to supply more information. Do this:
1. Open a Command Prompt.
2. Type this:
set > c:\set.txt
notepad c:\set.txt
3. Paste the contents of set.txt into your reply.

 

[Guest]

hi pegasus, below is what you wanted...
i do not feel showing this would help though...

ALLUSERSPROFILE=C:\Documents and Settings\All Users
APPDATA=C:\Documents and Settings\cheau\Application Data
CLASSPATH=.;"C:\Program Files\Java\j2re1.4.1_01\lib\ext\QTJava.zip"
CLIENTNAME=Console
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=WENBIN
ComSpec=C:\windows\system32\cmd.exe

HOMEDRIVE=C:
HOMEPATH=\Documents and Settings\cheau
LOGONSERVER=\\FILSVR
NUMBER_OF_PROCESSORS=1
OS=Windows_NT
Path=C:\windows\system32;C:\windows;C:\windows\system32\WBEM
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 15 Model 1 Stepping 3, GenuineIntel
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=0103
ProgramFiles=C:\Program Files
PROMPT=$P$G
QTJAVA="C:\Program Files\Java\j2re1.4.1_01\lib\ext\QTJava.zip"
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\windows
TEMP=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp
TMP=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp
USERDNSDOMAIN=KCP.COM
USERDOMAIN=KCP
USERNAME=CHEAU
USERPROFILE=C:\Documents and Settings\cheau
windir=C:\windows

 

[Pegasus \(MVP\)]

I suspected for a while that your problem user might be
authenticated locally rather than by the domain controller.
Your reply proved beyond doubt that this is not so.

Your problem has me puzzled. If this was my server
then I would run a few tests in order to reduce the
number of variables:
- Ask the same user to log on to different PCs, to see
if the problem was user-specific.
- Ask different users to log on to the problem PC, to
see if the problem is PC-specific.
- Rename the profile folder of the problem user in
order to force a new profile to be created.
- Delete, then recreate the domain account of the problem
user.
- Disconnect the problem PC from the domain, then
re-register it.
- Ensure that the share permissions are set to "Full
Access" for everyone, and that all restrictions are
managed with NTFS security.
- Delete the share on the server, then recreate it.
- Ensure that the problem user does not also have
a local account under the same logon name.

Many of these tests are based on pure guesswork, with
no strong rationale behind them. However, they might
point you in the right direction.