Remote logins are currently disabled что значит
Перейти к содержимому

Remote logins are currently disabled что значит

  • автор:

Remote Logins Are Currently Disabled on Server 2016: How to Fix

Here in this post, we list 3 ways for you to solve the issue “Remote logins are currently disabled on Server 2016”. Keep reading and take the ways into practice.

By Ellie Twitter / Last Updated November 24, 2022

Run into the issue “Remote logins are currently disabled on Server 2016

Greetings to the well of knowledge. I have a Server 2016 that I am unable to remote into a PC. I get a «Remote logins are disabled» error. This happens to be a Remote Desktop Broker server for an RD server farm. All of the Remote Desktop settings in the Local Group policy are «not configured». Where else should I be looking to fix this? Thanks

— Question from Spiceworks

Remote Logins are Currently Disabled

It will be frustrated to run into the error “Remote logins are currently disabled” on Server 2016 when you try to connect to another PC via RDP. Usually, the issue occurs when a user is attempting to log on to a Terminal Server where an administrator has disabled logon by issuing the CHANGE LOGON /DISABLE command.

How to fix “Remote logins are currently disabled on Server 2016

Here we summarize 3 solutions to fix “Remote logins are currently disabled” on Server 2016. Before the operation, please press Win + R and then input “sysdm.cpl” and click on OK. Make sure the option “Allow remote connections to this computer” under the Remote tab has been ticked. Now follow me to operate.

Fix 1. Use Command Prompt

Here in this part, we’ll manually enable the remote login using the command prompt.

Step 1. Right-click on the Start menu, and choose Command Prompt(Admin).

CMD

Step 2. In the command prompt window, type the following command:

psexec.exe \\SERVERNAME\ change logon /enable

psexe

Then, connect again to check out whether the command enables the remote logins and eliminate the error “Server 2016 RDP remote logins are currently disabled”.

Fix 2. Take advantage of Remote Desktop Session Host configuration utility

We will enable the logon services using the Remote Desktop Session Host Configuration Utility.

Step 1. Press Win + R and then type in tsconfig.msc and then hit the Enter key.

TSConfig

Step 2. In the Remote Desktop Session Host Configuration window. And locate the Edit settings. You’ll see that Restrict each user to a single session has been put Yes.

Yes

Step 3. Right-click on Restrict each user to a single session > Properties and then uncheck the Restrict each user to a single session checkbox.

No

Step 5. Click on Apply then OK for getting back of this type of Remote Logins are Currently Disabled on Server 2016.

Fix 3. Use Registry Editor

In this method, we will use the registry editor to resolve the Remote Logins are Currently Disabled issues.

Step 1. Press Win + R and then input “regedit”.

Regedit

Step 2. In the registry editor navigate to the following path:

HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Terminal Server

Step 3. On the Right Locate the fSingleSessionPerUser, then double click on it.

fSingle

Step 4. In the Value data put 0, to allow Multiple sessions.

Change Data

Step 5. Save the changes and restart your system to check whether the error “Remote logins are currently disabled server 2016” still remains.

AnyViewer: Get remote connection with little effort

Now you may have already fixed the issue “Remote Logins are currently disabled on Server 2016”. However, if the issue remains still or you don’t want to take too much time on fixing it, why not choose a free & professional remote access software, like AnyViewer.

With AnyViewer, you could get remote access anywhere and anytime. Apart from that, you can get one-click connection once you log into the same AnyViewer account on 2 PCs. And it’s workable for multiple Windows versions, like Windows Server 2022/2016/2012 R2 as well as Windows 11/10/8/7. Now follow me to know the operation.

Step 1. Install AnyViewer on both 2 PCs and then open it. Go to the “Log in” tab, and click on “Sign up”.

Log in AnyViewer

Step 2. Fill in the information to sign up.

Sign Up for AnyViewer

Step 3. Now you can see your interface as the following picture. And your device will automatically be assigned to the account you’ve logged in to.

Free Editions

Step 4. If you log the same account on another device, there will be 2 devices in the “My devices” tab. Click the PC that you need to control and click «One-click control» to achieve unattended access with one click.

Connect to My Devices

Step 5. The connection is established successfully.

You can also choose to upgrade to an advanced plan, with which you are able to enjoy the following advantages:

  • Enjoy Privacy Mode. With the feature Privacy Mode, the screen of the remote PC will be blackened and the keyboard & mouse would be disabled.
  • Transfer large files. No matter how large your files are, you can get file transfer without any limitation.
  • Bind more devices. After the upgrade, you are able to bind 10 devices for one-click unattended remote access and manage 100 devices.

Conclusion

The methods for resolving «Remote logins are currently disabled” on Server 2016 are illustrated in this post. However, you could use a third-party remote access software, such as AnyViewer, to easily establish a remote connection.

Remote logins are currently disabled что значит

I have a RDS farm with two RD Session Hosts. I use DNS Round Robin and life is good and everything working until I try to take out one of the servers from the farm. To do so I go to the RD Session Host Configuration | Member of farm in RD Connection Broker | General tab | and check ‘Allow connections, but prevent new logons’.

