Fix Windows Server Internet Access When the Default Route Points to Itself

apiVersion: soultec.ch/v1kind: Postmetadata: name: how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself locale: en labels: author: valentina-cicmak series: how-to capability/automation: 1.78 capability/network: 2.16 annotations: source: blog-content/posts/en/how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself.md route: /en/insights/how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself/ schema: /nerd/schema/posts.json markdown: /en/insights/how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself.mdspec: title: >- Fix Windows Server Internet Access When the Default Route Points to Itself date: 2026-06-09 author: valentina-cicmak locale: en summary: >- A Windows Server can lose internet access even though the network settings look correct. capabilities: [automation, network] series: how-to hero: >- /blog-assets/how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself/hero.webp legacySlug: >- how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself migrated: 2026-08-24 draft: false sections: - body: | A Windows Server can lose internet access even though the network settings look correct. The IP address is set, the subnet mask is correct, DNS servers are configured, and the default gateway appears to point to the router. Local devices in the same network still respond to ping, but the server cannot reach the internet. In this situation, the problem is often not DNS. It is routing. ### Solution Windows needs a default route for all traffic outside the local subnet. To check this, open Command Prompt or PowerShell and run: ```powershell route print ``` In the output, look for the IPv4 Route Table and then for the Active Routes section. The default route is the line where both Network Destination and Netmask are 0.0.0.0. A correct default route usually looks like this: ```powershell 0.0.0.0 0.0.0.0 10.177.192.1 ``` Here, 10.177.192.1 is the router or firewall. That is where internet traffic needs to go. The problem appears when the routing table contains a route like this: ```powershell 0.0.0.0 0.0.0.0 On-link 10.177.192.5 ``` or when the server uses its own IP address as the gateway: ```powershell 0.0.0.0 0.0.0.0 10.177.192.5 ``` In this example, 10.177.192.5 is the server itself. That means Windows tries to send internet traffic to itself instead of sending it to the router. Local network communication still works, because local devices are directly reachable. Internet access fails because the traffic never reaches the real gateway. Then test the connection step by step: ```powershell ping 10.177.192.1 ping 8.8.8.8 nslookup google.com ``` If the gateway responds but 8.8.8.8 does not, the issue is most likely routing. If 8.8.8.8 works but google.com does not, the issue is most likely DNS. To remove the broken default route, use this template: ```powershell route delete 0.0.0.0 mask 0.0.0.0 ``` For example: ```powershell route delete 0.0.0.0 mask 0.0.0.0 10.177.192.5 ``` This removes the wrong route where the server points internet traffic to itself. After that, reset the adapter configuration cleanly. The following command is only a template. Replace the adapter name, IP address, subnet mask, gateway, and metric with the values from your own network: ```powershell netsh interface ipv4 set address name="" static ``` For example: ```powershell netsh interface ipv4 set address name="Ethernet0" static 10.177.192.5 255.255.255.0 10.177.192.1 1 ``` In this example, Ethernet0 is the network adapter, 10.177.192.5 is the server IP, 255.255.255.0 is the subnet mask, 10.177.192.1 is the real gateway, and 1 is the route metric. After running the command, check the routing table again: ```powershell route print ``` The default route should now point to the real gateway: ```powershell 0.0.0.0 0.0.0.0 10.177.192.1 ``` The reason this works better than changing the same values in the Windows network settings is that the graphical interface can show correct values while the routing table still contains an old or broken route. Software, virtual adapters, VPN clients, network drivers, or management tools can influence the routing table. The command line resets the adapter configuration more directly and forces Windows to recreate the route properly. The key lesson is simple: when a Windows Server can reach the local network but not the internet, do not only check IP, DNS, and gateway fields. Always check route print. If the default route points to the server itself, Windows sends the traffic in the wrong direction. - heading:

Next Steps

body: | If you've read this far then chances are you are still having issues. [Feel free to reach out to us](https://soultec.ch/contact-us/). We're happy to help out!status: corpus: 267 alsoLike: - {ref: posts/how-to-fix-fix-static-windows-network-settings-reset-after-reboot, score: 0.55} - {ref: posts/vmware-software-defined-wan, score: 0.53} - {ref: solutions/vmware, score: 0.53}

