Advertisement

There's no such thing as a stupid question, but they're the easiest to answer.
Login
Search

Advertisement

Networking Networking
Search Search
Search for:
Tech Support Guy > > >

Solved: "Cannot communicate with Primary DNS Server(192.168.2.1)."


(!)

Charles123138's Avatar
Charles123138 Charles123138 is offline
Junior Member with 3 posts.
THREAD STARTER
 
Join Date: Jun 2010
Experience: Intermediate
12-Jun-2010, 12:05 PM #1
Exclamation Solved: "Cannot communicate with Primary DNS Server(192.168.2.1)."
When I turned on my desktop computer this morning, my internet stopped working. Upon further investigation, I realized that I couldn't even access http://192.168.2.1/ like I normally could before. My computer is connected by cable and it says that it is connected to a network. I hadn't changed anything recently on my computer and it's been working fine for a couple years (except last morning, the internet stopped for a couple minutes). I went on the laptop (which I'm on now, wireless) and Iv'e been restarting my desktop, restarting the modem, resetting the router to factory defaults, and restarting the router (from http://192.168.2.1/) at least 20 times. After reading around some more, I tried resetting WINSOCK entries, IPv4 TCP/IP, and IPv6 TCP/IP.

Modem Model: Motorola SB5120
Router Model: Belkin F5D9230-4
Desktop OS: Vista
I my desktop set to obtain IP adress and DNS server address automatically.

Quote:
Originally Posted by Command Prompt
Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Charles-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Belkin

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : Belkin
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-1D-60-B5-BA-23
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::3578:f726:5f0e:d25e%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.2.4(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Saturday, June 12, 2010 11:33:12 AM
Lease Expires . . . . . . . . . . : Sunday, June 12, 2011 11:33:12 AM
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DHCPv6 IAID . . . . . . . . . . . : 201333756
DNS Servers . . . . . . . . . . . : 192.168.2.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

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

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . : Belkin
Description . . . . . . . . . . . : isatap.Belkin
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.2.4%11(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.2.1
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Windows\system32>ping 192.168.2.4

Pinging 192.168.2.4 with 32 bytes of data:

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

Ping statistics for 192.168.2.4:
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 192.168.2.1

Pinging 192.168.2.1 with 32 bytes of data:

General failure.
General failure.
General failure.
General failure.

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

C:\Windows\system32>ping 206.190.60.37

Pinging 206.190.60.37 with 32 bytes of data:

General failure.
General failure.
General failure.
General failure.

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

C:\Windows\system32>ping yahoo.com
Ping request could not find host yahoo.com. Please check the name and try again.


C:\Windows\system32>ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:

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

Ping statistics for 127.0.0.1:
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>

Last edited by Charles123138; 12-Jun-2010 at 12:15 PM.. Reason: More details
TerryNet's Avatar
Computer Specs
Moderator with 65,258 posts.
 
Join Date: Mar 2005
Location: Ottawa, IL
12-Jun-2010, 01:33 PM #2
"General failure" is usually associated with a corrupted or mis-configured non-Windows firewall or security suite. Often ZoneAlarm or Norton. Un-install it and use the Removal Tool if one is provided.
Charles123138's Avatar
Charles123138 Charles123138 is offline
Junior Member with 3 posts.
THREAD STARTER
 
Join Date: Jun 2010
Experience: Intermediate
12-Jun-2010, 03:52 PM #3
OOOH... dumb me I forgot to check that, normally that's the first thing I check. Thank you so much
TerryNet's Avatar
Computer Specs
Moderator with 65,258 posts.
 
Join Date: Mar 2005
Location: Ottawa, IL
12-Jun-2010, 05:25 PM #4
You're welcome. Was it one of the two I mentioned?
Charles123138's Avatar
Charles123138 Charles123138 is offline
Junior Member with 3 posts.
THREAD STARTER
 
Join Date: Jun 2010
Experience: Intermediate
12-Jun-2010, 07:12 PM #5
nah it was kaspersky, I accidentally clicked block network activity when i was trying to pause protection to see if that was the problem. I guess restarting the router did work, except I blocked network activity. Thanks
As Seen On

BBC, Reader's Digest, PC Magazine, Today Show, Money Magazine
WELCOME TO TECH SUPPORT GUY!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.


(clock)
THIS THREAD HAS EXPIRED.
Are you having the same problem? We have volunteers ready to answer your question, but first you'll have to join for free. Need help getting started? Check out our Welcome Guide.

Search Tech Support Guy

Find the solution to your
computer problem!




Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools


Similar Threads
Title Thread Starter Forum Replies Last Post
Cannot communicate with Primary DNS server(192.168.0.1) gaurav123 Networking 1 25-Dec-2009 11:39 PM
Cannot Communicate with primary DNS server mdamore Networking 1 01-Dec-2009 03:18 AM
Solved: dell studio1555 "cannot communicate with primary DNS server" gian013 Networking 3 10-Nov-2009 03:24 PM
Help please cannot communicate with Primary DNS Server jackles Web & Email 0 02-May-2009 02:08 PM
Solved: "Cannot Communicate with primary DNS Server" jsautumn Networking 10 26-Nov-2008 09:52 PM

WELCOME
You Are Using: Server ID
Trusted Website Back to the Top ↑