Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Author Topic: TP-LINK TD-W9980 replacing HH3  (Read 3939 times)

keithwjones

  • Just arrived
  • *
  • Posts: 3
TP-LINK TD-W9980 replacing HH3
« on: March 07, 2015, 05:21:16 PM »

BT Infinity 2. I have ECI modem and HH3, getting resolving host issue.

Decided to change modem for:
Firmware Version:0.6.0 1.10 v0021.0 Build 141215 Rel.41342n
Hardware Version:TD-W9980 v1 00000000

But I am still getting Resolving Host issue.

At present connected through ECI modem.

I am getting a test error:
Test DNS Root - Fail

Anyone got any ideas. I have tried all sorts to get rid of the issue.

Keith
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: TP-LINK TD-W9980 replacing HH3
« Reply #1 on: March 07, 2015, 05:42:51 PM »

Welcome to the Kitz forum.  :)

Just to confirm that I understand . . . You had an ECI modem (in the default configuration bridge mode) and an HH3 acting as a router/switch/DNS server/DHCP server/WAP, etc and have now replaced the HH3 with the TP-Link TD-W9980 whilst retaining the ECI modem?

You mention that there is a "Resolving Host" issue; I assume that is part of a message output by one of the devices? The fact that you see a "Test DNS Root - Fail" message makes me think that the problem is with the router obtaining DNS server addresses and then using them locally to resolve DNS queries. Was the problem also present when the HH3 was in use? And is still present when the TP-Link is used?

Perhaps you could try specifying DNS server IP addresses to use, explicitly, in the router's (HH3 or TP-Link) configuration. Try using 8.8.8.8 and 8.8.4.4 (Google's public DNS servers) as a quick test.

Puzzling.  :-\
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

keithwjones

  • Just arrived
  • *
  • Posts: 3
Re: TP-LINK TD-W9980 replacing HH3
« Reply #2 on: March 07, 2015, 06:08:54 PM »

Setup as you say.

Resolving Host comes up in Chrome browser. Other browsers are sluggish.

Problem was also present with HH3, from research others had solved it by getting a new router.

When I first installed the TP it automatically used DNS:
213.120.234.22
213.120.234.34

I changed that to 8.8.8.8 etc.

Keith

Logged

ejs

  • Kitizen
  • ****
  • Posts: 2078
Re: TP-LINK TD-W9980 replacing HH3
« Reply #3 on: March 07, 2015, 06:34:06 PM »

I think the "Test DNS Root - Fail" is just a broken test which always fails. The test being broken doesn't really matter and won't affect anything else. I think the test does a DNS lookup for www.root-servers.net, which doesn't seem to exist, and I'm not sure what the purpose of a test looking up that name could possibly be.
Logged

keithwjones

  • Just arrived
  • *
  • Posts: 3
Re: TP-LINK TD-W9980 replacing HH3
« Reply #4 on: March 09, 2015, 11:27:11 AM »

I think  have an answer.

Problem was with BT Infinity 2, ECI Modem and HH3. I thought HH3 was the issue so put in a TP-Link TD-W9980. Windows 7.

I have used the answer of A Guy at http://www.sevenforums.com/browsers-mail/336501-google-chrome-resolving-host.html

Let's flush the DNS cache and restore MS's Hosts file. Copy and paste these lines in Note pad.

Code: [Select]
@Echo on
pushd\windows\system32\drivers\etc
attrib -h -s -r hosts
echo 127.0.0.1 localhost>HOSTS
attrib +r +h +s hosts
popd
ipconfig /release
ipconfig /renew
ipconfig /flushdns
netsh winsock reset all
netsh int ip reset all
shutdown -r -t 1
del %0

Save as flush.bat

Right click the .bat file and choose to Run as Administrator. Your computer will reboot itself. See if that fixes it.

Appears to have worked for me, before I used this I tried many other things, here are some:

http://www.webnots.com/correct-chrome-resolving-host-issue/

Keith
Logged
 

anything