Groups | Search | Server Info | Login | Register

Groups > comp.os.ms-windows.networking.misc > #98

Can't connect to Web

From Steve Hayes <hayesstw@telkomsa.net>
Newsgroups microsoft.public.windowsxp.general, alt.comp.os.windows-xp, comp.os.ms-windows.networking.misc
Subject Can't connect to Web
Date 2017-05-26 10:04 +0200
Organization Khanya Publications
Message-ID <m0ofic9sm6v97v17qncgjp45q6tdvg6scv@4ax.com> (permalink)

Cross-posted to 3 groups.

Show all headers | View raw

This morning I suddenly lost my connection to the web while I was
browsing. 

Mail still worked, news still worked, but the web connection did not. 

I reset the router, rebooted my computer, but still nothing. 

I wondered if it was a browser fault (I use Firefox) so tried Internet
Explorer. It too could not connect, but offered to run diagnostics.
This is what was found:

---- diagnostic report ----
Last diagnostic run time: 05/26/17 09:44:37 HTTP, HTTPS, FTP
Diagnostic 
HTTP, HTTPS, FTP connectivity 

info HTTP: Successfully connected to www.microsoft.com. 
warn HTTPS: Error 12157 connecting to www.microsoft.com: An error
occurred in the secure channel support  
warn FTP (Passive): Error 12031 connecting to ftp.microsoft.com: The
connection with the server was reset  
warn HTTPS: Error 12029 connecting to www.passport.net: A connection
with the server could not be established  
warn FTP (Active): Error 12031 connecting to ftp.microsoft.com: The
connection with the server was reset  
error Could not make an HTTPS connection. 
error Could not make an FTP connection. 
info Redirecting user to support call 
 


DNS Client Diagnostic 
DNS - Not a home user scenario 

info Using Web Proxy: no 
info Resolving name ok for (www.microsoft.com): yes 
No DNS servers 

DNS failure 

 


Gateway Diagnostic 
Gateway 

info The following proxy configuration is being used by IE:
Automatically Detect Settings:Disabled Automatic Configuration Script:
Proxy Server: Proxy Bypass list:  
info This computer has the following default gateway entry(ies):
192.168.0.1 
info This computer has the following IP address(es): 192.168.0.2 
info The default gateway is in the same subnet as this computer 
info The default gateway entry is a valid unicast address 
info The default gateway address was resolved via ARP in 1 try(ies) 
info The default gateway was reached via ICMP Ping in 1 try(ies) 
info TCP port 80 on host 104.92.152.182 was successfully reached 
info The Internet host www.microsoft.com was successfully reached 
info The default gateway is OK 
 


IP Layer Diagnostic 
Corrupted IP routing table 

info The default route is valid 
info The loopback route is valid 
info The local host route is valid 
info The local subnet route is valid 
Invalid ARP cache entries 

action The ARP cache has been flushed 
 


IP Configuration Diagnostic 
Invalid IP address 

info Valid IP address detected: 192.168.0.2 
 


Wireless Diagnostic 
Wireless - Service disabled 

Wireless - User SSID 

Wireless - First time setup 

Wireless - Radio off 

Wireless - Out of range 

Wireless - Hardware issue 

Wireless - Novice user 

Wireless - Ad-hoc network 

Wireless - Less preferred 

Wireless - 802.1x enabled 

Wireless - Configuration mismatch 

Wireless - Low SNR 

 


WinSock Diagnostic 
WinSock status 

info IrDA protocol is not found in Winsock catalog. 
info All base service provider entries are present in the Winsock
catalog. 
info The Winsock Service provider chains are valid. 
info Provider entry MSAFD Tcpip [TCP/IP] passed the loopback
communication test. 
info Provider entry MSAFD Tcpip [UDP/IP] passed the loopback
communication test. 
info Provider entry RSVP UDP Service Provider passed the loopback
communication test. 
info Provider entry RSVP TCP Service Provider passed the loopback
communication test. 
info Connectivity is valid for all Winsock service providers. 
 


Network Adapter Diagnostic 
Network location detection 

info Using home Internet connection 
Network adapter identification 

