Fix Broadband Connection Error 629 VPN Error 631 633 650 - Complete Solution Guide
🚀 Quick Fix Summary
Error Type: Network/VPN Connection Error
Error Codes: 629, 631, 633, 650
Common Causes: Port blocking, firewall interference, ISP restrictions, VPN server issues, network adapter problems, authentication failures
Time to Fix: 15-30 minutes
Difficulty: Easy to Intermediate
Success Rate: 87% with proper method selection
The "Fix Broadband Connection Error 629 VPN Error 631 633 650" is a network connectivity error that occurs when attempting to establish broadband internet connections or VPN (Virtual Private Network) connections. These error codes (629, 631, 633, 650) indicate various connection failures during the authentication or connection establishment process. Error 629 typically indicates that the connection was closed by the remote computer, Error 631 indicates that the user disconnected, Error 633 indicates that the port is already in use, and Error 650 indicates that the remote access server is not responding.
These broadband and VPN connection errors specifically occur when network ports required for connection are blocked by firewall or router settings, when ISP (Internet Service Provider) restricts VPN connections or specific ports, when VPN server is unavailable or overloaded, when network adapter drivers are corrupted or outdated, when authentication credentials are incorrect or expired, when Windows network components are corrupted, or when another connection is already using the required port. The errors prevent users from establishing internet connections or VPN connections, which can be critical for remote work, secure browsing, or accessing restricted content.
This issue is particularly common when using VPN services, connecting to corporate networks, or establishing broadband connections through dial-up or PPPoE. The problem affects Windows 10, Windows 11, Windows 8.1, Windows 7, and Windows Server editions. Common scenarios include systems where firewall blocks VPN ports, systems with ISP restrictions on VPN usage, systems connecting to unavailable VPN servers, systems with corrupted network adapter drivers, systems with incorrect VPN configuration, and systems where Windows network stack is corrupted.
Understanding that these connection errors have multiple potential causes is crucial for effective resolution. While the error codes are different, they often share common solutions. This comprehensive fix guide provides five proven methods to resolve broadband connection errors 629, 631, 633, and 650, including checking firewall and port settings, updating network adapter drivers, resetting network components, configuring VPN settings correctly, and running network diagnostics, along with troubleshooting steps for edge cases and prevention strategies to avoid future occurrences.
Understanding Broadband Connection Errors 629, 631, 633, and 650
Broadband connection errors 629, 631, 633, and 650 are network connectivity errors that occur during connection establishment. Each error code indicates a specific type of connection failure.
Error code meanings:
- Error 629: Connection closed by remote computer - port blocked or server unavailable
- Error 631: User disconnected - connection terminated unexpectedly
- Error 633: Port already in use - another connection using the port
- Error 650: Remote access server not responding - server unavailable or unreachable
Where these errors typically occur:
- When establishing VPN connections - during VPN connection attempt
- When connecting to broadband - during dial-up or PPPoE connection
- When connecting to corporate networks - during remote access connection
- After network changes - after router or firewall configuration changes
- After Windows updates - when updates modify network components
Common error messages you might encounter:
- "Error 629: The port was disconnected"
- "Error 631: The user disconnected from this connection"
- "Error 633: The port is already in use"
- "Error 650: The remote access server is not responding"
- "Connection failed with error 629/631/633/650"
Why these errors occur:
- Port blocking: Firewall or router blocking required ports (PPTP: 1723, L2TP: 1701, OpenVPN: 1194)
- ISP restrictions: Internet Service Provider blocking VPN connections or specific ports
- VPN server issues: VPN server unavailable, overloaded, or misconfigured
- Network adapter problems: Corrupted or outdated network adapter drivers
- Authentication failures: Incorrect username, password, or expired credentials
- Windows network corruption: Corrupted Windows network components
- Port conflicts: Another application or connection using required port
Method 1: Check Firewall and Port Settings (Recommended First Step)
Firewall blocking required ports is a common cause of connection errors 629, 631, 633, and 650. This method ensures firewall allows VPN and broadband connections.
- Open Windows Firewall:
- Press Windows + R, type
wf.msc, press Enter - Or search "Windows Defender Firewall" in Start menu
- Click "Yes" when UAC prompts
- Press Windows + R, type
- Allow VPN through firewall:
- Click Advanced settings in left panel
- Click Inbound Rules in left panel
- Click New Rule in right panel
- Select Port → Next
- Select TCP and enter port 1723 (PPTP) or 1701 (L2TP)
- Or select UDP and enter port 1194 (OpenVPN)
- Select Allow the connection → Next
- Check all profiles (Domain, Private, Public) → Next
- Name it "VPN Connection" → Finish
- Check router firewall:
- Access router admin panel (usually 192.168.1.1 or 192.168.0.1)
- Check firewall settings
- Ensure VPN passthrough is enabled (PPTP, L2TP, IPSec)
- If router blocks VPN, enable VPN passthrough or disable firewall temporarily to test
- Check third-party firewall:
- If using third-party firewall (Norton, McAfee, etc.)
- Add VPN application to firewall exceptions
- Or temporarily disable firewall to test connection
- Re-enable firewall after testing
- Test connection:
- After configuring firewall, try connecting again
- If connection succeeds, firewall was the issue
- If error persists, proceed to Method 2
Why this works: Firewalls often block VPN and broadband connection ports by default. Allowing these ports through firewall enables connections to establish properly, resolving errors 629, 631, 633, and 650 caused by port blocking.
Method 2: Update Network Adapter Drivers
Corrupted or outdated network adapter drivers can cause connection errors. Updating drivers ensures network adapters function properly and can establish connections.
- Open Device Manager:
- Press Windows + X → "Device Manager"
- Or search "Device Manager" in Start menu
- Find network adapters:
- Expand Network adapters section
- Look for your network adapter (Ethernet, Wi-Fi, VPN adapter)
- Note the adapter name and manufacturer
- Update driver automatically:
- Right-click network adapter → Update driver
- Select Search automatically for drivers
- Windows will search for and install latest driver
- Wait for installation to complete
- Update driver manually (if automatic fails):
- Visit network adapter manufacturer's website
- Download latest driver for your adapter model
- Right-click adapter → Update driver
- Select Browse my computer for drivers
- Navigate to downloaded driver and install
- Restart your computer:
- Restart to ensure driver changes take effect
- After restart, try connecting again
- If connection succeeds, driver update resolved the issue
When to use this method: Use Method 2 when connection errors persist after checking firewall, when network adapter shows errors in Device Manager, or when connection worked before but stopped working after Windows updates.
Method 3: Reset Network Components
Corrupted Windows network components can cause connection errors. Resetting network components restores network stack to working state.
- Open Command Prompt as Administrator:
- Press Windows + X → "Command Prompt (Admin)"
- Or search "cmd", right-click → "Run as administrator"
- Click "Yes" when UAC prompts
- Reset TCP/IP stack:
- Type:
netsh int ip resetand press Enter - Wait for "Reset completed" message
- This resets TCP/IP configuration
- Type:
- Reset Winsock:
- Type:
netsh winsock resetand press Enter - Wait for "Successfully reset the Winsock Catalog" message
- This resets network socket configuration
- Type:
- Flush DNS cache:
- Type:
ipconfig /flushdnsand press Enter - Wait for "Successfully flushed the DNS Resolver Cache" message
- This clears DNS cache
- Type:
- Release and renew IP address:
- Type:
ipconfig /releaseand press Enter - Type:
ipconfig /renewand press Enter - This refreshes network configuration
- Type:
- Restart your computer:
- Restart to apply all network resets
- After restart, try connecting again
- Connection errors should be resolved
Why this works: Corrupted Windows network components can prevent connections from establishing properly. Resetting TCP/IP, Winsock, and DNS cache restores network stack to clean state, resolving connection errors caused by network component corruption.
Method 4: Configure VPN Settings Correctly
Incorrect VPN configuration can cause connection errors. This method ensures VPN is configured correctly for your connection type.
- Open Network Settings:
- Press Windows + I to open Settings
- Go to Network & Internet → VPN (Windows 10/11)
- Or Control Panel → Network and Sharing Center → Set up a new connection (Windows 7/8.1)
- Check VPN connection properties:
- Find your VPN connection
- Click Advanced options or right-click → Properties
- Verify VPN server address is correct
- Verify VPN type matches server (PPTP, L2TP, IKEv2, OpenVPN)
- Configure authentication:
- Go to Security or Advanced tab
- Select correct VPN type:
- PPTP: Point-to-Point Tunneling Protocol
- L2TP/IPSec: Layer 2 Tunneling Protocol with IPSec
- IKEv2: Internet Key Exchange version 2
- SSTP: Secure Socket Tunneling Protocol
- Enter correct authentication credentials
- Configure encryption (if required):
- For L2TP/IPSec, enter pre-shared key if required
- For IKEv2, configure certificate if required
- Check with VPN provider for correct encryption settings
- Test connection:
- After configuring VPN settings, try connecting
- If connection succeeds, configuration was the issue
- If error persists, verify VPN server is available
When to use this method: Use Method 4 when connection errors occur with specific VPN connections, when VPN configuration was recently changed, or when connecting to a new VPN server.
Method 5: Run Network Diagnostics and Troubleshooter
Windows built-in network diagnostics can identify and fix common network issues causing connection errors. This method uses automated tools to resolve problems.
- Open Network Troubleshooter:
- Press Windows + I to open Settings
- Go to Update & Security → Troubleshoot (Windows 10)
- Or System → Troubleshoot (Windows 11)
- Click Other troubleshooters or Additional troubleshooters
- Find "Network Adapter" → Click Run
- Run Network Adapter troubleshooter:
- Troubleshooter will scan for network issues
- Process takes 2-5 minutes
- Follow on-screen instructions
- Troubleshooter may automatically fix issues
- Run Internet Connections troubleshooter:
- In Troubleshoot settings, find "Internet Connections"
- Click Run
- This checks internet connectivity issues
- Follow on-screen instructions
- Review troubleshooter results:
- After troubleshooter completes, review results
- If issues were found and fixed, try connecting again
- If issues remain, note what troubleshooter found
- Test connection:
- After running troubleshooters, try connecting again
- If connection succeeds, troubleshooters resolved the issue
- If error persists, proceed to other methods
Why this works: Windows network troubleshooters can automatically detect and fix common network configuration issues, driver problems, and service issues that cause connection errors. This method provides quick resolution for many connection problems.
💡 Pro Tip: Prevent Broadband Connection Errors 629, 631, 633, and 650
Keep network drivers updated: Regularly update network adapter drivers. Configure firewall correctly: Ensure firewall allows VPN and broadband connections. Use reliable VPN servers: Connect to stable, well-maintained VPN servers. Verify ISP allows VPN: Check if your ISP blocks VPN connections. Keep Windows updated: Regular Windows updates include network component improvements. Use wired connection for VPN: Wired connections are more stable than Wi-Fi for VPN.
Additional Troubleshooting Steps
Check ISP Restrictions
Some ISPs block VPN connections or specific ports. Contact your ISP to verify if VPN connections are allowed. If ISP blocks VPN, you may need to use different VPN protocols or change ISPs.
Try Different VPN Protocols
If one VPN protocol fails, try another. For example, if PPTP fails with error 629, try L2TP/IPSec or OpenVPN. Different protocols use different ports and may not be blocked.
Check VPN Server Status
Verify that VPN server is online and accessible. Contact VPN provider to check server status. If server is down, wait for it to come back online or use alternative server.
Prevention Strategies
- Keep network drivers updated: Regularly update network adapter drivers
- Configure firewall correctly: Ensure firewall allows VPN and broadband connections
- Use reliable VPN servers: Connect to stable, well-maintained VPN servers
- Verify ISP allows VPN: Check if your ISP blocks VPN connections
- Keep Windows updated: Regular Windows updates include network component improvements
- Use wired connection for VPN: Wired connections are more stable than Wi-Fi
- Save VPN credentials securely: Use password manager to avoid authentication errors
When to Seek Professional Help
If all methods fail to resolve connection errors, consider these scenarios:
- ISP blocking VPN: If ISP blocks VPN connections, you may need to change ISPs or use different connection methods
- Corporate network restrictions: In business environments, consult IT support for VPN configuration
- Hardware issues: If network adapter hardware is failing, hardware replacement may be necessary
- Complex network setup: If you have complex network configuration, professional network setup may be needed
Frequently Asked Questions
Q: What's the difference between error 629, 631, 633, and 650?
A: Error 629 means connection was closed by remote computer (port blocked or server unavailable). Error 631 means user disconnected (connection terminated unexpectedly). Error 633 means port is already in use (another connection using the port). Error 650 means remote access server is not responding (server unavailable or unreachable).
Q: Can my ISP block VPN connections?
A: Yes, some ISPs block VPN connections or specific VPN ports. If your ISP blocks VPN, you may need to use different VPN protocols (like OpenVPN on port 443 which looks like HTTPS traffic), use VPN obfuscation, or change ISPs.
Q: Will resetting network components affect my internet connection?
A: Resetting network components may temporarily disconnect your internet connection, but it will reconnect automatically after restart. Your network settings will be reset to defaults, so you may need to reconfigure Wi-Fi passwords or network settings.
Q: Can I use VPN if my router blocks it?
A: If router blocks VPN, you can enable VPN passthrough in router settings, or connect VPN directly on your computer instead of through router. Some routers have VPN passthrough disabled by default - enable it in router admin panel.
Q: What VPN protocol should I use?
A: IKEv2 and OpenVPN are generally more reliable and secure than PPTP. L2TP/IPSec is also good. PPTP is older and less secure but may work when others fail. Check with your VPN provider for recommended protocol.