Results 1 to 6 of 6

Thread: "Cannot communicate with Primary DNS Server" in Wireless Network

  1. #1
    Join Date
    May 2009
    Posts
    3

    "Cannot communicate with Primary DNS Server" in Wireless Network

    Hello. I'm having some problems with my internet connection that I can't figure out. I've searched google, searched several forums and tried various things. Nothing seems to work.
    I'm using Windows Vista Home Premium on a desktop which is connected to a wireless network, using the standard wireless Linksys router.

    When I connect to my router (wirelessly), it does not connect to the internet and it's Access reads Local Only as opposed to "Local & Internet." I use the Diagnose and Repair option and it sends back a Network Diagnostics messages saying "Cannot communicate with Primary DNS Server (68.87.71.226)." The option it gives me to repair is to reset the network adapter "Wireless Network Connection" but when I click on that I get a message that comes back saying the same exact thing. This problem only persists on my desktop, the 3 other laptops in the house work fine. So, maybe a DNS changer trojan? I don't know. I have checked to see if my non-Windows firewall was blocking access and it wasn't. I have done TCP/IP stack repairs, unsuccessful. I have tried flushing my DNS cache, release the IP and renewing it, nothing. Here is some of my information, I appreciate any help.

    Using ipconfig/all the following is displayed:

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : Zexby-PC
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : hsd1.ct.comcast.net.

    Wireless LAN adapter Wireless Network Connection:

    Connection-specific DNS Suffix . : hsd1.ct.comcast.net.
    Description . . . . . . . . . . . : USB Wireless 802.11 b/g Adaptor
    Physical Address. . . . . . . . . : 00-16-44-6B-09-3A
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::94fd:b45b:87af:1ff%9(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.103(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : Sunday, May 10, 2009 1:48:19 PM
    Lease Expires . . . . . . . . . . : Monday, May 11, 2009 1:48:19 PM
    Default Gateway . . . . . . . . . : 192.168.1.1
    DHCP Server . . . . . . . . . . . : 192.168.1.1
    DHCPv6 IAID . . . . . . . . . . . : 151000644
    DNS Servers . . . . . . . . . . . : 68.87.71.226
    68.87.73.242
    68.87.64.146
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Local Area Connection:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
    Physical Address. . . . . . . . . : 00-1D-60-B5-DD-1C
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 6:

    Connection-specific DNS Suffix . : hsd1.ct.comcast.net.
    Description . . . . . . . . . . . : isatap.hsd1.ct.comcast.net.
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::5efe:192.168.1.103%13(Preferred)
    Default Gateway . . . . . . . . . :
    DNS Servers . . . . . . . . . . . : 68.87.71.226
    68.87.73.242
    68.87.64.146
    NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter Local Area Connection* 7:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : isatap.{E012AFC3-E32C-4B0A-BB2F-C9EB06053
    1DD}
    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 . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    Physical Address. . . . . . . . . : 02-00-54-55-4E-01
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes



    I have also included what appears when I try to pull up the NETBIOS (nbtstat -n), ping an internet website (www.live.com), my default gateway (192.168.1.1), my desktop's ip address(192.168.1.103) and my computer (zexby-pc).

    C:\Windows\system32>nbtstat -n

    Local Area Connection:
    Node IpAddress: [0.0.0.0] Scope Id: []

    No names in cache

    Wireless Network Connection:
    Node IpAddress: [192.168.1.103] Scope Id: []

    NetBIOS Local Name Table

    Name Type Status
    ---------------------------------------------
    ZEXBY-PC <00> UNIQUE Registered
    WORKGROUP <00> GROUP Registered
    ZEXBY-PC <20> UNIQUE Registered
    WORKGROUP <1E> GROUP Registered
    WORKGROUP <1D> UNIQUE Registered
    ..__MSBROWSE__.<01> GROUP Registered

    C:\Windows\system32>ping 192.168.1.1

    Pinging 192.168.1.1 with 32 bytes of data:

    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.

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

    C:\Windows\system32>ping 192.168.1.103

    Pinging 192.168.1.103 with 32 bytes of data:

    Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
    Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
    Reply from 192.168.1.103: bytes=32 time<1ms TTL=128
    Reply from 192.168.1.103: bytes=32 time<1ms TTL=128

    Ping statistics for 192.168.1.103:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

    C:\Windows\system32>ping www.live.com
    Ping request could not find host www.live.com. Please check the name and try aga
    in.

    C:\Windows\system32>ping zexby-pc

    Pinging Zexby-PC [fe80::94fd:b45b:87af:1ff%9] from fe80::94fd:b45b:87af:1ff%9 wi
    th 32 bytes of data:

    Reply from fe80::94fd:b45b:87af:1ff%9: time<1ms
    Reply from fe80::94fd:b45b:87af:1ff%9: time<1ms
    Reply from fe80::94fd:b45b:87af:1ff%9: time<1ms
    Reply from fe80::94fd:b45b:87af:1ff%9: time<1ms

    Ping statistics for fe80::94fd:b45b:87af:1ff%9:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms


    Any help here would be greatly appreciated. I thank you in advance for your response.
    Last edited by Yogesh; 11-05-2009 at 10:39 AM. Reason: Thread title edited. A thread with same previous title already existed.

  2. #2
    Join Date
    May 2008
    Posts
    991

    Re: Cannot communicate with Primary DNS Server

    I would say better you first get confirm from your ISP the correct DNS for your network. Because the DNS servers are controlled by ISP's and only he is the one who can help you to rectify the actual problem.

  3. #3
    Join Date
    Apr 2008
    Posts
    3,424

    Re: "Cannot communicate with Primary DNS Server" in Wireless Network

    Have you seen this thread? You solution is most probably in 1 of those...
    cannot communicate with primary dns server - Vista Suspend/Sleep/Standby issue

  4. #4
    Join Date
    May 2009
    Posts
    3

    Re: "Cannot communicate with Primary DNS Server" in Wireless Network

    @ Aleksandra

    I have contacted my ISP and they told me that since my computer is the only one experiencing this problem it's of none of their concern. Comcast sucks. They refreshed the connection to my home, no luck and they ran me through a set of instructions which I have already tried, again, no luck.


    @ Milton.J

    I have seen that thread, I have tried their 4 solutions, no luck. That is why I posted this thread. All previous threads that I have read, and I have searched them all, have left me unsuccessful.

  5. #5
    Join Date
    Nov 2005
    Posts
    2,327

    Re: "Cannot communicate with Primary DNS Server" in Wireless Network

    Hey!
    It seems that the problem lyes with your Wifi adapter. Try to use a different adapter and check if you get through... All the best!

  6. #6
    Join Date
    May 2009
    Posts
    3

    Re: "Cannot communicate with Primary DNS Server" in Wireless Network

    I don't currently have another adapter, which is why I am trying to correct the problem with this one.

Similar Threads

  1. Replies: 9
    Last Post: 27-11-2011, 10:08 PM
  2. Replies: 4
    Last Post: 06-02-2011, 08:15 AM
  3. Replies: 3
    Last Post: 20-01-2011, 07:51 PM
  4. Replies: 5
    Last Post: 15-01-2011, 07:01 PM
  5. Replies: 2
    Last Post: 03-06-2008, 03:16 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,529,940.26266 seconds with 17 queries