C
Carmine Castiglia
This situation involves a notebook PC running XP Pro/SP1 and a "Snap Server"
NAS device in a mixed (Win2K, Win98, WinXP) P2P environment.
When the notebook was originally configured by the reseller, he defaulted
the username to "user". When our user received the notebook, he promptly
changed the name associated with the account to his name - let's call him
"John Smith". All is well.
Now, it becomes necessary to give John access to protected folders on the
Snap Server NAS. A user is created on the Snap Server, "John Smith" with
the same password as the password used to logon to his notebook. No go -
the notebook cannot get authenticated by the Snap Server and is refused
access to the shared folders. Note that this scenario works perfectly under
Win2K and Win98.
The problem, after much trial and error, turns out to be that no matter what
the "User Name" on the notebook is set to, it is attempting to log onto the
Snap Server using the original "user" username.
Why?
Is there a way around this?
PS: I have tried using XP's "Network Logon Id" function to get around this,
so far without success. Seems like it should work...
NAS device in a mixed (Win2K, Win98, WinXP) P2P environment.
When the notebook was originally configured by the reseller, he defaulted
the username to "user". When our user received the notebook, he promptly
changed the name associated with the account to his name - let's call him
"John Smith". All is well.
Now, it becomes necessary to give John access to protected folders on the
Snap Server NAS. A user is created on the Snap Server, "John Smith" with
the same password as the password used to logon to his notebook. No go -
the notebook cannot get authenticated by the Snap Server and is refused
access to the shared folders. Note that this scenario works perfectly under
Win2K and Win98.
The problem, after much trial and error, turns out to be that no matter what
the "User Name" on the notebook is set to, it is attempting to log onto the
Snap Server using the original "user" username.
Why?
Is there a way around this?
PS: I have tried using XP's "Network Logon Id" function to get around this,
so far without success. Seems like it should work...