What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
On a Windows 9x client dialing a Windows NT 4.0 RAS server running Service Pack 4 or later, error 649 can be triggered by the client computer name System. Rename the client to a unique workstation name, apply the change, reboot if requested, and try the dial-up connection again. If the client is not named System, investigate normal RAS authorization instead.
What JSI Tip 1426 describes
Jerold Schulman’s JSI Tip 1426, published June 25, 1999, covers a narrowly defined Windows NT 4.0-era failure: a Windows 9x computer dialing a Windows NT RAS server updated to Service Pack 4 or later (often written as “SP4+”). The report identifies the client computer name System as the decisive condition.
As an Amazon Associate I earn from qualifying purchases.
This is a legacy dial-up RAS issue, not a general fix for every modern Windows VPN or Remote Access Service error.
Free tools Windows power users keep installed
One-click scans. No signup required.
Source: JSI Tip 1426 (June 25, 1999).
Why error 649 sends you in the wrong direction
Microsoft’s general error-code reference defines RAS error 649 as The account does not have Remote Access permission.
That normally points an administrator toward user dial-in settings, server policy, or authentication.
#1 Best Overall
- Server 2022 Standard 16 Core
In the JSI case, however, the same number appears when the client computer itself is named System. The visible message therefore resembles an account-permission failure even when the unusual machine-name condition is the real trigger. Microsoft’s current reference documents the generic meaning; it does not independently document the historical System-name condition.
Source: Microsoft: Error codes for dial-up or VPN connections.
Rank #2
- Server 2025 will be delivered by post, FPP version
- Enterprise Security – Built-in advanced security features including Hotpatching for seamless updates and Credential Guard to protect against unauthorized access.
- Hybrid Cloud Integration – Connects seamlessly with cloud-based services for efficient management of on-premise and cloud infrastructure
- Optimized Performance – Enhanced networking and storage capabilities with improved data handling and support for high-performance workloads
- User-Friendly Interface – A modernized desktop experience with streamlined management tools such as WinGet and Terminal.
How the symptom is displayed
| Client or system | Displayed wording |
|---|---|
| Windows 9x | “Error 649: You do not have dial-in permission. Change the permissions on the computer you are dialing in to, or contact your network administrator.” |
| Windows NT | “Error 649: The account does not have remote access permission.” |
The wording differs by operating system, but the JSI report ties the Windows 9x failure to a client named System when connecting to an SP4-or-later NT RAS server.
Recommended Free Tools
Check these facts before changing anything
- Confirm that the client is running Windows 9x, such as Windows 95, 98, or Me.
- Confirm that the destination is a Windows NT 4.0 RAS server, not a current RRAS, VPN, or third-party gateway.
- Establish that the server has Windows NT Service Pack 4 or a later service pack. “SP4+” means Service Pack 4 or later, not a separate product or build designation.
- Check the client’s computer name. The reported trigger is the name exactly shown as
System.
The original tip does not specify whether system, SYSTEM, or other variants behave the same way, so do not assume that every capitalization or every reserved-looking name is affected.
Rank #3
- Offers quick and easy installation on PC
- The software is licensed for 5 User CAL
Documented remedy: rename the client
- Open the Windows 9x computer-identification or network-identification settings. The exact dialog labels vary by release.
- Replace
Systemwith a short, unique workstation name that fits the naming limits of that installation. - Apply the change and restart the computer if Windows requests a reboot.
- Retry the same dial-up RAS connection.
JSI Tip 1426 presents renaming as the fix for this exact condition. It does not provide a command-line procedure, registry edit, or separate hotfix identifier. Choose a name that does not duplicate another computer and avoid names that look like operating-system or service identities. The source does not prescribe a particular replacement name.
If renaming does not resolve error 649
Do not treat the rename as a universal answer. If the client was not named System, or the error remains after the name change and restart, return to ordinary RAS authorization checks:
Rank #4
- Verify that the user account is allowed to use remote access or dial-in.
- Check server-side RAS authorization and any applicable policy.
- Confirm that the modem is dialing the intended NT RAS server.
- Review account restrictions, password state, domain or local authentication, and authentication-protocol compatibility.
- Confirm that the server is configured to accept incoming RAS calls.
- Make sure the error is not coming from a different RAS, VPN, or network-access implementation.
Later Windows Server environments can evaluate account settings and network policies through Network Policy Server. Those mechanisms are useful diagnostic background, but they are not evidence that the 1999 System-name condition used the same policy architecture.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Background: Microsoft: Configure Network Policies and Microsoft: Install and configure a VPN server.
Best Value
What is—and is not—established
The historical report strongly supports a naming defect or reserved-name interaction in the Windows NT 4.0/Windows 9x RAS path. It does not identify the internal code path, affected NT build numbers beyond SP4 or later, a formal Microsoft bulletin, or a hotfix. It also does not establish effects for modern Windows systems.
Quick Recap
Quick-reference checklist
- Windows 9x client
- Windows NT 4.0 RAS server
- Server running Service Pack 4 or later
- Client computer name exactly
System - Rename to a unique name and reboot if prompted
- If unresolved, check genuine remote-access authorization and server configuration
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.
