Need help - network problem

roborobs computer repair

Active Member
Reaction score
35
Location
Kissimmee, FL
I have a customer who has three main computers connected two via Ethernet and one wireless. He also has three PS3's and three printers connected to the network. For some reason he is experiencing intermittent internet connection on the PC's. The error he is getting is cannot contact the DNS Server. All machines are connected with Static IP. He has a 40MB high-speed connection through bright-house networks cable.

so far we have replaced the router and modem, he has wiped one of the machines as told to by an online tutorial he found (don't let customers do their own research...), removed a program which seemed to be causing the problem and five minutes after I left it happened again.

Anything you can think of that would cause this and how do I fix it?
 
If you do an "IPCONFIG /ALL" from a workstation...what do you get for DNS servers?

Is the external DNS on the router being manually over ridden?
What if you flip the clients to "Obtain Auto"?
 
I've had issues with BHN's DNS servers. I also do not like that they use redirects if you mistype an address.

I would recommend switching over to another DNS provider like Opendns.

I have also seen issues(very rare) when the PC tries to directly query the external DNS server. For whatever reason, when I let the router do the lookup's for the PC, it worked fine.
 
If you do an "IPCONFIG /ALL" from a workstation...what do you get for DNS servers?

Is the external DNS on the router being manually over ridden?
What if you flip the clients to "Obtain Auto"?

I used IPconfig/all and got the DNS. This is part of what was confusing me. When I bring up the router on network magic it shows no DNS. Part of what is confusing me. Also the computers were originally setup as DHCP and now they have been switched and were actually holding the connection for over a couple hours.
 
When I bring up the router on network magic it shows no DNS.

"Network Magic"...yuck get that bloated thing out of the way. A computer tech should never be seen using that!

First thing I would do...log onto the routers web admin, and ensure its WAN interface is setup correctly. Are the external DNS servers set to 0.0.0.0? (meaning DCHP). Or is something else manually typed in there? 0.0.0.0 means they'll pickup the ISPs DNS servers. A default setup, but...not always ideal. I change to OpenDNS servers...208.67.222.222 and 208.67.220.220. Puts at added layer of security for the clients because it blocks out known malware distribution sites.

Now from a workstation, when you run an IPCONFIG....what are they getting for DNS servers? The routers LAN IP? Or the external DNS servers IP?
 
"Network Magic"...yuck get that bloated thing out of the way. A computer tech should never be seen using that!

First thing I would do...log onto the routers web admin, and ensure its WAN interface is setup correctly. Are the external DNS servers set to 0.0.0.0? (meaning DCHP). Or is something else manually typed in there? 0.0.0.0 means they'll pickup the ISPs DNS servers. A default setup, but...not always ideal. I change to OpenDNS servers...208.67.222.222 and 208.67.220.220. Puts at added layer of security for the clients because it blocks out known malware distribution sites.

Now from a workstation, when you run an IPCONFIG....what are they getting for DNS servers? The routers LAN IP? Or the external DNS servers IP?

I used Network Magic only because the client insisted on using it - I know sometimes the client isn't always right but when they pay for a product and expect it to work I try and make it work as best as possible before suggesting a new program. I try to make the customer as happy as possible even if that means using a program I do not personally care for. I will let the customer know my concern but if they feel it is still worth the hassle I'll leave it. In this case however we did end up removing the Network magic program.

Currently when I log into the router the DNS is set to one of Brighthouse's defaults I believe which is 65.32.5.111 and 65.32.5.112
 
Couldnt u always resort to just setting the dns in the tcp/ip properties

Edit: to clarify, resort as in one of the last resorts this is typically considered a bandaid fix.
 
Last edited:
Back
Top