Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Windows Error 623 means “Cannot find the phonebook entry.” The Windows Remote Access Service (RAS) or VPN client cannot find the connection profile name it was asked to use in the phonebook it searched. Check the exact profile name and phonebook path first, then repair or recreate the profile. Do not start by changing passwords or server authentication: those checks matter only after Windows has found the profile.
Error 623 is reused by unrelated products. If the message appeared in a streaming player, messaging-registration portal, or a standalone mobile device, the Windows procedure below is not the right fix. Identify the product and wording before changing anything.
As an Amazon Associate I earn from qualifying purchases.
What Windows Error 623 means
Microsoft’s Windows Client dial-up and VPN error list defines 623 as Cannot find the phonebook entry.
The RRAS error table names the condition ERROR_CANNOT_FIND_PHONEBOOK_ENTRY. In this context, a “phonebook” is the set of dial-up or VPN connection profiles that Windows RAS can search. A shortcut, script, rasdial command, or VPN client requests a connection by name; Windows returns 623 when that name is absent from the phonebook it is using.
Free tools Windows power users keep installed
One-click scans. No signup required.
The failure normally occurs before a username, password, certificate, or VPN server can be authenticated. A profile can still appear in the Settings app while a command fails if the command is pointed at a different phonebook (for example, a per-user file instead of an all-user file), or if the requested name differs by a space, punctuation mark, or other character.
#1 Best Overall
Microsoft documents RAS error definitions in raserror.h and provides the RasGetErrorString function for applications that need the human-readable text. That originating message is more reliable than a generic list of error numbers.
First identify which product displayed 623
The number alone is not enough to select a remedy. Compare the wording, screen, and point of failure with the following cases.
| Where 623 appeared | What it means there | First remedy |
|---|---|---|
Windows RAS, a Windows VPN or dial-up connection, or rasdial |
Windows cannot find the requested phonebook entry. | Verify the connection name and the phonebook path, then repair or recreate the profile. |
| Swank cloud-streaming player | Swank labels it Error Playing Video: Error Code 623, an unknown playback error. |
Restart the playback device, as Swank’s support table recommends. |
| Government of India DLT registration portal | PEID_NOT_MATCHED_WITH_HEADER: the principal-entity ID does not match the header ID. |
Correct the registration data or ask the platform administrator to reconcile the IDs. |
| WM090TD device | No mobile wireless network is available. | Check reception and retry later; the device instructions label the remedy “Try again later.” |
If the message includes a product name, use that product’s wording and support material. The Windows steps below apply only when the failure is tied to Remote Access, a Windows VPN or dial-up entry, or a RAS command.
Windows fix: verify the connection profile name
1. Record exactly what is being requested
Write down the complete error text and the action that triggered it. Note whether you clicked a VPN shortcut, selected a connection in Windows, ran a batch file, or used rasdial. Copy the connection name exactly as shown in the command or shortcut. Preserve spaces, punctuation, and capitalization; some calling tools compare the name literally.
A command such as rasdial "Work VPN" asks for an entry named Work VPN. It will not find an entry named WorkVPN, Work VPN with an accidental trailing space, or a similarly named profile in another phonebook. Do not rename the profile until you have recorded the name used by the caller, because that can make a script fail in a different way.
2. Check the Windows VPN and dial-up lists
- In Windows 11 or Windows 10, open Settings > Network & internet > VPN and look for the connection name. Select it to confirm that the profile still exists.
- If the connection is a traditional dial-up or RAS entry, open Control Panel > Network and Internet > Network and Sharing Center and inspect the available connection options. Older Windows editions may expose the list through Control Panel > Network Connections.
- Compare the displayed name character by character with the name in the shortcut, script, or command. A profile that is visible under one spelling does not satisfy a request for another spelling.
If the requested entry is not listed, Windows has nothing to look up under that name. Recreate the profile using the provider’s server address and authentication requirements, or correct the script to call the existing profile. If the entry is listed but 623 persists, continue with the phonebook-path check rather than assuming the server or credentials are wrong.
Check the phonebook path
When a command or script specifies a file
RAS commands and applications can be directed to a particular phonebook. Inspect the complete command line, shortcut target, scheduled task, or script for a phonebook argument and record the path. Confirm in File Explorer that the file exists, that the spelling is correct, and that the account running the command can read it.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Windows commonly maintains separate per-user and all-user RAS phonebooks. A profile created for your account may not be present in an all-user phonebook, and a machine-wide profile may not appear when a per-user file is searched. Use the same scope when recreating the connection as the scope expected by the command.
When no path is visible
A shortcut may call a VPN client that chooses its own phonebook. Open that client’s connection-management screen and verify which profile or connection group it uses. If an administrator supplied the shortcut, ask for the intended phonebook location instead of guessing. Record the Windows edition, VPN client name, connection name, and any path shown in logs; these details allow the administrator or vendor to reproduce the lookup.
Check access and file integrity
- Make sure the phonebook file was not moved, renamed, or deleted during a profile migration or user-account change.
- Check that the file is not on a disconnected network drive or removable disk.
- If the file opens but the entry is missing or malformed, export any needed settings and recreate the connection rather than editing the file by hand.
- When multiple users share a computer, test from the account that normally runs the shortcut. A profile available to one account may not be available to another.
Repair or recreate the missing profile
Use the built-in Windows VPN form
- Open Settings > Network & internet > VPN and choose Add VPN (the exact button text can vary by Windows release).
- Set the VPN provider to the built-in Windows option when the service is designed for Windows’ native client. Enter the server address, connection name, VPN type, and sign-in method supplied by your organization or VPN provider.
- Save the profile, then compare the saved connection name with the name used by the shortcut or script. If the script expects
Work VPN, use that exact name or update the script deliberately. - Connect from the Settings page first. This separates a profile-creation problem from a shortcut or automation problem.
Do not guess a VPN type, server address, certificate, or authentication method. Those values are service-specific. If the provider supplied an import file or installer, use its documented procedure and verify the resulting profile name afterward.
Rebuild a legacy dial-up or RAS entry
For a dial-up or older RAS connection, open the connection wizard exposed by your Windows edition, select the appropriate modem or network device, and enter the number or server details supplied by the service. Give the entry the exact name expected by the calling application. Test it interactively before restoring any automated connection.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Repair a shortcut or script after rebuilding
Once the profile connects from Windows, edit the shortcut or script so it calls that same name and phonebook scope. Run the command manually in a console under the same user account used by the automation. If the interactive connection works but the script still returns 623, the script is still selecting a different name or file; capture its full command line for troubleshooting.
Use rasdial carefully
rasdial can connect to a named entry and can be directed to a specific phonebook. A typical name-only test is rasdial "Work VPN". If the environment uses a specific file, use the phonebook option documented for that command and supply the complete path rather than relying on a default. Avoid putting passwords in scripts or command history; use the organization’s approved credential method.
Run the test from the account that owns the profile. If the command succeeds without a path but fails when a path is supplied, the supplied file is not the one containing the entry. If both forms fail with 623, compare the requested name with the connection list again and verify that the profile was saved under the expected scope.
What Error 623 does not prove
- It does not by itself show that the VPN server is offline.
- It does not establish that a password, certificate, or multifactor token is invalid.
- It does not prove that the computer has malware or that Windows networking is generally broken.
- It does not identify a single universal driver problem.
Investigate authentication, firewall policy, DNS, routing, or server availability only after the client can locate and start the requested profile. If the error changes to an authentication or connection-stage code after the profile is found, troubleshoot that new condition separately.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsWhen a legacy Dell mobile-broadband case applies
Dell’s Wireless 5720 VZW Mobile Broadband Mini Card driver page, released 18 May 2009, records a fix for the specific symptom: When trying to auto connect to VPN using Dell Dragnet user gets ‘error code 623’.
The package targets legacy Dell systems running Windows XP or Windows Vista.
Best Value
This is not a current, universal Windows 10 or Windows 11 remedy. Use it only when the computer is the matching Dell model, the Wireless 5720 VZW card and Dell Dragnet software are involved, and the operating-system requirements on Dell’s model-specific support page are satisfied. For other Dell cards, newer Windows editions, or a built-in Windows VPN, return to the profile-name and phonebook checks above.
If 623 came from another product
Swank cloud streaming
Swank’s support table uses the wording Error Playing Video: Error Code 623
for an unknown playback error. Restart the playback device as the listed remedy. If the message returns, note the player, device model, title being played, and whether other videos work; those details are more useful to the service’s support team than Windows RAS diagnostics.
Government of India DLT registration
The DLT error-code document defines 623 as PEID_NOT_MATCHED_WITH_HEADER. Check that the principal-entity ID in the registration record matches the ID carried in the header. This is a registration-data correction, not a Windows VPN repair.
WM090TD device instructions
WM090TD instructions labeled January 2023 describe 623 as “No mobile wireless network available” and advise trying again later. Check the device’s signal or service availability, move to an area with reception if appropriate, and retry. Do not delete Windows VPN profiles for this device-level message.
When to escalate
Escalate to your administrator, VPN provider, or hardware vendor after you have recorded the exact error wording, Windows edition, VPN or device model, connection name, command used, phonebook path, and the point at which the failure occurs. Include whether the profile appears in the Windows connection list and whether a newly recreated profile changes the error. Do not send passwords or private keys in a support ticket.
Quick Recap
As an optional shortcut after the manual checks, Outbyte PC Repair can look for more than 100 common Windows issues, including broken system elements, and includes an app-crash log; it runs on Windows 11, 10, 8 and 7. Its free trial is offered by category for at least two days before a paid subscription. Results vary, it does not repair every crash, and it complements rather than replaces antivirus software.
Practical decision checklist
- Windows RAS/VPN wording: compare the requested profile name with the entry list.
- A phonebook path is supplied: verify the file exists, is the intended per-user or all-user file, and is readable by the calling account.
- The entry is missing: recreate it with the provider’s exact settings, then test interactively.
- The entry exists but 623 remains: inspect the command, shortcut, VPN client, and account scope for a different phonebook.
- The message came from streaming, DLT registration, or a WM090TD device: use that product’s remedy instead of Windows VPN steps.
- A matching 2009 Dell Dragnet case: consult the model-specific Dell release information; do not treat the legacy driver as a general fix.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
