error 5 connecting to Ghost share

[JAQK]

We've set up a (Win2K3) server that holds Ghost images in a share from which
we can pull down images to workstations using the Ghost boot diskette.

Problem is we can no longer map a drive using 'net use g: \\server\share',
because error 5/access denied comes up, asking for a password that never
works. The mapping always used to work. The permissions are sufficient and
always worked before.

This is totally mystifying -- there's no password on the share, this is a
Windows 2K3 domain!

I have a feeling this is a known problem, but I can't find any info on it.

Anyone know what could be the cause ?

 

[Pegasus \(MVP\)]

We've set up a (Win2K3) server that holds Ghost images in a share from which
we can pull down images to workstations using the Ghost boot diskette.

Problem is we can no longer map a drive using 'net use g: \\server\share',
because error 5/access denied comes up, asking for a password that never
works. The mapping always used to work. The permissions are sufficient and
always worked before.

This is totally mystifying -- there's no password on the share, this is a
Windows 2K3 domain!

I have a feeling this is a known problem, but I can't find any info on it.

Anyone know what could be the cause ?

Delete the share, then recreate it:

net share Images /del
net share Images=d:\Images

Now check the "Images" share permissions via "My Computer". They
are NOT the NTFS permissions!

 

[JAQK]

Delete the share, then recreate it:

net share Images /del
net share Images=d:\Images

Where do you suggest we do this -- at the command prompt in windows or in
DOS, when booting from the ghost floppy ?

Now check the "Images" share permissions via "My Computer". They
are NOT the NTFS permissions!

It's clear to me that the share pemissions are not the same as the NTFS
permissions, but I think the share permissions (Domain Admins - Full,
Authenticated Users - Change) are more than adequate (since the mapping
always worked before it suddenly stopped working).

The boot floppy client has always been set to log on as domain
administrator.

 

[Phillip Windell]

DOS is not capable of connecting to Server2003 until you weaken the security
of 2003. This was not the case with 2000 and older. The article does not
mention DOS (nobody remembers it exists I guess) but the same issue applies.

811497 - Error Message When Windows 95 or Windows NT 4.0 Client
Logs On to Windows Server 2003 Domain
http://support.microsoft.com/default.aspx?scid=kb;en-us;811497

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------