Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

HTTP-specific network issue?

  • Keine Antworten
  • 1 hat dieses Problem
  • 9 Aufrufe
jjharr
jjharr
more options

This is probably a network problem, but it only appears to manifest in http. The problem manifests itself thusly :

1) If I type in the URL of a website (e.g. http://www.google.com) in the browser, I am redirected to a server on my internal network. 2) If I open a command prompt and ping the domain, it pings fine. 3) If I type the IP address of the pinged domain into the browser URL bar, it opens up the page just fine. 4) Finally, if I use an IP address to load a site I can sometimes, but not always, click on links and get pages to load properly. But if I manually enter in the top level domain for that site, I get redirected internally again. When the load fails, it appears that it tried to load a relative domain name.

Any pointers?

This is probably a network problem, but it only appears to manifest in http. The problem manifests itself thusly : 1) If I type in the URL of a website (e.g. http://www.google.com) in the browser, I am redirected to a server on my internal network. 2) If I open a command prompt and ping the domain, it pings fine. 3) If I type the IP address of the pinged domain into the browser URL bar, it opens up the page just fine. 4) Finally, if I use an IP address to load a site I can sometimes, but not always, click on links and get pages to load properly. But if I manually enter in the top level domain for that site, I get redirected internally again. When the load fails, it appears that it tried to load a relative domain name. Any pointers?