When users now try to connect to the farm and DNS resolves the farm entry rdsfarm1.domain.com with the IP pointing to the RD Session Host I disabled they see the message ‘Remote Logins are currently disabled’. If they hit the server which is not disabled then everything works fine.

I now found the following thread in this forum and in there is sounds like this is expected. I personally would have expected that disabled RDS Session Host is still forwarding requests to Connection Broker but that does not seem to be the case.

If this is expected and I would have to take additionally the DNS entry for the disabled server out as well then this would not work for us and we would have to implement NLB. But before I do that I wanted to double-check if my theory is correct or if I have setup something wrong.

Please let me know.

Thank you
Marcus

Answers

Your understanding is correct. If you use DNS RR for balancing the initial connections, then you will need to remove the DNS record if you take a server out of service for some reason. You may solve this issue by setting up dedicated redirector(s), using NLB, or using a rdp-aware hardware load balancer. For example, if you had a dedicated redirector you could take a RDSH server down for maintenance and things would still work as long as the redirector server and the other RDSH server were still working. The DNS entry for the farm would point to the redirector ip address instead of the RDSH servers.

  • Marked as answer by Mc2102 Thursday, April 5, 2012 5:28 PM

Yes, use Drainstop on the host you plan to take out of service. This will make sure that no new initial connections will be sent to the RDSH via NLB.

  • Marked as answer by Yuan Wang Microsoft employee Wednesday, April 25, 2012 7:44 AM

All replies

MSP Provider (Network,Hardware,Software,WAN/LAN,Exchange,WiFi,Cisco Controllers/Routers/Switches/AP Autonomous/LWAPP)

One of the scenarios would be that we want to take out a RD Session host for maintenance for example. Or because we have a problem with one of the apps on the server. Besides that we are looking for redundancy. So if we lose one of the servers we do not cause an outage for our users. The question actually is will a NLB solve that problem?

I read your statement ‘remove the downed server from your connection brokers RDS config’. I am not sure where I am supposed to do that. On the Connection Broker I do not see the function and on the RD Session Host if I uncheck the ‘Participate in Connection Broker load-Balancing’ checkbox on ‘RD Connection Broker’ tab does not prevent any new logins.

Your understanding is correct. If you use DNS RR for balancing the initial connections, then you will need to remove the DNS record if you take a server out of service for some reason. You may solve this issue by setting up dedicated redirector(s), using NLB, or using a rdp-aware hardware load balancer. For example, if you had a dedicated redirector you could take a RDSH server down for maintenance and things would still work as long as the redirector server and the other RDSH server were still working. The DNS entry for the farm would point to the redirector ip address instead of the RDSH servers.

  • Marked as answer by Mc2102 Thursday, April 5, 2012 5:28 PM

Thanks for your response. That is exactly the information I was looking for.

Here is just a small follow-up one. If I setup the NLB for my farm, and then take one of the RD Session Hosts out of my farm by clicking on ‘Allow connections, but prevent new logons’ do I also have to put the server into Drain mode in the NLB Manager or will that work automatically since the RD Session Host does not forward any requests to the connection broker anymore.

If you know the answer to this please let me know.

Yes, use Drainstop on the host you plan to take out of service. This will make sure that no new initial connections will be sent to the RDSH via NLB.

  • Marked as answer by Yuan Wang Microsoft employee Wednesday, April 25, 2012 7:44 AM
  • Proposed as answer by Badpandy Friday, April 27, 2012 12:36 PM
  • Unproposed as answer by Badpandy Friday, April 27, 2012 12:36 PM

Thanks for the tips, i was in trouble when i need to put a server out of order, i had to put it off from the Session broker Group on SB.

Whatever, i’ve another issue that produce the same error message. All my RDS server are virtualized on Hyper V, but sometimes, the dedicated redirector don’t forward the logon request to the SB and another RDS server for logon. It stays on redirector and display ‘remote login are currently disabled’.

As usual, i reboot the redirector but it does not solve the problem all the time. So i reboot the SB too, but i’m wondering how it’s possible. The servers aren’t busy (CPU & RAM are highly available) and the Hyper V host isn’t busy either. I’ve got 4 differents RDS farms, all with 2 dedicated redirector, 1 Session Broker and about 10 to 80 servers behind.

Windows Administrators Blog!

Online knowledge base and an Known Error DataBase (KEDB)

Remote Logins Are Currently Disabled

If you trying to connect to a RDP server and you get this error:

Remote logins are currently disabled.

Description: The user is attempting to log on to a Terminal Server where an administrator has disabled logon by issuing the CHANGE LOGON /DISABLE command. In order to enable logon, the CHANGE LOGON /ENABLE command must be issued.

You would require the help of psexec utility to gain access to the command prompt of the desired server. You the below syntax:

psexec.exe “\\SERVERNAME\ change logon /enable”

