Server 2003 and Users

[ThePiston]

I just installed Server 2003 and I'm having trouble with Users. It seems that if you change a User's name on a client, the username does not actually change - it only changes in the profile, but behind the scenes it's the same. This is a problem because 2003 is very picky about the usernames and passwords. So, I created a User called "Staff" and passwords. Only the client PCs that had "Staff" as the username from the get-go will see the files on Server 2003 - others that were changed from anything else to "Staff" are not able to see the files.

I guess my questions is - how do you change the username in XP and have them actually change?

 

[Genx87]

Are these usernames you are changing local usernames on the XP machines vs Domain accounts on Windows 2003 Active Directory?

 

[RebateMonger]

If you are trying to match local PC User accounts with Domain User accounts, then you'll have to create a NEW account on the PC and use that. I had a few laptops that weren't joined to the Domain, and even though I CHANGED the name of the User on the laptop, they still couldn't access a SQL database on Server 2003.

Once we had them log onto the new account on their laptoops, they could access the SQL database on the server.

 

[ThePiston]

these are local usernames on the clients - I set them all up as the same (on 12 clients) with username "Staff". Some were changed usernames and some were new. I'll try making all new ones for the ones that do not work.

Another problem I have is that even though I can see the files and alter them, I still get a path error on some programs... is that a domain thing? I know on those PCs that Server 2003 is letting them in, but for some reason the paths are weird.

 

[RebateMonger]

Originally posted by: ThePiston
I know on those PCs that Server 2003 is letting them in, but for some reason the paths are weird.

Any chance of furnishing an example?

Re: the User Names.
I don't know why it does this. I didn't have a lot of time to spend on it. It's possible that removing all the cached User account information would fix it (although I'd think I would have tried that). But I do know that creating a brand new account on those PCs that aren't working will likely fix the account logon problem.

 

[ThePiston]

lastly - I have the Staff client that will get the error 75 (path) error on a program that uses the Server. It will not do this when I change the account from a Limited account to a Admin account - it only does this on a Limited account and only on some computers. I have set all Users in 2003 to have all rights so I guess it's the XP machine that is restricting rights or changing paths for limited accounts?

 

[imported_snikt]

Seems like a permissions issue if they don't have a problem with an admin account. The app may be trying to write a temp file somewhere on the local drive.

 

[ThePiston]

i guess that could be it but I've got some clients that can run the app on a Limited account...

 

[imported_snikt]

Originally posted by: ThePiston
i guess that could be it but I've got some clients that can run the app on a Limited account...

Is that occurring on XP or 2000? If I remember correctly, 2000 wasn't as restrictive with access to some local folders as XP is. Also, depending how the app is coded and installed can also explain that. When our in-house coders write an app up for us, they give us an option to allow "everyone" access to the app or just the admin account when its installed.

 

[ThePiston]

you're right - I figured part of it out. The app needs access to some Windows files so I had to go into the Security tab (safe mode using XP Home) and give the Staff users full access to a folder and file in C drive. Those work fine now. I stil lcan't figure out the username mess though so I'm sure I'll have to delete and add some new names.