{ "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": { "name": "how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself", "locale": "en", "labels": { "author": "valentina-cicmak", "series": "how-to", "capability/automation": "1.78", "capability/network": "2.16" }, "annotations": { "source": "blog-content/posts/en/how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself.md", "route": "/en/insights/how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself/", "schema": "/nerd/schema/posts.json", "markdown": "/en/insights/how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself.md" } }, "spec": { "title": "Fix Windows Server Internet Access When the Default Route Points to Itself", "date": "2026-06-09", "author": "valentina-cicmak", "locale": "en", "summary": "A Windows Server can lose internet access even though the network settings look correct.", "capabilities": [ "automation", "network" ], "series": "how-to", "hero": "/blog-assets/how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself/hero.webp", "legacySlug": "how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself", "migrated": "2026-08-24", "draft": false }, "sections": [ { "body": "A Windows Server can lose internet access even though the network settings look correct. The IP address is set, the subnet mask is correct, DNS servers are configured, and the default gateway appears to point to the router. Local devices in the same network still respond to ping, but the server cannot reach the internet.\n\nIn this situation, the problem is often not DNS. It is routing.\n\n### Solution\n\nWindows needs a default route for all traffic outside the local subnet. To check this, open Command Prompt or PowerShell and run:\n\n```powershell\nroute print\n```\n\nIn the output, look for the IPv4 Route Table and then for the Active Routes section. The default route is the line where both Network Destination and Netmask are 0.0.0.0.\n\nA correct default route usually looks like this:\n\n```powershell\n0.0.0.0 0.0.0.0 10.177.192.1\n```\n\nHere, 10.177.192.1 is the router or firewall. That is where internet traffic needs to go.\n\nThe problem appears when the routing table contains a route like this:\n\n```powershell\n0.0.0.0 0.0.0.0 On-link 10.177.192.5\n```\n\nor when the server uses its own IP address as the gateway:\n\n```powershell\n0.0.0.0 0.0.0.0 10.177.192.5\n```\n\nIn this example, 10.177.192.5 is the server itself. That means Windows tries to send internet traffic to itself instead of sending it to the router. Local network communication still works, because local devices are directly reachable. Internet access fails because the traffic never reaches the real gateway.\n\nThen test the connection step by step:\n\n```powershell\nping 10.177.192.1\nping 8.8.8.8\nnslookup google.com\n```\n\nIf the gateway responds but 8.8.8.8 does not, the issue is most likely routing. If 8.8.8.8 works but google.com does not, the issue is most likely DNS.\n\nTo remove the broken default route, use this template:\n\n```powershell\nroute delete 0.0.0.0 mask 0.0.0.0\n```\n\nFor example:\n\n```powershell\nroute delete 0.0.0.0 mask 0.0.0.0 10.177.192.5\n```\n\nThis removes the wrong route where the server points internet traffic to itself.\n\nAfter that, reset the adapter configuration cleanly. The following command is only a template. Replace the adapter name, IP address, subnet mask, gateway, and metric with the values from your own network:\n\n```powershell\nnetsh interface ipv4 set address name=\"\" static\n```\n\nFor example:\n\n```powershell\nnetsh interface ipv4 set address name=\"Ethernet0\" static 10.177.192.5 255.255.255.0 10.177.192.1 1\n```\n\nIn this example, Ethernet0 is the network adapter, 10.177.192.5 is the server IP, 255.255.255.0 is the subnet mask, 10.177.192.1 is the real gateway, and 1 is the route metric.\n\nAfter running the command, check the routing table again:\n\n```powershell\nroute print\n```\n\nThe default route should now point to the real gateway:\n\n```powershell\n0.0.0.0 0.0.0.0 10.177.192.1\n```\n\nThe reason this works better than changing the same values in the Windows network settings is that the graphical interface can show correct values while the routing table still contains an old or broken route. Software, virtual adapters, VPN clients, network drivers, or management tools can influence the routing table. The command line resets the adapter configuration more directly and forces Windows to recreate the route properly.\n\nThe key lesson is simple: when a Windows Server can reach the local network but not the internet, do not only check IP, DNS, and gateway fields. Always check route print. If the default route points to the server itself, Windows sends the traffic in the wrong direction." }, { "heading": "

Next Steps

", "body": "If you've read this far then chances are you are still having issues. [Feel free to reach out to us](https://soultec.ch/contact-us/). We're happy to help out!" } ], "status": { "corpus": 267, "alsoLike": [ { "ref": "posts/how-to-fix-fix-static-windows-network-settings-reset-after-reboot", "score": "0.55" }, { "ref": "posts/vmware-software-defined-wan", "score": "0.53" }, { "ref": "solutions/vmware", "score": "0.53" } ] }}

apiVersion = "soultec.ch/v1"kind = "Post"[metadata]name = "how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself"locale = "en"[metadata.labels]author = "valentina-cicmak"series = "how-to""capability/automation" = "1.78""capability/network" = "2.16"[metadata.annotations]source = "blog-content/posts/en/how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself.md"route = "/en/insights/how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself/"schema = "/nerd/schema/posts.json"markdown = "/en/insights/how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself.md"[spec]title = "Fix Windows Server Internet Access When the Default Route Points to Itself"date = 2026-06-09author = "valentina-cicmak"locale = "en"summary = "A Windows Server can lose internet access even though the network settings look correct."capabilities = ["automation", "network"]series = "how-to"hero = "/blog-assets/how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself/hero.webp"legacySlug = "how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself"migrated = 2026-08-24draft = false[[sections]]body = '''A Windows Server can lose internet access even though the network settings look correct. The IP address is set, the subnet mask is correct, DNS servers are configured, and the default gateway appears to point to the router. Local devices in the same network still respond to ping, but the server cannot reach the internet.In this situation, the problem is often not DNS. It is routing.### SolutionWindows needs a default route for all traffic outside the local subnet. To check this, open Command Prompt or PowerShell and run:```powershellroute print```In the output, look for the IPv4 Route Table and then for the Active Routes section. The default route is the line where both Network Destination and Netmask are 0.0.0.0.A correct default route usually looks like this:```powershell0.0.0.0 0.0.0.0 10.177.192.1```Here, 10.177.192.1 is the router or firewall. That is where internet traffic needs to go.The problem appears when the routing table contains a route like this:```powershell0.0.0.0 0.0.0.0 On-link 10.177.192.5```or when the server uses its own IP address as the gateway:```powershell0.0.0.0 0.0.0.0 10.177.192.5```In this example, 10.177.192.5 is the server itself. That means Windows tries to send internet traffic to itself instead of sending it to the router. Local network communication still works, because local devices are directly reachable. Internet access fails because the traffic never reaches the real gateway.Then test the connection step by step:```powershellping 10.177.192.1ping 8.8.8.8nslookup google.com```If the gateway responds but 8.8.8.8 does not, the issue is most likely routing. If 8.8.8.8 works but google.com does not, the issue is most likely DNS.To remove the broken default route, use this template:```powershellroute delete 0.0.0.0 mask 0.0.0.0```For example:```powershellroute delete 0.0.0.0 mask 0.0.0.0 10.177.192.5```This removes the wrong route where the server points internet traffic to itself.After that, reset the adapter configuration cleanly. The following command is only a template. Replace the adapter name, IP address, subnet mask, gateway, and metric with the values from your own network:```powershellnetsh interface ipv4 set address name="" static```For example:```powershellnetsh interface ipv4 set address name="Ethernet0" static 10.177.192.5 255.255.255.0 10.177.192.1 1```In this example, Ethernet0 is the network adapter, 10.177.192.5 is the server IP, 255.255.255.0 is the subnet mask, 10.177.192.1 is the real gateway, and 1 is the route metric.After running the command, check the routing table again:```powershellroute print```The default route should now point to the real gateway:```powershell0.0.0.0 0.0.0.0 10.177.192.1```The reason this works better than changing the same values in the Windows network settings is that the graphical interface can show correct values while the routing table still contains an old or broken route. Software, virtual adapters, VPN clients, network drivers, or management tools can influence the routing table. The command line resets the adapter configuration more directly and forces Windows to recreate the route properly.The key lesson is simple: when a Windows Server can reach the local network but not the internet, do not only check IP, DNS, and gateway fields. Always check route print. If the default route points to the server itself, Windows sends the traffic in the wrong direction.'''[[sections]]heading = "

Next Steps

"body = "If you've read this far then chances are you are still having issues. [Feel free to reach out to us](https://soultec.ch/contact-us/). We're happy to help out!"[status]corpus = 267[[status.alsoLike]]ref = "posts/how-to-fix-fix-static-windows-network-settings-reset-after-reboot"score = "0.55"[[status.alsoLike]]ref = "posts/vmware-software-defined-wan"score = "0.53"[[status.alsoLike]]ref = "solutions/vmware"score = "0.53"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Post"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself</name> <locale>en</locale> <labels> <author>valentina-cicmak</author> <series>how-to</series> <entry key="capability/automation">1.78</entry> <entry key="capability/network">2.16</entry> </labels> <annotations> <source>blog-content/posts/en/how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself.md</source> <route>/en/insights/how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself/</route> <schema>/nerd/schema/posts.json</schema> <markdown>/en/insights/how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself.md</markdown> </annotations> </metadata> <spec> <title>Fix Windows Server Internet Access When the Default Route Points to Itself</title> <date>2026-06-09</date> <author>valentina-cicmak</author> <locale>en</locale> <summary>A Windows Server can lose internet access even though the network settings look correct.</summary> <capabilities> <item>automation</item> <item>network</item> </capabilities> <series>how-to</series> <hero>/blog-assets/how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself/hero.webp</hero> <legacySlug>how-to-fix-windows-server-internet-access-when-the-default-route-points-to-tself</legacySlug> <migrated>2026-08-24</migrated> <draft>false</draft> </spec> <sections> <section> <body>A Windows Server can lose internet access even though the network settings look correct. The IP address is set, the subnet mask is correct, DNS servers are configured, and the default gateway appears to point to the router. Local devices in the same network still respond to ping, but the server cannot reach the internet.In this situation, the problem is often not DNS. It is routing.### SolutionWindows needs a default route for all traffic outside the local subnet. To check this, open Command Prompt or PowerShell and run:```powershellroute print```In the output, look for the IPv4 Route Table and then for the Active Routes section. The default route is the line where both Network Destination and Netmask are 0.0.0.0.A correct default route usually looks like this:```powershell0.0.0.0 0.0.0.0 10.177.192.1```Here, 10.177.192.1 is the router or firewall. That is where internet traffic needs to go.The problem appears when the routing table contains a route like this:```powershell0.0.0.0 0.0.0.0 On-link 10.177.192.5```or when the server uses its own IP address as the gateway:```powershell0.0.0.0 0.0.0.0 10.177.192.5```In this example, 10.177.192.5 is the server itself. That means Windows tries to send internet traffic to itself instead of sending it to the router. Local network communication still works, because local devices are directly reachable. Internet access fails because the traffic never reaches the real gateway.Then test the connection step by step:```powershellping 10.177.192.1ping 8.8.8.8nslookup google.com```If the gateway responds but 8.8.8.8 does not, the issue is most likely routing. If 8.8.8.8 works but google.com does not, the issue is most likely DNS.To remove the broken default route, use this template:```powershellroute delete 0.0.0.0 mask 0.0.0.0```For example:```powershellroute delete 0.0.0.0 mask 0.0.0.0 10.177.192.5```This removes the wrong route where the server points internet traffic to itself.After that, reset the adapter configuration cleanly. The following command is only a template. Replace the adapter name, IP address, subnet mask, gateway, and metric with the values from your own network:```powershellnetsh interface ipv4 set address name="" static```For example:```powershellnetsh interface ipv4 set address name="Ethernet0" static 10.177.192.5 255.255.255.0 10.177.192.1 1```In this example, Ethernet0 is the network adapter, 10.177.192.5 is the server IP, 255.255.255.0 is the subnet mask, 10.177.192.1 is the real gateway, and 1 is the route metric.After running the command, check the routing table again:```powershellroute print```The default route should now point to the real gateway:```powershell0.0.0.0 0.0.0.0 10.177.192.1```The reason this works better than changing the same values in the Windows network settings is that the graphical interface can show correct values while the routing table still contains an old or broken route. Software, virtual adapters, VPN clients, network drivers, or management tools can influence the routing table. The command line resets the adapter configuration more directly and forces Windows to recreate the route properly.The key lesson is simple: when a Windows Server can reach the local network but not the internet, do not only check IP, DNS, and gateway fields. Always check route print. If the default route points to the server itself, Windows sends the traffic in the wrong direction. </body> </section> <section> <heading>

Next Steps

</heading> <body>If you've read this far then chances are you are still having issues. [Feel free to reach out to us](https://soultec.ch/contact-us/). We're happy to help out!</body> </section> </sections> <status> <corpus>267</corpus> <alsoLike> <item> <ref>posts/how-to-fix-fix-static-windows-network-settings-reset-after-reboot</ref> <score>0.55</score> </item> <item> <ref>posts/vmware-software-defined-wan</ref> <score>0.53</score> </item> <item> <ref>solutions/vmware</ref> <score>0.53</score> </item> </alsoLike> </status></manifest>

Next Steps

Next Steps

Next Steps

Next Steps

Fix Windows Server Internet Access When the Default Route Points to Itself

Solution

Next Steps

You might also like

Fix Static Windows Network Settings Reset After Reboot

Software-Defined WAN

VMware