Problem Mapping a Drive to a Server 2003 Machine in XP

I'm toying with a test configuration using Server 2003. At the moment
I'm testing file shares. I have a Server 2003 box running as a domain
controller and a file server (obviously this configuration will not be
making it to production).

I'm trying to map a drive on a Windows XP machine, which does not
belong to any domain, to the Server 2003 box. I've successfully
mapped the same drive (using the same path) on another standalone
Server 2003 box (also not belonging to any domain) so I know that the
user account on the domain controller computer is functioning properly
as the drive is mapped without any problems.

However, whenever I repeat the same steps on the XP comp it appears to
connect but then an additional dialogue box appears asking for a
username/password combo. This never appeared on the standalone Server
2003 comp while connecting.

So my question is am I missing a security setting on either the DC or
the XP machine that would explain why the domain controller doesn't
seem to trust it but does the other Server 2003 box? I don't want to
make the XP machine a part of the domain and like I said the other
Server 2003 machine connected fine.

Thanks for any assistance.

Hi,

when you are prompted for username and password can you enter it like this:

in username part enter: domainname\username
in password part enter: password

Replace domainname with name of your test domain
Replace username with username in your environment
Replace password with password that is assigned to your user

I hope this helps,

Mike

"Shawn Albright" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) m...
> I'm toying with a test configuration using Server 2003. At the moment
> I'm testing file shares. I have a Server 2003 box running as a domain
> controller and a file server (obviously this configuration will not be
> making it to production).
>
> I'm trying to map a drive on a Windows XP machine, which does not
> belong to any domain, to the Server 2003 box. I've successfully
> mapped the same drive (using the same path) on another standalone
> Server 2003 box (also not belonging to any domain) so I know that the
> user account on the domain controller computer is functioning properly
> as the drive is mapped without any problems.
>
> However, whenever I repeat the same steps on the XP comp it appears to
> connect but then an additional dialogue box appears asking for a
> username/password combo. This never appeared on the standalone Server
> 2003 comp while connecting.
>
> So my question is am I missing a security setting on either the DC or
> the XP machine that would explain why the domain controller doesn't
> seem to trust it but does the other Server 2003 box? I don't want to
> make the XP machine a part of the domain and like I said the other
> Server 2003 machine connected fine.
>
> Thanks for any assistance.

Thanks for the reply, but I finally figured it out. I had already
tried using the domain name\username format in both that
authentication box and in the map drive window where it says "connect
using a different user name". It still wouldn't work.

The problem lay in the Domain Controller Security Policy, possibly
because in this test I'm using the DC as a file server (just for
testing obviously). I've yet to narrow the problem but it relates to
one of the following four security settings.

Domain member: Digitally encrypt or sign secure channel data (always)
Microsoft network server: Digitally sign communications (always)
Microsoft network server: Digitally sign communications (if client
agrees)
Network security: LAN Manager authentication level

I just disabled them to see what would happen and I was able to map
the drive from XP almost instantly. Like I said, I think this
occurred because I made the DC a file server as well (which will not
be so when we go live).