New answers tagged

4

You can visualize the failed user names after you turn up the verbosity of the log in sshd_config¹, but there is no way to see the failed passwords as this could be a potential security issue and would violates the privacy of users (for example you could mistype your password and it would be leaked into some log file). All the passwords are handled as ...


2

The problem is that AD now sees the VM as the Official [TM] version of your company-issued laptop. I'm afraid you're going to have to 'fess up to someone who has the privileges to click "reset" on the domain side, then pop the laptop out of and back into AD. This will break the VM on your home desktop.


1

Everybody uses the same user log ins for their machine (WorkUser1) - so I cannot simply add the WorkUser1 account as having shared/owner access This is your problem which you must fix first: If you use a workgroup, you create user accounts with the same usernames and password combinations like on your local PCs and optionally create groups where those ...


0

You do this by having Active Directory. If you've got 30 computers and users, I'd say that's above the threshold where you'd want to, or be able to, manage them independently in any kind of effective way. Rob-d's solution will work, but only if you don't want any kind of accountability for those confidential files.


0

Create a new user on the server and give that user the access and not 'everybody' then pass around the credentials like currency EDIT - actually just for giggles goto start run //serverip/c$


0

Windows Server 2012 R2, by default, installs with a user named Administrator with a blank password and forces you to change it at first boot. That sounds like what you ran into, so try that. Failing that, it's not hard to reset a Windows password with a boot disk any number of ways, including by copying cmd.exe to utilman.exe and then using the ease of ...


0

this feels like an selinux issue with the files related to passwd. If something has changed the passwd files when selinux was not active it can have the wrong labels and selinux will deny access to the file. (You can probably confirm if selinux is on by examining the kickstart file) Follow the instructions from here to boot into rescue mode. After you gain ...


1

you are in single user mode so you don't specify users make sure your root filesystem is mounted in read/write mount -o remount,rw / then passwd


0

1- Shut down your server using the Xencenter controls 2- Right click on machine and select Properties 3- Go under Boot options Change the OS Boot Parameters to rw init=/bin/bash Some times for some OS especial CentOS you will need to write in the field the word single instead of rw init=/bin/bash so try both if first trick didn’t work. 4- Save and ...



Top 50 recent answers are included