Internet: parts of the internet not connectable

Page 2 of 2 FirstFirst 12

  1. Posts : 8,870
    Windows 7 Ult, Windows 8.1 Pro,
       #11

    wpte said:
    chev65 said:
    If you can post your ipconfig /all it may show problems which can help to solve this connection issue.
    Sure, I masked some parts for privacy:)
    Or some parts should be really vital, but it looks to me like a common output.
    I hope the dutch is not a big issue, since the layout is the same on every windows.

    Code:
    Windows IP-configuratie
     
       Hostnaam  . . . . . . . . . . . . : Home-PC
       Primair DNS-achtervoegsel . . . . :
       Knooppunttype . . . . . . . . . . : hybride
       IP-routering ingeschakeld . . . . : nee
       WINS-proxy ingeschakeld . . . . . : nee
       DNS-achtervoegselzoeklijst. . . . : my.home.network
     
    Ethernet-adapter voor Local Area Connection 4:
     
       Mediumstatus. . . . . . . . . . . : medium ontkoppeld (disconnected)
       Verbindingsspec. DNS-achtervoegsel:
       Beschrijving. . . . . . . . . . . : TAP-Win32 Adapter V9
       Fysiek adres. . . . . . . . . . . : 00-FF-EF-73-43-6F
       DHCP ingeschakeld . . . . . . . . : ja
       Autom. configuratie ingeschakeld  : ja
     
    Ethernet-adapter voor Local Area Connection:
     
       Verbindingsspec. DNS-achtervoegsel: my.home.network
       Beschrijving. . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet
       Fysiek adres. . . . . . . . . . . : ************
       DHCP ingeschakeld . . . . . . . . : ja
       Autom. configuratie ingeschakeld  : ja
       IPv6-adres. . . . . . . . . . . . : 2001:**********(voorkeur)
       Tijdelijk IPv6-adres. . . . . . . : 2001:**********(voorkeur)
       Link-local IPv6-adres . . . . . . : fe80::**********(voorkeur)
       IPv4-adres. . . . . . . . . . . . : 192.168.2.12(voorkeur)
       Subnetmasker. . . . . . . . . . . : 255.255.255.0
       Lease verkregen . . . . . . . . . : maandag 24 januari 2011 23:34:03
       Lease verlopen. . . . . . . . . . : woensdag 26 januari 2011 0:07:18
       Standaardgateway. . . . . . . . . : fe80::**************
                                           192.168.2.1
       DHCP-server . . . . . . . . . . . : 192.168.2.1
       DNS-servers . . . . . . . . . . . : 192.168.2.1
                                           192.168.2.1
       Primaire WINS-server. . . . . . . : 192.168.2.1
       NetBIOS via TCPIP . . . . . . . . : ingeschakeld
     
    Tunnel-adapter voor isatap.my.home.network:
     
       Verbindingsspec. DNS-achtervoegsel: my.home.network
       Beschrijving. . . . . . . . . . . : Microsoft ISATAP Adapter
       Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP ingeschakeld . . . . . . . . : nee
       Autom. configuratie ingeschakeld  : ja
       Link-local IPv6-adres . . . . . . : fe80::*************(voorkeur)
       Standaardgateway. . . . . . . . . :
       DNS-servers . . . . . . . . . . . : 192.168.2.1
                                           192.168.2.1
       NetBIOS via TCPIP . . . . . . . . : uitgeschakeld
     
    Tunnel-adapter voor Local Area Connection* 11:
     
       Verbindingsspec. DNS-achtervoegsel:
       Beschrijving. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP ingeschakeld . . . . . . . . : nee
       Autom. configuratie ingeschakeld  : ja
       IPv6-adres. . . . . . . . . . . . : 2001**********(voorkeur)
       Link-local IPv6-adres . . . . . . : fe80::*********(voorkeur)
       Standaardgateway. . . . . . . . . :
       NetBIOS via TCPIP . . . . . . . . : uitgeschakeld
     
    Tunnel-adapter voor isatap.{****************}:
     
       Mediumstatus. . . . . . . . . . . : medium ontkoppeld
       Verbindingsspec. DNS-achtervoegsel:
       Beschrijving. . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP ingeschakeld . . . . . . . . : nee
       Autom. configuratie ingeschakeld  : ja
     
    Tunnel-adapter voor isatap.{****************}:
     
       Mediumstatus. . . . . . . . . . . : medium ontkoppeld (disconnected)
       Verbindingsspec. DNS-achtervoegsel:
       Beschrijving. . . . . . . . . . . : Microsoft ISATAP Adapter #3
       Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP ingeschakeld . . . . . . . . : nee
       Autom. configuratie ingeschakeld  : ja
    and yes, ipv6 is working fine.
    if I disable ipv6 no change regarding the ea.com problem.

    How many of those tunnel adaptors are showing up on the rest of your ipconfig?
      My Computer


  2. Posts : 13
    Windows 7 x64 ultimate
    Thread Starter
       #12

    chev65 said:
    How many of those tunnel adaptors are showing up on the rest of your ipconfig?
    this is the complete output, there isn't more

    I got my TAP adapter for openvpn, for connectiong to my servers.
    2 tunnel adaptors for isatap, 1 being disconnected and the other one connected to my local dhcp server:)
    And a teredo adaptor
      My Computer


  3. Posts : 13
    Windows 7 x64 ultimate
    Thread Starter
       #13

    I looked at tcpview at what's going on
    When I try to visit the customersupport site the connection doesn't pass "SYN_SENT"
      My Computer


  4. Posts : 8,870
    Windows 7 Ult, Windows 8.1 Pro,
       #14

    wpte said:
    I looked at tcpview at what's going on
    When I try to visit the customersupport site the connection doesn't pass "SYN_SENT"
    Have you tried resetting winsock? I didn't see that on your list.

    netsh winsock reset catalog (reset winsock entries)

    Other than that it might be a DNS problem or something.
      My Computer


  5. Posts : 13
    Windows 7 x64 ultimate
    Thread Starter
       #15

    chev65 said:
    wpte said:
    I looked at tcpview at what's going on
    When I try to visit the customersupport site the connection doesn't pass "SYN_SENT"
    Have you tried resetting winsock? I didn't see that on your list.

    netsh winsock reset catalog (reset winsock entries)

    Other than that it might be a DNS problem or something.
    Just tried that, rebooted windows still no change

    But when it would be a DNS problem, could I resolve and ping the domain name?
    The thing is, chrome also is able to resolve the ip, the correct one.
    Also I noticed ping doesn't show up in tcpview from sysinternals, is this because it's programmed on a lower level?

    Anyway, when trying squid, a proxy installed on my router it does work.
    Also I checked the cache at openDNS and everything matches.
    I don't use my ISP dns because it sometimes responds after half a minute
    All other computers connected to the same router work fine, including the problem maker when it's booted into linux.

    So I dunno, but this doesn't seem like a DNS problem
      My Computer


  6. Posts : 13
    Windows 7 x64 ultimate
    Thread Starter
       #16

    Well guess what...
    I tried connecting today, without doing ANYTHING about networking after all these attempts to fix it.
    And it worked!
    it simply worked!
    I'm confused right now, how suddenly things do work, but I'm glad it does
    thanks for the help you guys.
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:45.
Find Us