If you receive The account is not authorized to log in from this station error in Windows Server while connecting systems in your home network, then this post will help you.
If you have more the one computer running Windows Server, then it’s possible to connect them using HomeGroup. HomeGroup provides an easy pathway to share files and printers on a home network. The conventional way of copying the file first to USB drive and then pasting it on the target machine can thus be suppressed. However, sometimes you may come around to a situation, that leads to connection failure while connecting in your home network. In that case, you’ll receive the following message:
<domainname> is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
The account is not authorized to log in from this station.
The first and foremost step you might want to take after receiving this error is to try turning on and then turning off the Windows Firewall and see if that helps. If that doesn’t help, you can try the suggestion mentioned below.
The account is not authorized to log in from this station Windows Server error
Making mistakes while manipulating the registry could affect your system adversely. So be careful while editing registry entries and create a System Restore point before proceeding.
1. Press Windows Key + R combination, type put regedit in Run dialog box, and hit Enter to open the Registry Editor.
2. In the left pane of Registry Editor, navigate here:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
3. In the right pane of the above-mentioned registry location, right-click and select New -> DWORD.
Name the newly created DWORD as AllowInsecureGuestAuth and double click the same DWORD to modify its Value data:
4. In the above-shown box, put the Value data as 1 and click OK.
Close the Registry Editor and reboot the machine, the problem must be fixed after restarting the machine.
Let us know if this works for you.
Read: How to install and configure Windows Server Essentials Experience.
