Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 691

VPN error 691: username or password rejected by the remote access server

11 min read Updated October 5, 2026 Networking, Sharing & Printing

Fix it now

The remote access server received your credentials and refused them, so the network path and the tunnel are already working. Microsoft publishes 691 as access denied because the user name or password is invalid on the domain, but the same refusal is what you see when a network policy declines the connection, so read the event on the policy server before changing anything.

Run these on the Network Policy Server, in an elevated PowerShell session

Get-WinEvent -LogName Security -MaxEvents 40 | Where-Object Message -match "Network Policy Server" | Format-List TimeCreated,Id,Message
Get-ADUser <user> -Properties Enabled,LockedOut,PasswordExpired,msNPAllowDialin | Format-List Name,Enabled,LockedOut,PasswordExpired,msNPAllowDialin
  1. Read the newest event first. It records the account name exactly as it was submitted, the policy that matched, and a reason in plain words. That single entry tells you whether you have an authentication problem or an authorisation one.
  2. If the name in the event is not the name you expected, retype the credentials in the connection using the down-level form, domain backslash user. A profile keeps its own saved copy and will replay an old password indefinitely.
  3. If the event names no matching policy, open the Network Policy Server console, check the conditions on each policy and the order they are evaluated in. The first policy whose conditions match is the one that decides.
  4. If msNPAllowDialin comes back False, that is an outright deny on the account. Set the network access permission on the user object to be controlled through policy unless the deny was deliberate.

Get-ADUser needs the Active Directory module for Windows PowerShell, which comes with the Remote Server Administration Tools. On a server that does not have it, read the same three states on the Account and Dial-in tabs in Active Directory Users and Computers.

If the connection now completes you can stop here. If not, the next section explains which of the two decisions behind this error is refusing you.

Why it happens

A remote access logon is decided twice. First the credentials are authenticated: the account is located and the password or certificate verified. Then the connection is authorised: the policy engine decides whether this user, on this kind of connection, at this time, is permitted at all. Failing either produces a rejection at the client, and 691 is the label the client puts on both.

This is why the event written on the policy server matters more than anything you can see on the laptop. It carries the account name as submitted, which is frequently not what the user believes they typed, the name of the policy that matched, and a reason. A rejection naming no policy is an authorisation problem. A rejection naming a credentials mismatch is an authentication problem. Guessing between them without that event is where most of the time on this error goes.

Some account states surface as numbers of their own instead. Microsoft publishes 647 as the account being disabled, 648 as the password having expired, 708 as the account itself having expired, and 649 as the account not having Remote Access permission. Where you get one of those, the diagnosis is already done. Which one you get depends on the authentication method in use, so do not read a bare 691 as ruling any of them out.

The identity is being submitted in a form the server will not accept

You have this one if The event on the policy server shows a user name you do not recognise, or shows the domain missing altogether.

  1. Enter the domain and user name explicitly rather than relying on the connection to supply the domain.
  2. Try the user principal name form as a second test, and check which form the policy conditions expect.
  3. Delete and re-enter the saved credentials on the client, because the profile holds its own copy.

A password changed since the connection last worked is the single most common cause. The saved copy is what is being sent.

Dial-in permission or the matching policy denies the connection

You have this one if The credentials are right and the event names either no matching policy or a policy that denied access.

  1. On the user object, set the network access permission to be controlled through policy rather than denied.
  2. Check the conditions on the policy that should match: group membership, connection type, and any restriction on time or client.
  3. Check policy order. Policies are evaluated top down and the first match decides, so a broad deny above your allow policy always wins.

The account is not in a state that permits any logon

You have this one if Codes 647, 648 or 708 rather than 691, or an event naming the account state.

  1. Enable, extend or reset as appropriate, having first checked that the state was not deliberate.
  2. For an expired password, have it changed on the internal network or through self-service. Most remote access methods have nowhere to present a change prompt.
  3. Retry once the directory shows the account usable.

The two ends cannot agree on an authentication method

You have this one if The credentials are certainly correct and the event points at the method rather than at the account.

  1. Compare the methods enabled on the client connection with those the matching policy allows, and make sure at least one is common to both.
  2. Where a certificate-based method is required, confirm the client actually holds a usable certificate before blaming the password.
  3. Change one end so both offer the same method, rather than enabling everything on both.

Enabling weak methods to make a connection work leaves them enabled afterwards. Agree on a strong method both ends support.

The access server and the policy server are not talking

You have this one if Code 645, or no event at all on the policy server for attempts the client is plainly making.

  1. Confirm the access server is defined as a RADIUS client on the policy server, with the right address.
  2. Re-enter the shared secret on both sides. A mismatch produces silence rather than a clear message.
  3. Confirm the policy server is registered in Active Directory so it can read account information.

645 is published only as an internal authentication error. Treat it, or the absence of any event, as a prompt to check the RADIUS relationship – not as proof that the shared secret is wrong.

Full reference

The six numbers and what Microsoft publishes for each

