How to Fix the Modem or Other Connecting Device Is Already in Use Error 633
WindowsResolve Error 633 and restore VPN or modem connectivity in Windows by identifying port conflicts, updating registry settings, and managing device configurations.

“Error 633 – the modem (or other connecting device) is already in use or is not configured properly” appears when attempting to establish a VPN connection or use a modem in Windows. This issue is typically caused by a conflict over TCP port 1723, which is required for PPTP VPN connections, or by multiple processes attempting to access the same device. The result: VPN or modem connections fail until the conflict is resolved.
Reserve TCP Port 1723 for VPN Connections
Step 1: Open the Registry Editor by pressing Windows + R
, typing regedit.exe
, and pressing Enter
. If prompted by User Account Control, approve the action.

Step 2: Navigate to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

Step 3: In the right pane, right-click and select New > Multi-String Value
. Name this value ReservedPorts
.

Step 4: Double-click ReservedPorts
, and in the Value data field, enter 1723-1723
to reserve the port for VPN use. Click OK
and close the Registry Editor.

Step 5: Restart your computer to apply the changes. This ensures that port 1723 is reserved for VPN connections and prevents other processes from claiming it.
Identify and Stop Processes Using Port 1723
Step 1: Open Command Prompt as an administrator by opening the Start menu, typing cmd
and selecting Run as administrator
.

Step 2: At the prompt, enter the following command to display active connections and the processes using them:
netstat -aon

This lists all active TCP and UDP connections, including the local port number and associated process ID (PID).
Step 3: Look for any entry where the local address includes :1723
. Note the PID in the last column for that entry.
Step 4: To terminate the process using port 1723, run:
taskkill /PID [PID] /F

Replace [PID]
with the process ID you identified. The /F
flag forces the process to end. Closing the conflicting process frees up port 1723 for your VPN connection.
Step 5: Exit the Command Prompt and attempt to reconnect your VPN or modem device.
Remove and Reinstall WAN Miniport Adapters
Virtual WAN Miniport adapters can sometimes become misconfigured, especially after driver changes or failed VPN sessions. Resetting these adapters can resolve Error 633.
Step 1: Open Device Manager by right-clicking the Start menu and choosing Device Manager
.

Step 2: From the View
menu, select Show hidden devices
to display all network adapters.

Step 3: Expand the Network adapters
section and locate WAN Miniport entries (such as WAN Miniport (PPTP)
, WAN Miniport (L2TP)
, etc.).

Step 4: Right-click each relevant WAN Miniport adapter and select Uninstall device
. Confirm any prompts.

Step 5: After uninstalling, click Action > Scan for hardware changes
in Device Manager. Windows will automatically reinstall the WAN Miniport adapters with default settings.

Step 6: Restart your computer and test your VPN or modem connection again.
Restart the Computer
Sometimes, a simple restart can clear temporary conflicts where a previous VPN or modem session has not released the port or device properly. After rebooting, try to establish your connection again. This method is quick and frequently resolves transient issues without further troubleshooting.
Check VPN Connection Limits and Device Configuration
Windows restricts the number of concurrent VPN sessions, usually to two. Attempting to start multiple VPN connections can trigger Error 633. To check the current limit, open Command Prompt and run:
netsh ras show wanports

If you need more simultaneous connections, increase the maximum ports for your WAN Miniport device by running:
netsh ras set wanports device="WAN Miniport (L2TP)" maxports=3

Replace WAN Miniport (L2TP)
with the adapter type you use. Restart for changes to take effect.
Resolving Error 633 restores reliable VPN or modem connectivity by preventing port conflicts and device misconfiguration. Regularly updating drivers and reviewing device settings helps avoid recurrence of this issue.
Comments