If only a few users lost their passwords, you could boot the PC with ophcrack and that very well may recover their passwords. I still don't understand why they're configured as a workgroup. Locally on the PC if you are using the local users there are some questions to be answered as to why Your gonna get some heat on your config!
We're a bit stumped as to why a domain and workgroup How about this post? Wow, you guys have some work to do as a long term project! Gotta get all those workstations in the domain and get everyone logging in that way. What a nightmare!!! Anyway, it is possible to make this work, but the user name and password on the workstation has to match perfectly with the user name and password on the domain. If they don't, authentication prompt.
Like everyone else said, wow! I bet you could save yourselves 10 hours a week on the low side! For the current setup, as the admin you will probably need to reset his password on the server, and then on the workstation have him set it to the same password. This is a registry fix, if you look at the profile it may say John.
Doe domain. Wow, I think everyone has already sufficiently suggested you like pain having that many in a workgroup; so I will not say anything else. I had one business that I serviced that had a domain server not used as that though and everyone was in a workgroup only 10 computers.
It made no sense at all and since they were just using the server to store approx 2 GB of files I got them to get rid of it and installed a HP media vault.
Active 3 years, 2 months ago. Viewed 49k times. Improve this question. Acorn Acorn 1 1 gold badge 5 5 silver badges 19 19 bronze badges. Add a comment. Active Oldest Votes. Improve this answer. This seems to be "the" answer. The "net use" incantation suggested by user did not work - as it did not work for Acorn. Sure it logs me in, but it doesn't "persist". StackzOfZtuff 1, 1 1 gold badge 11 11 silver badges 23 23 bronze badges. I tried that and had no luck, hence the last resort of authenticating at startup.
There's no error message, just after rebooting the credentials are not remembered and you need authenticate again. This answer is not saying anything wrong. It does not solve the problem either. Rob Rob 31 1 1 bronze badge. And this fixed my issue. Thank you!!! I did try their user account on a separate system and it worked fine. I will try another user account on their system and see how that responds but will do a little later.
For now I have used a batch file with the net use command and it's working for now. I'll keep you posted. Thanks so much. Used another profile on the system and it worked fine. I guess it could be his profile is corrupt some how. Is it SP3 related I'm having the same problem with my systems.
They all map to a shared drive using a valid network username and password, though this is not the same credentials as the user is logged in with. All worked perfectly for many years and then, since installing SP3, the password gets forgotten when the user logs out and back in again.
When the user tries to open the mapped drive it then locks out the account on the network. I've done the same thing but am not happy having the password readable by anyone.
We have found a way round by adding domain users with the same usernames and passwords as the local users on the machine. We then map the drive as each individual user, remember the password and Bob your aunties live in lover. Thanks for your help though.
I still need to read through all of those articles. Maybe there is something in there that can explain it. Sorry but using an XP machine at the moment so I can only work with my faulty memory! Well it is an XP machine, and I have done that already. It lets me enter the server name, the user name and password, but it doesn't work.
I still have to log in to the network manually after I log in to Windows. I'm thinking it must be something about connecting to Linux servers. Probably a lost cause. Oh I missed the earlier part about the server being Samba.
How are the samba users authenticated? Does your smb. See also forum Andrew Tridgell: Samba , since this condition is really due to your Samba configuration, not Windows. Unfortunately I'm not the network admin, though I'm trying to learn.
Out network admin doesn't really show much concern over this. I checked out the smb. I cat the smbusers file and it lists root and guest. Is that something that can be edited? Should it be? I use the same username and password to log on to Windows as I do the server Thanks a lot for your help.
0コメント