info Network connection: Name=Local Area Connection 2, Device=Realtek
PCIe FE Family Controller, MediaType=LAN, SubMediaType=LAN 
info Network connection: Name=MSN, Device=, MediaType=PHONE,
SubMediaType=NONE 
info Network connection: Name=telkomsa9, Device=WAN Miniport (PPPOE),
MediaType=PPPOE, SubMediaType=NONE 
info Ethernet connection selected 
Network adapter status 

info Network connection status: Connected 
 


HTTP, HTTPS, FTP Diagnostic 
HTTP, HTTPS, FTP connectivity 

warn FTP (Passive): Error 12031 connecting to ftp.microsoft.com: The
connection with the server was reset  
info HTTP: Successfully connected to www.microsoft.com. 
warn HTTPS: Error 12157 connecting to www.microsoft.com: An error
occurred in the secure channel support  
warn HTTPS: Error 12029 connecting to www.passport.net: A connection
with the server could not be established  
warn FTP (Active): Error 12031 connecting to ftp.microsoft.com: The
connection with the server was reset  
error Could not make an HTTPS connection. 
error Could not make an FTP connection. 
 
--- end diagnostic report ---


Can any of you network gurus suggest what can be done to fix it?


-- 
Steve Hayes
http://www.khanya.org.za/stevesig.htm
http://khanya.wordpress.com

Back to comp.os.ms-windows.networking.misc | Previous | Next — Next in thread | Find similar

Thread

Can't connect to Web Steve Hayes <hayesstw@telkomsa.net> - 2017-05-26 10:04 +0200
  Re: Can't connect to Web rickman <gnuarm@gmail.com> - 2017-05-26 04:47 -0400
    Re: Can't connect to Web Steve Hayes <hayesstw@telkomsa.net> - 2017-05-28 06:21 +0200
      Re: Can't connect to Web VanguardLH <V@nguard.LH> - 2017-05-27 23:33 -0500
      Re: Can't connect to Web rickman <gnuarm@gmail.com> - 2017-05-28 01:24 -0400
        Re: Can't connect to Web Paul <nospam@needed.invalid> - 2017-05-28 02:17 -0400
          Re: Can't connect to Web rickman <gnuarm@gmail.com> - 2017-05-28 03:18 -0400
            Re: Can't connect to Web VanguardLH <V@nguard.LH> - 2017-05-28 05:31 -0500
  Re: Can't connect to Web VanguardLH <V@nguard.LH> - 2017-05-26 13:39 -0500
  Re: Can't connect to Web Stef <not@this.address.com> - 2017-05-28 17:16 +0000
    Re: Can't connect to Web Bert <bert@iphouse.com> - 2017-05-28 17:48 +0000
      Re: Can't connect to Web Stef <not@this.address.com> - 2017-05-29 19:05 +0000
        Re: Can't connect to Web Bert <bert@iphouse.com> - 2017-05-31 17:51 +0000
          Re: Can't connect to Web Stef <not@this.address.com> - 2017-05-31 23:03 +0000
          Re: Can't connect to Web Char Jackson <none@none.invalid> - 2017-06-13 15:10 -0500
    Re: Can't connect to Web VanguardLH <V@nguard.LH> - 2017-05-28 15:11 -0500
      Re: Can't connect to Web rickman <gnuarm@gmail.com> - 2017-05-29 00:20 -0400
      Re: Can't connect to Web Stef <not@this.address.com> - 2017-05-29 18:57 +0000
    Re: Can't connect to Web Steve Hayes <hayesstw@telkomsa.net> - 2017-05-29 03:53 +0200
      Re: Can't connect to Web Stef <not@this.address.com> - 2017-05-29 16:27 +0000
      Re: Can't connect to Web VanguardLH <V@nguard.LH> - 2017-05-31 15:41 -0500
        Re: Can't connect to Web Steve Hayes <hayesstw@telkomsa.net> - 2017-06-01 08:52 +0200
          Re: Can't connect to Web Rene Lamontagne <rlamont@shaw.ca> - 2017-06-20 20:50 -0500

csiph-web