Overview of the CHANGE LOGON Command
The change logon command uses the following syntax:
change logon /enable | /disable | /query
The parameters that are used by the change logon command are:
/enable: Use this parameter to turn on logons from client sessions.
/disable: Use this parameter to turn off any further logons from client sessions. Currently-logged-on users are not affected.
/query: Use this parameter to display the current logon status.

NOTES: The change logon command applies to logons from client sessions. Logons from the console session are not affected.

Solutions to Fix Remote Logins are Currently Disabled Error Problem Issue

Remote logins are currently disabled error is a very commons error that user faces. The issue has been common when using the active directory, remote login on a domain controller, etc. Every time the user tries to log in to the server, the error appears and stops the login process. Furthermore, the error also appears while transferring the files from server to domain if you do not know how to troubleshoot this issue then it can be a headache in this article on troubleshooting this error. We will cover methods that will help eliminate this issue.

Remote Logins Are Currently Disabled

Table of Contents

Causes of Remote Logins are Currently Disabled Error Problem:

Remote Logins Are Currently Disabled Citrix Error can occur due to multiple reasons. If any user that has the administrator privileges may disable the logins using the changelogon command easily. In was if the RDP port is closed for connection in the security setup, then this error appears. Another issue in which this error appears is while using the Citrix application, as the app has some privacy policy that parents the user for remote logging in. Furthermore, the error also if the Host server is put into the drain mode.

  • Disable login
  • Citrix privacy policy
  • The host server is put into the drain mode
Similar Types of Remote Logins are Currently Disabled Error Issue:
  • Server 2016
  • Windows 2016
  • Change logon /enable
  • Change logon /enable remotely
  • Rds farm
  • 2016
  • Server 2008 r2
  • Terminal server sessions disabled remote logins currently disabled

How to Fix Remote Logins are Currently Disabled Error Issue

Troubleshooting Remote Logins Are Currently Disabled Citrix Error can be a little complicated. We have demonstrated methods that you can use to fix this error. The following are the methods. In the first method, we will manually enable the service or process using the command prompt. In the second method, we will enable the logon services using the Remote Desktop Session Host Configuration Utility. In the third method, we will fix the issue using the registry editor. Finally, in the fourth method, we will talk about some essential points that you should know.

1. Using Command Prompt –

In this method, we will fix the Remote Logins are Currently Disabled Citrix issue by using the command prompt. We will execute the command that will enable the disabled remote login services. Follow the steps.

  • STEP 1. In the Start menu, type cmd
  • STEP 2. Now right click on the command and click on Run as administrator
  • STEP 3. In the command prompt window, type the following command
  • /enable: This attribute is used to enable logins from client
  • /disable: This attribute is used to disable logins from the client, already logged on users will have no effect
  • /query: This attribute is used to display the current logon status

2. Using the Remote Desktop Session Host Configuration Utility –

In this Remote Logins are Currently Disabled Server 2008 method, we will the Remote Desktop Session Host Configuration Utility enable the logon services.

  • STEP 1. In the Start menu, type run and then hit Enter
  • STEP 2. Now in the Run box type tsconfig.msc and then hit Enter

tsconfig

  • STEP 3. In the Remote Desktop Session Host Configuration window, Under the Edit settings

RDHC

  • STEP 4. You will see that Restrict each user to a single session has been put Yes

RDHC

  • STEP 5. Right-click on Restrict each user to a single session > Properties
  • STEP 6. Now uncheck the Restrict, each user to a single session checkbox
  • STEP 7. Click on Apply then ok for getting back of this type of Remote Logins are Currently Disabled Server 2008 Citrix error.

3. Using Registry –

In this method, we will use the registry editor to resolve the Remote Logins are Currently Disabled Citrix issues. Kindly follow each step carefully as wrong changes may cause system instability. Follow the steps now.

  • STEP 1. Go to the Start > type in the search/run box regedit then hit Enter
  • STEP 2. In the registry editor navigate to the following path
  • STEP 3. On the Right Locate the fSingleSessionPerUser, then double click on it
  • STEP 4. In the Value data put 0, to allow Multiple sessions

fSingleSessionPerUser,

  • STEP 5. Save the changes and restart your system to get back from this Remote Logins are Currently Disabled Server 2008 problem.

4. Basic Troubleshooting –

Here we have mentioned some common verification points for getting rid out of this Remote Logins are Currently Disabled Server 2008 Citrix issue.

  • Make sure that the RDP port is allowed/open for connection in the security setup.
  • Make sure that the Host Server has not been put on “Do not allow new connections.
Conclusion:

We have seen four ways that will help you in eliminating Remote Logins Are Currently Disabled Citrix Error. The error only occurs if the netlogon or similar setting has been disabled. With this article you get all the methods by using step by step guide also we have briefly discussed its causes.

We hope these Remote Logins are Currently Disabled Citrix article resolves your issues. For more articles on troubleshooting, follow us. Thank you!

Добавить комментарий

Ваш адрес email не будет опубликован. Обязательные поля помечены *