Hi Greg,
Having differing passwords works fine with Windows XP, so it must
just be a Win2K specific "feature".
I guess I'd be surprised if that were the case, given the above
scenario; I don't see how security is preserved with username
alone..
it might be failing over to guest access in that case.
I guess make sure the XP is configured with the same WORKGROUP
as the others.
The domain/workgroup must also come into it somehow as you
suggest....I carried out some more tests:
On the Win XP box (on the samba domain FUEL):
c:\>runas /user:netrender cmd
Enter the password for netrender:
Attempting to start cmd as user "STUKA\netrender"
RUNAS ERROR: Unable to run - cmd
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...if I go:
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.
Which is now what we have learned to expect, because the netrender
account on the filer has a different password. However, in our
testing on Friday, we found that specifying a log directory on the
filer would work on Win XP hosts (the share on the filer is already
mapped on the Win XP host using different credentials - same
username, but matched with the password of the account on the filer).
I checked the user account manager in the control panel - it says it
has a user netrender in the FUEL domain (rather than the local STUKA
domain).
Returning to my Win 2K box once again (also on the samba domain FUEL):
c:\>runas /user:netrender cmd
Enter the password for netrender:
Attempting to start "cmd" as user "netrender"...
And a new command shell is opened.
c:\>runas /user:FUEL\netrender cmd
Enter password for FUEL\netrender:
Attempting to start "cmd" as user "FUEL\netrender"...
And a new command shell is opened also.
We already know that then going on to do the directory listing also
generates the Logon failure message like the XP host, however our
testing on Friday also showed that it won't let us use a log
directory on the filer even when it is mapped to the host in the same
way as on the XP host, using different credentials - same username,
but matched with the password of the account on the filer, rather
than on the domain).
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).
So I suppose the "problem" comes down to differences between the ways
in which Win 2K and Win XP handle user authentication/drive mappings...
---
Luke Cole
Systems Administrator / TD
FUEL International
65 King St., Newtown, Sydney NSW, Australia 2042
|