I've tried everything and still cant connect to the net!

I just got a new desktop the other day, and it can't connect to my home WiFi. Every other device in my house can connect with no problems, and the desktop can connect to my neighbors internet and use it with no problems. When the troubleshooter is used, it cites various DNS problems as the cause. Is this fixable? How do I fix it? I have already reset and power cycled my modem several times, to no avail. Changing to OpenDNS and back does nothing, and on DNS Jumper, all DNS hosts are said to be offline. What the hell is going on?
10 answers Last reply
More about connect
  1. Try using a cable, and plugging directly into your router.
  2. My desktop isn't close enough to the router to be plugged in with a cable (pc is in the basement, about 6 feet below the router - my neighbors is far more than that, and I have no problems connecting to it. Could being directly under it be the problem?
  3. My ipconfig /all:

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : ConnorLake-HP
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : home

    Wireless LAN adapter Wireless Network Connection 2:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Ada
    Physical Address. . . . . . . . . : 44-6D-57-73-57-24
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes

    Ethernet adapter Bluetooth Network Connection:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Bluetooth Device (Personal Area Net
    Physical Address. . . . . . . . . : 9C-B7-0D-9C-C6-60
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes

    Ethernet adapter Local Area Connection:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Atheros AR8161/8165 PCI-E Gigabit E
    t Controller (NDIS 6.20)
    Physical Address. . . . . . . . . : 78-E3-B5-AE-D5-57
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes

    Wireless LAN adapter Wireless Network Connection:

    Connection-specific DNS Suffix . : home
    Description . . . . . . . . . . . : Broadcom WLAN Adapter
    Physical Address. . . . . . . . . : 44-6D-57-73-57-24
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::8886:f386:cfd1:8728%13(Prefer
    IPv4 Address. . . . . . . . . . . : 192.168.2.34(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : September-30-12 9:31:26 PM
    Lease Expires . . . . . . . . . . : October-03-12 9:31:26 PM
    Default Gateway . . . . . . . . . : 192.168.2.1
    DHCP Server . . . . . . . . . . . : 192.168.2.1
    DHCPv6 IAID . . . . . . . . . . . : 222588247
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-6D-21-81-44-6D-57-73

    DNS Servers . . . . . . . . . . . : 192.168.2.1
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.home:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . : home
    Description . . . . . . . . . . . : Microsoft ISATAP Adapter
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 9:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft 6to4 Adapter
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 12:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
  4. So your computer has an IP address, try pinging 4.2.2.4 and post the result.

    Also, post the result of this command: tracert 4.2.2.4
  5. C:\Users\Connor Lake>ping 4.2.2.4

    Pinging 4.2.2.4 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.

    Ping statistics for 4.2.2.4:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    C:\Users\Connor Lake>ping 4.2.2.4

    Pinging 4.2.2.4 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.

    Ping statistics for 4.2.2.4:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


    C:\Users\Connor Lake>tracert 4.2.2.4

    Tracing route to 4.2.2.4 over a maximum of 30 hops

    1 * * * Request timed out.
    2 * * * Request timed out.
    3 * * * Request timed out.
    4 * * * Request timed out.
    5 * * * Request timed out.

    (all the rest are the same)

    currently windows diagnostics says that the DNS server isn't responding.
  6. Are you running any kind of anti-virus on this machine?

    Also, I'm wondering if the reason you cannot connect is because your PC is defaulting to your router for DNS. Go to your network settings and change your DNS to 4.2.2.3 and 4.2.2.4.

    Go to the command prompt and type: netsh interface ip set dns "Wireless Network Connection" static 4.2.2.4

    Let me know what happens.
  7. Try walking before running. If traffic isn't passing the gateway there's no way that pinging anything beyond it will respond.

    What is the result when you ping the gateway (192.168.2.1)?

    If it's successful then we know that there has been a successful negotiation between the access point and the adapter.

    I have seen cases where there was a successfully negotiated connection to the router but traffic would not pass through the gateway. In all those cases it turned out to be an incompatibility between the adapter and router (usually dlink adapter to netgear router) when WPA encryption was in use. Dropping to WEP cured the problem.
  8. moving the pc to another room fixes the problem...
    pinging the gateway does nothing in that room.
  9. DarthLakey said:
    moving the pc to another room fixes the problem...
    pinging the gateway does nothing in that room.



    OK, signal problem. PC's antenna was sitting in a dead (or mostly dead) zone.

    By "does nothing" I assume you mean timed out.
  10. yes.
Ask a new question

Read More

Connection Desktops DNS Networking