Cisco error “remote user is disabled”

After you click Connect, no sign-in window appears. Two messages pop up instead. The first is the real cause; the second is only its consequence.

• VPN establishment capability for a remote user is disabled. A VPN connection will not be established.
• Cisco Secure Client was not able to establish a connection to the specified secure gateway. Please try connecting again.

Before connecting, the Cisco client checks whether the person using the PC signed in at the machine itself or came in remotely. If it is remote, the client refuses by default. This is a safety rule built into the client, meant to stop someone who has remoted into your PC from joining a network as you.

So the same PC and the same account connect fine when you sit in front of it, and fail when you are remoted in. Retrying or switching regions makes no difference.

To confirm whether you are in a remote session: press Win + R, type cmd and press Enter, then run the command below. The line marked with > is your current session. A session name starting with rdp-tcp means remote; console means you are signed in at the PC: query session

• You are controlling this PC with Windows Remote Desktop, from another computer, a phone or a tablet. This is the most common case.
• The PC is a cloud PC, cloud desktop or remote work machine. Most of them deliver the screen through Remote Desktop.
• You signed in through Remote Desktop earlier and never signed out. That session may still be active, so you can still be treated as a remote user at the keyboard.
• The PC has software that opens a remote session in the background: remote-control or remote-assistance tools, activity-monitoring software, management agents installed by an employer, and security suites such as 360 that bundle remote assistance and network protection. Not all of them trigger this error, but if you see it and are sure you are not using Remote Desktop, they are worth checking one by one.

1. Using Remote Desktop now: disconnect, sign in at the PC with its own keyboard and mouse, then click Connect.
2. Signed in remotely earlier: sign out of Windows or restart, sign in at the PC, then connect.
3. You must operate the PC remotely: use RustDesk, VNC or a similar tool that controls the local desktop instead of Windows Remote Desktop. These are not treated as a remote user.
4. Not using Remote Desktop but still seeing the error: open Settings → Apps → Installed apps, uninstall remote-control tools, monitoring software and security suites such as 360, restart, and try again. If it connects, one of them was the cause; reinstall the ones you need one at a time to find which.
5. Cloud PC or cloud desktop where you cannot change how you sign in: switch to OpenVPN or the browser proxy. Neither has this restriction, and the same account works.