yet another superhub issue. dns not found

TheWoodster · 14-02-2011, 20:34

Like a lot of people on here i have had the free upgrade to 30meg with the new superhub.
On my pc i am running win 7 64bit, wireless connections work fine, I run a win2008 server also.

The server which is wired in works fine as do the wireless connections, mainly iphones and 1 win 7 32bit.

On my main pc which is wired in I cannot get a connection to the internet and the diagnostics state it dns server is not responding.
At first the connection worked fine then it has dropped out all together.

Is there anything i can do, I even took the drastic step of reinstalling windows thinking i had a virus.
After working for a few hours it dropped out all together.

Thanks

General Maximus · 14-02-2011, 21:49

dude dude dude, surely this is down to how you have configured your lan and especially the server and nothing to do with the superhub and your connection?

From both your pc and the server and click on start, run and type in cmd which will open a command prompt. Type in nslookup and hit enter. In theory it should display the virgin dns server as cache1.service.virginmedia.net at 194.168.4.100.

The other thing you can try is to manually set your ip address, sub net, default gateway and dns server in your connection properties.

Have you tried pinging an ip address to see if it is actually a connection issue and not a name resolution problem?

qasdfdsaq · 14-02-2011, 21:56

Turn off the firewall and IP flood detection to see what happens. At least one other user has had intermittent blocking of outbound port 53 (DNS) traffic by the superhub for unknown reasons.

TheWoodster · 14-02-2011, 22:05

apologies, didnt make myself very clear. it was to do with name resolution from my pc to the internet, the lan was fine but couldnt get to the outside.
the server works fine without issue.
Ive turned off the flood detection and it works fine now.

Thanks

General Maximus · 15-02-2011, 07:42

Quote:

Originally Posted by qasdfdsaq

At least one other user has had intermittent blocking of outbound port 53 (DNS) traffic by the superhub for unknown reasons.

does it block port 80 as well?

joveonmars · 16-02-2011, 21:28

Go to your network interface card details and see what it says next to "IPv4 Default Gateway", it needs to say 192.168.0.1 & "IPv4 DNS Servers" 192.168.0.1 means it will acquire the DNS address from the superhub.

For your NIC to obtain the DNS address from the superhub automatically, it needs to be set to "Obtain DNS server address automatically" under "Properties" & "Internet Protocol Version 4 (TCP/IPv4)", or you can set it manually to 192.168.0.1