So, our office got a new computer for the office coordinator, unfortunately it's an XP machine.

Well, I've got a lot of it working, but for one bug........

We have a Linux server which holds all of our files. From the XP machine, when I connect from my own account, everything is fine. But, when I log in as her, everything on the server is read-only. Looking the logs, when I connect, samba recognizes me. When she connects, samba thinks of her as "nobody."

I've checked several times to make sure the username/passwords match on the two machines. I've also changed her status on the XP box as Administrator, because it worked for someone on according to a google search.

Any assistance in figuring out why she is considered a "nobody" would be appreciated.

--Dave

Just to eliminate an account problem, is everything ok if she logs into your machine (or another working one in the office) with her login details?

She had no problems from her old computer. I've logged into the Linux box as her, and had no problems.

I'm thinking that XP has some sort of network cache, is sending her old information to the server, which then assigns her the user name "Nobody." I've noticed that whenever I make any type of change to a Window's network, it takes quite a while before any window's computers take notice.

Any thoughts on how to clear this cache? (if it exists)

--Dave

In the XP machine, do the following:

1. Go to Control Panel, choose Administrative Tools, and click on Local Security Policy.

2. In the Local Security Policy window, expand Local Policies, and expand Security Options.

3. In Security Options, you'd find an option that says "Number of previous logons to cache". Change the value to zero if you don't want the machine to cache logins.

4. Once you change this, run "gpupdate" in command prompt, and restart your machine.

This should help remove the cached logins.

Hope this helps. Let me know if it doesn't.


--
Guru

It's been a while, because someone else sinmply created a totally new account with the correct user name and password. HOwever, I'm trying to get someone else on right now.

There is no "Local Security Policy" under Administrative Tools or anywhere else obvious in Control Panels.

What next?

--Dave

I'm still having a problem, wherein a Windows XP user is constantly being logged in as "nobody". The original problem was solved when a totally new XP account was created with the same nameassword combo.

I now have a person who needs to log in with his laptop. We've made sure his XP and Samba nameassword match up. Many, many times. Yet, his XP machine still sends the wrong info.

I'm only 90% sure this is a Windows problem. Any information as to this problem will be appreciated.

--Dave

make sure that the computer is browserable and other computer window box could look into it, I sure this the problem
and the linux server type this command smbpassd -a "username" and then do smbpassd -e "username"

I've run smbpasswd several times for this user.

I have 4 other window's users who do not have problems logging in. It's just this one particular user, and his laptop. This tells me that Samba is configures properly.

The only difference is that his laptop gets it's address via DHCP, while the other machines have a static address. I don't think this is the problem, because it happened before on a machine with a static IP address. It was resolved by creating a totally new account.

--Dave