Code Published meaning What to do first
691 Access denied because the user name and/or password is invalid on the domain Read the policy server event; check the submitted name
649 The account does not have Remote Access permission Check the network access permission on the user object
645 Internal authentication error Check the RADIUS client entry, the shared secret and NPS registration
647 The account is disabled Enable it, or confirm the disable was intended
648 The password has expired Change it on the internal network first
708 The account has expired Extend the account expiry date in the directory

Note what 645 does not say. It is published as an internal authentication error and nothing more. It is a reasonable prompt to look at the relationship between the access server and the policy server, because that is where internal failures tend to live, but it does not identify a shared secret mismatch and re-keying secrets on the strength of it is guesswork.

Telling the two decisions apart from the event alone

What the event says Which decision failed Where to work
A credentials mismatch, naming a policy Authentication The account and the submitted name
Access denied, naming a policy Authorisation That policy’s conditions and constraints
No matching network policy was found Authorisation Policy order and conditions
The account is disabled, expired or locked Authentication The directory, not the VPN
Nothing at all for the attempt Neither yet The RADIUS client entry and the shared secret

Checking the account without opening five consoles

What you want to know Command
Is the account enabled, locked or expired Get-ADUser <user> -Properties Enabled,LockedOut,AccountExpirationDate | Format-List
Has the password expired Get-ADUser <user> -Properties PasswordExpired,PasswordLastSet | Format-List
What does the Dial-in tab say Get-ADUser <user> -Properties msNPAllowDialin | Format-List
Which groups does the policy match on Get-ADPrincipalGroupMembership <user> | Select-Object Name
What did the policy server decide Windows Logs, Security, on the policy server

msNPAllowDialin is the attribute behind the Dial-in tab’s network access permission. True is an explicit allow, False is an explicit deny that overrides your policies, and an empty value means the decision is left to network policy – which is what you want in almost every deployment, because it puts the rule in one place instead of on ten thousand user objects.

When the account and the policy both check out

  • Test a second account in the same group. If it works, the problem is the user object, not the policy.
  • Test the same account from a second device. If that works, the problem is the profile and its saved credentials.
  • Check whether the account is subject to a logon hours restriction. It is enforced on remote access too and produces a policy denial that looks like a password problem.
  • Check for an account lockout that has already expired by the time you look. The event on the policy server carries the time; the account state you are reading does not.
  • Where several policy servers exist, confirm which one answered. They can drift apart, and testing against the wrong one proves nothing.

Things that will not help

  • Recreating the VPN profile. It replaces the saved credentials, which is occasionally the fix, but it tells you nothing and hides what was wrong.
  • Adding the user to more groups. If the policy is not matching, more group memberships usually make policy order harder to reason about rather than easier.
  • Enabling extra authentication methods on the client. If the methods already overlap, this changes nothing; if they do not, fix the mismatch on purpose.
  • Restarting the remote access service. It clears nothing relevant to a decision taken on another machine.

Every code this article covers

Code What it points at Source
691 Access denied because the user name and/or password is invalid on the domain Microsoft Learn
649 The account does not have Remote Access permission Microsoft Learn
645 Internal authentication error. Microsoft publishes nothing more specific, so treat it as a prompt to check the access server’s RADIUS relationship rather than as a diagnosis Microsoft Learn
647 The account is disabled Microsoft Learn
648 The password has expired Microsoft Learn
708 The account has expired Microsoft Learn

Confirm the fix worked

  1. Reconnect and confirm the policy server logs a granted connection naming the policy you expect.
  2. Confirm the client is issued an address and can open an internal resource by name.
  3. Test with a second account in the same group, to prove the policy matches the group rather than one user.
  4. Disconnect and reconnect once more, so you know the success was not the result of one manual credential entry.
  5. Confirm no authentication method was left enabled that you only turned on to test.

Questions people ask about this

Do I need to buy anything to fix this?

No. Routing and Remote Access and Network Policy Server are roles included with Windows Server, and everything here is configuration. If you have a server, you have the tools.

Why does the same account work in the office and fail over the tunnel?

Because the office logon is decided once, by a domain controller, and the remote connection is decided twice. The second decision is policy, and an account can be entirely valid and still not be authorised for remote access.

The user swears the password is right. Now what?

Read the policy server event. It records the name as submitted, which is often not what the user believes they typed, and it separates a credentials mismatch from a policy rejection in plain words.

Can users change an expired password over the connection?

Usually not. Most remote access authentication methods have nowhere to present a change prompt, so the attempt simply fails with 648. Have the password changed on the internal network or through a self-service portal first.

I got 645. Is the shared secret wrong?

Maybe, but the code does not say so. Microsoft publishes 645 only as an internal authentication error. Check the RADIUS client entry, the shared secret and whether the policy server is registered in Active Directory, and treat all three as candidates rather than re-keying on the strength of the number.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix Error 0x8009030C: logon denied when NTLM is blocked or restricted Free Fix Duplicate name on the network 0x80070034 and a broken Winsock TCP stack License Error Error 0x80092012: TLS inspection breaks certificate checks on the client License Error Error 0x80070047: no more connections can be made to this remote computer
โ† Back to Knowledge Base