System 2221 Error Mapping Drive

[Heinz]

If I Map a drive from Windows XP on a domain, as in:
Net Use Q: \\Nt4SrvName\ShareName
I get a System error 2221. The user name could not be found.

But if I do the same thing with an IP address, such as:
Net Use Q: \\192.168.52.11\ShareName
It is successfull.

If I Ping Nt4SrvName it resolves to the correct I/P Address.

What is going on here?

[Heinz]

I should add that the NT-Server is not in the 2003 domain, but DNS contains
both Forward and Reverse Lookup records for the server as below:

Forward Lookup Zones
ophl.ca
NT4SRVNAME Host(A) 192.168.52.11

Reverse Lookup Zones
192.168.52.x Subnet
192.168.52.11 OPSWPGNT1.ophl.ca.
192.168.52.11 opswpgnt1.

Is there something wrong here?

[Kevin D. Goodknecht Sr. [MVP]]

In news:3B04CF5B-9898-4EBF-B1F3-613F7E0E9141@microsoft.com,
Heinz <Heinz@discussions.microsoft.com> commented
Then Kevin replied below:
> If I Map a drive from Windows XP on a domain, as in:
> Net Use Q: \\Nt4SrvName\ShareName
> I get a System error 2221. The user name could not be
> found.
>
> But if I do the same thing with an IP address, such as:
> Net Use Q: \\192.168.52.11\ShareName
> It is successfull.
>
> If I Ping Nt4SrvName it resolves to the correct I/P
> Address.
>
> What is going on here?

Does the mapping work if you use FQDN in the mapping
\\OPSWPGNT1.ophl.ca\sharename ?

--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

[Heinz]

"Kevin D. Goodknecht Sr. [MVP]" wrote:

> Does the mapping work if you use FQDN in the mapping
> \\OPSWPGNT1.ophl.ca\sharename ?


No, then I get: System error 67 has occurred.
The network name cannot be found.
See results below:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\op_new>net use q: \\opswpgnt1\mntcprg
System error 2221 has occurred.

The user name could not be found.

C:\op_new>net use q: \\opswpgnt1.ophl.ca\mntcprg
System error 67 has occurred.

The network name cannot be found.


C:\op_new>ping opswpgnt1

Pinging opswpgnt1.ophl.ca [192.168.52.11] with 32 bytes of data:

Reply from 192.168.52.11: bytes=32 time<1ms TTL=128
Reply from 192.168.52.11: bytes=32 time<1ms TTL=128
Reply from 192.168.52.11: bytes=32 time<1ms TTL=128
Reply from 192.168.52.11: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.52.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\op_new>nslookup opswpgnt1
Server: wpgbk1.ophl.ca
Address: 192.168.50.25

Name: opswpgnt1.ophl.ca
Address: 192.168.52.11

C:\op_new>net use q: \\192.168.52.11\mntcprg
The command completed successfully.

[laratech2]

I am having exactly the same issue here, works fine with the domain admin account though? Any ideas anyone?

[timeshell]

While logging into the domain with my user. However, logging into another computer works fine. Domain admin also works. Suggestions?

[DaveE]

I ran into precisely the same trouble trying to map a drive located on a local workgroup (thepauls) while connected to a Windows 2003 domain over a VPN connection.

I finally got the local drive mapping to work by adding a username and password to the use net command as such:

use net e: \\pirsig"\DaveE's Documents" password /u:thepauls\DaveE

where password is the user's password and thepauls\DaveE is the local workgroup and username.

The username and password I'm using above are the same as I use to login to the XP machine I want to map the drive on (pirsig).

What's so strange about this is I have two XP machines on the local workgroup (thepauls) and I can map drives on one of them (chesterton) without all this trouble but to map drives on the other listed here (pirsig), I have to go through all this work. Anyone got an idea of what's different between the two?

These two web pages provide more detail and helped me:

• http://www.howtonetworking.com/VPN/b...govervpne1.htm
• http://www.microsoft.com/resources/d....mspx?mfr=true

[racingmustang]

Hello all,

I found a true solution to this problem (not a workaround). Hopefully it will be relevant for others experiencing this frustrating, nearly inexplicable problem. (I know the thread is old.)

I had the following symptoms:

1. On ONE workstation only, the user logged in and received System Error 2221 while a logon script tried to map a drive using the remote system name and share. This problem did NOT happen at other workstations when used with the same user account and logon script.

2. If an administrator account was used at the "faulty" workstation, the share would map perfectly.

3. Alternatively providing an IP address and share name in place of the remote system name and share name successfully mapped the drive at the "faulty" workstation.

The answer... tada...

I was unaware of an obsolete set of credentials saved in the STORED USER NAMES AND PASSWORDS applet. It was overriding the expected login script (default) credentials. To access this applet and delete the offending credentials, go to Control Panel > User Accounts > Advanced (tab) > Manage Passwords (button).

In all fairness to previous posts, this was a really tough problem to find because the errors were very subtle, but I did get the feeling the credentials were being overridden somewhere.

Enjoy!
Racingmustang

[ctvarner]

I have the same problem, but racingmustang's solution did not apply. I'd like to offer a variation of DaveE's solution.

I found I could map a drive with the /user keyword in the net use command, specifying the same domain\userid that I had used to log on to this machine, but without specifying a password. Thus the following:

net use drive: \\servername\share /user:%userdomain%\%username%

Building on that, I wrote a little batch script to un- and re-map all of my mapped drives using the logon credentials. (Your mileage may vary: you may not need to un-map anything, or you may need some of your drives mapped with different credentials. Caveat emptor.)

for /f "tokens=2,3 skip=6" %%i in ('net use') do call :check %%i %%j

goto :EOF

:check
set __drive=%1
set __share=%2
if "%__drive% %__share%" NEQ "Windows Network" (

if "%__drive% %__share%" NEQ "command completed" (

net use %__drive% /d
net use %__drive% %__share% /user:%userdomain%\%username%

)

)

Good luck!

[stooge44]

Hello all,

I found a true solution to this problem (not a workaround). Hopefully it will be relevant for others experiencing this frustrating, nearly inexplicable problem. (I know the thread is old.)

I had the following symptoms:

1. On ONE workstation only, the user logged in and received System Error 2221 while a logon script tried to map a drive using the remote system name and share. This problem did NOT happen at other workstations when used with the same user account and logon script.

2. If an administrator account was used at the "faulty" workstation, the share would map perfectly.

3. Alternatively providing an IP address and share name in place of the remote system name and share name successfully mapped the drive at the "faulty" workstation.

The answer... tada...

I was unaware of an obsolete set of credentials saved in the STORED USER NAMES AND PASSWORDS applet. It was overriding the expected login script (default) credentials. To access this applet and delete the offending credentials, go to Control Panel > User Accounts > Advanced (tab) > Manage Passwords (button).

In all fairness to previous posts, this was a really tough problem to find because the errors were very subtle, but I did get the feeling the credentials were being overridden somewhere.

Enjoy!
Racingmustang

Thanks so much! this really helped solve a big issue.