W2K Pro Loses Profile

[bluemartian22]

I have a laptop user that continues to loses his profile when he does not use his computer for several days. The local profile remains, but the profile used when he logs into the network is gone and he his forced to setup a new one. Anyone have any ideas how to correct this problem?

Thanks

 

[wolluf]

'but the profile used when he logs into the network is gone' - what exactly do you mean by this? Has it physically disappeared from hard drive? Is it there, but windows has set user up with new profile?

Are you using roaming profiles?

There's no confusion between logging in locally and logging onto the domain? (eg, does user have same user id locally and on the domain?)

How many different domains does this user log onto? Is it all domain networks?

 

[bluemartian22]

When I say it is gone, I'm referring to the profile settings that are applied to his network login. These settings are supposed to be under the "Documents and Settings" folder but somehow, they are not being applied and the user is forced to login under the default profile. In other words, the files are there, but Windows has set up the user with another profile.

The user is only logging into one domain and we are not using raoming profiles. The user also has the same login for local access and domain access.

Any ideas...I'm stumped.

Thanks

 

[morpheu5]

Not sure I am on the right track here but we intermittently have some problems with profiles (i.e. local and network) and as long as your user does not rely on a roaming profile I suggest the following.

Login in as an Administator and copy any necessary favourites etc.. from the users profile, then delete the profile entirely.

Get the user to logon to the laptop connected to your network (domain) which will create a network profile on the laptop. When you disconnect the laptop from the network the user shoud be able to logon as normally as the account information information will have been cached on a W2K machine. This will not work on roaming profiles because as soon as you logon the network profile will overwrite the laptops.

Not a direct answer I'm afraid and apologies in advance if this is teaching you how to suck eggs but it may cut down on some of the potential problems.

 

[wolluf]

Have a go with Morpheu5's suggestion - though machine should already have a profile for the user's network login, and one for local profile login. I was asking if local & network login's are the same id. Because windows will set up separate profiles for these 2 logins - first to log on will get a profile same name as user id. Second will get profile with .domainname or .machinename added to it. I was just wondering if the user is logging on locally when not connected to the network and expecting to pick up the network profile (because this won't happen - although I'm not sure if you actually supplied the network profile name & path to the local user's profile properties - run lusrmgr.msc - it would pick it up).