A broken or faulty internet connection can have various causes, such as incorrect IP address, subnet mask, gateway, DNS servers, or firewall settings. In this guide, we explain how you can independently identify and fix possible network problems.
The first step in troubleshooting is to ensure that the network adapter’s technical configuration on your server is correct – that means IP address, subnet mask, and gateway.
You can find these details in the Overview tab of your VPS management, where all IP addresses currently assigned to your service are displayed.
Now connect to your server via RDP or the console if you have issues. Open the Windows network adapter settings via:
Settings -> Network & Internet -> Change adapter options -> Network adapters
Find the option Internet Protocol Version 4 (TCP/IPv4) in the list and click Properties.
Compare the details in the adapter and make sure they are set as follows:
- IP Address: This should match the IP address you find in the Overview tab of your VPS management.
- Subnet Mask: Usually
255.255.255.0, as our network uses Class C. - Default Gateway: This is your IP address with the last octet (
.xxx) replaced by.1.
This is an example to make it easier for you. Replace the IP address with your server’s own IP.
For an IP address of 185.223.28.163, the configuration should look like this:
| Setting | Value |
|---|---|
| IP Address | 185.223.28.163 |
| Subnet Mask | 255.255.255.0 |
| Default Gateway | 185.223.28.1 |
If everything is correct, click Ok to apply the changes. We recommend restarting the server to complete the troubleshooting.
If you still experience internet connection problems, the next step is to check the DNS server configuration. Replace missing or incorrect DNS server entries with known, reliable hosts.
We recommend Google or Cloudflare DNS servers as they are widely used and stable.
| DNS Provider | DNS Server Addresses |
|---|---|
| Preferred: 8.8.8.8 / Alternate: 8.8.4.4 | |
| Cloudflare | Preferred: 1.1.1.1 / Alternate: 1.0.0.1 |
Then click Ok again to save the changes. We also recommend restarting the server to apply the settings.
You can open the command prompt (cmd.exe) on your server and run the following command to quickly and easily set the DNS servers:
powershell “Get-NetAdapter | Get-NetIPAddress | ForEach-Object { netsh interface ip set dns name=\"$($_.InterfaceAlias)\" static 8.8.8.8; netsh interface ip add dns name=\"$($_.InterfaceAlias)\" 1.1.1.1 index=2 }”
The last step in troubleshooting is to ensure that the Windows Firewall is configured correctly.
We recommend temporarily disabling the Windows Firewall to check if the problem disappears. Open Windows Search, type Windows Defender Firewall, and select the Turn Windows Defender Firewall on or off option on the left.
If the issue is resolved with the firewall disabled, the cause is likely an incorrect firewall configuration.
The solution depends heavily on the specific problem. For further help managing firewall rules, please use our Port Forwarding (Firewall) guide.
Preferred source on Google
