I have previously been using a D-Link DSL-G604T Router (the noisy one) to connect to the net via UK Online, with relatively few problems (i.e. if it doesnt connect, turn it off and back on again). However, this time the problem remains, and fails the DNS test in all troubleshooters. Since I don't have much of an idea what DNS is, or why it is important, I couldn't guess at the cause of the problem. What I do know, however, is that without me touching anything, suddenly i was booted from the internet and couldn't connect again. I know the fault does not relate to my ISP as I am currently connected with the dire default Voyager 105 USB Modem. This is extremely bad, as not only does it mean I lose my firewall, but the modem is significantly less reliable than the 56k modems pf yesterday, with me on the edge of my seat hoping it doesn't lose the DSL signal... Has the router failed or could something in windows automatically meddled with my settings? If so, what can I do to put them back? (P.S. I have restored factory settings, wiped connections etc. etc. on the router, and this does not resolve the problem)
DNS is what translates a domain name to an IP address, else you would have to type the ip address for any web site instead of www.whatever.com. Check to make sure that port 53 is not blocked, that is what DNS uses. Check your computer TCP/IP config by typing ipconfig /all at a command prompt and see what DNS server you are using, and try to find out what DNS server you should be using from your ISP and make sure it is the one listed.
I will go ahead and do that, but why would that suddenly go wrong? And whay does it mean that I can't connect to my ISP?
It's hard to say why it would not connect all of a sudden. Do you even get an IP address? Usually if you are not connecting to the ISPs DHCP server you will get a 169.254.x.x address. Thats the non routeable block the IANA has reserved for automatic assignment if you can't get an IP from your DHCP server.
Sorted problem, Encapsulation should be VC not LLC. Dunno how that change Anyway hats of to Tech support, problem solved in 11 minutes.
