From: Greg Ercolano <erco@(email surpressed)>
Subject: Re: Win2K Submit Error
   Date: Mon, 23 Jan 2006 04:59:24 -0500

Luke Cole wrote:

c:\>runas /user:netrender cmd
Enter the password for netrender:
Attempting to start cmd as user "STUKA\netrender"
                                 ^^^^^
1326: Logon failure: unknown user name or bad password.

So, by default Win XP seems to be looking inside the local user database for the credentials.

	Correct -- without a domain qualifier, it assumes the local machine.

	As you show below, to login as the domain user, you have to use the
	"DOMAIN\username" syntax for the runas command.

c:\>runas /user/:FUEL\netrender cmd
Enter the password for FUEL\netrender:
Attempting to start cmd as user "FUEL\netrender"

And it works - launching the new cmd window - in this new window I try the directory listing:

c:\blah> dir \\na2.fuel\red\
Logon failure: unknown user name or bad password.

	Sounds like the domain user FUEL\netrender is somehow unknown
	or untrusted by your file server.

	Since FUEL\netrender is a domain user, and if your server is
	part of that domain, then the 'FUEL\netrender' user should have
	the same password everywhere, and consistent access permissions.

	Verify the Rushd service is set to run consistently as the domain
	user "FUEL\netrender" on all machines in the "Services|Rushd|Log On As".

	Or, configure all machines with a *local* 'netrender' user ('workgroup' style),
	in which case make sure Rushd runs as that user on all machines, has the
	same local password on each, and on the filer as well.

Examining the user account manager in the control panel shows the same thing as on the XP host - it has a user netrender in the FUEL domain (rather than the local LANCASTER domain).

	You can have both a local user 'netrender' and the FUEL\netrender
	domain user. Sometimes this is done to give the domain user
	local admin permissions by adding the local netrender user to
	the admin group.

So I suppose the "problem" comes down to differences between the ways in which Win 2K and Win XP handle user authentication/drive mappings...

	It sounds odd.. I'm more apt to think there are differences
	in the user configs on the different machines, or domain membership
	issues.


	Either that, or its running XP Home Edition ;)
	(Home Edition has very dumbed down network file sharing capabilities;
	basically only guest access is allowed)

--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Cel: (Tel# suppressed)
Fax: (Tel# suppressed)