How to Fix Logon Failure: User Account Restriction

If you try to connect to the computer using Remote Desktop and login to the user account that has no password set, you will get the error “Login failure: user account restriction. Possible reasons are blank passwords not allowed, logon hour restrictions, or a policy restriction has been enforced”. Clicking the OK button will instantly boot you off the remote desktop connection.

The error happens because in Windows operating system such as Windows XP, Windows Vista, Windows 7, Windows Server 2003 and Windows Server 2008 (or their R2 versions) does not allow local user to log on remotely via network logon if the user account does not have a password set.

Setting a password for the user account that you want to login solves the problem but that would also mean you would have to type in the password every time you start the computer. You can also however disable the blank password check to allow Remote Desktop connection to login to account without password.

1. Click the Start button and type gpedit.msc in the Search programs and files bar and hit enter.
2. At the left pane, go to Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options
3. Look for “Accounts: Limit local account use of blank passwords to console logon only” and double click on it.
4. By default the Enable option is selected and all you need to do is select “Disable” and click OK.

Now you can connect to the computer using Remote Desktop and login to the user account that don’t have a password. Some Windows such as the XP home doesn’t have gpedit.msc and you will have to make the changes from registry.

1. Type regedit at the Search programs and files bar and hit enter.
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. Look for LimitBlankPasswordUse name on the right pane, double click on it and set the value data to 0.

Full system backup with rsync in linux

This command depends on brace expansion available in both the bash and zsh shells. When using a different shell, --exclude patterns should be repeated manually.

# rsync -aAXv --exclude={"/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*","/media/*","/lost+found"} /* /path/to/backup/folder

Using the -aAX set of options, the files are transferred in archive mode, ensuring that symbolic links, devices, permissions and ownerships, modification times, ACLs and extended attributes are preserved.

The --exclude option will cause files that match the given patterns to be excluded. The contents of /dev, /proc, /sys, /tmp and /run were excluded because they are populated at boot (while the folders themselves are not created), /lost+found is filesystem-specific. Quoting the exclude patterns will avoid expansion by shell, which is necessary e.g. when backing up over SSH.

Note:

• If you plan on backing up your system somewhere other than /mnt or /media, do not forget to add it to the list of exclude patterns to avoid an infinite loop.
• If there are any bind mounts in the system, they should be excluded as well, so that the bind mounted contents is copied only once.
• If you use a swap file, make sure to exclude it as well.
• Consider also if you want to backup the /home/ folder. If it contains your data, it might be considerably larger than the system. Otherwise consider excluding unimportant subdirectories such as /home/*/.thumbnails/*, /home/*/.cache/mozilla/*, /home/*/.cache/chromium/*, /home/*/.local/share/Trash/*, depending on software installed on the system. If GVFS is installed, /home/*/.gvfs must be excluded to prevent rsync errors.

How to disable firewall on RHEL / CentOS / RedHat Linux

First login as the root user.

Next enter the following three commands to disable firewall.
# service iptables save
# service iptables stop
# chkconfig iptables off

If you are using IPv6 firewall, enter:
# service ip6tables save
# service ip6tables stop
# chkconfig ip6tables off

Linux rdesktop ERROR recv Connection reset by peer

The vast majority of it means "Turn off Remote Desktop with NLA".

Set on target "Microsoft Windows (WIN)"

1. run SystemPropertiesRemote.exe
2. Deselect "Allow connections only from computers running Remote Desktop with NLA"
3. Try to connect from linux client

Your security settings have blocked a self signed application from running ( window 8 , Java 7 Update 51)

there could be many reason for this error , but I have encountered this error while trying to open Oracle EBS 12.1.3 after I have upgraded my Java 
FROM  Version 7 Update 40 
To  Version 7 Update 51

Well ,  this is a genuine message as Oracle has enhance security feature in Version 7 update 51 . It is highly recommended that we should not run the applications that raised this type of messages , but in my case I am trying to my EBS application which is a safe application. Options that I have - 

1.Contact DBA
2,Use below workaround , and I like option #2 as this is quick one ( but at the same time run these applications only if you understand the risks and implications).


As a workaround, you can use the Exception Site list feature to run the applications blocked by security settings. Adding the URL of the blocked application to the Exception Site list allows it to run with some warnings.

Workaround - 

Steps to Add URLs to the Exception Site list

• Go to the Java Control Panel (On Windows Click Start and then Configure Java)
• Click on the Security tab
• Click on the Edit Site List button
• Click Add in the Exception Site List window

Please note that above workaround works for me , you should evaluate your environment thoroughly before using this work around

Find the WiFi Password on Windows

Open the command prompt in administrator mode. Type “cmd” in the Run box, right-click the command prompt icon and choose Run as Administrator (see how). Now enter the following command and hit enter to see the WiFi password.

netsh wlan show profile name=labnol key=clear

Remember to replace labnol with the name of your Wireless SSID (this is the name of the Wi-Fi network that you connect your computer to). The password will show up under the Security Setting section (see screenshot).

If you do not see the password, probably you’ve not opened the command prompt window as administrator