[SOLVED] steps 9 and 10 of Network troubleshooter failing

[mshall]

Using the Network Troubleshooter, I failed step 9 - HDA used as DNS on clients?. Here's a paste to help troubleshoot: http://sprunge.us/cchP

I have normal default router DSL modem at 192.168.1.1, wifi router is 192.168.1.10

I have checked as best I can that there is no DHCP or DNS set up in either router.

I have released and renewed the config of this client computer which has windows 8. It is on 192.168.1.11

Step 10 also fails presumably same cause.

the settings of hda are ip 192.168.1.10; broadcast address 192.168.1.255
default route 192.168.1.1
primary dns is 192.168.1.10

I have set the client to have DNS of 192.168.1.10 primary blank secondary or to have automatic (The address is set up by amahi tobe static anyway.

I have searched the forums for any clues and am now at a loss and would appreciate any new ideas!

[bigfoot65]

Is this a new install? Ubuntu or Fedora?

I have normal default router DSL modem at 192.168.1.1, wifi router is 192.168.1.10

Something does not make sense here. You have more than one router? The DNS for your HDA is typically not a router.

With DHCP/DNS being done by the HDA, your clients should point to the HDA IP address vs the router.

[mshall]

Thanks for your reply.

Mine is a Ubuntu 12.04 set up after complete reinstall.

There is an adsl model and wi-fi router separately.

I made a mistake in my post the later is 198.168.1.2 NOT 10! Sorry.

The hda is 192.168.1.10. and its configuration was taken from the ubuntu eth0 connection description in system settings.....should it have the dns of 192.168.1.10 or should that be external?? But my problems seems to be that clients are going to external dns not the hda.

I confess to confusion and need help.

thanks again

[bigfoot65]

The HDA should be using it's own DNS. As for the clients, you have to release/renew the IP after turning off DHCP/DNS on your routers.

Once complete, the clients should point to the router as gateway and HDA for DNS.

[mshall]

Thanks for your reply.

But the HDA is using its own DNS and when I turned off DHCP I did renew the addresses of the clients so I think I have taken your advice already. DO I need to repeat anything?

The clients are definitely pointing to the router. But not HDA as DNS/

It seems the client is the problem maybe: Can you check this ipconfig result for the client?:

• C:\Users\Mike>ipconfig
  
  Windows IP Configuration
  
  
  Ethernet adapter Local Area Connection 3:
  
  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix . :
  
  Wireless LAN adapter Local Area Connection* 14:
  
  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix . :
  
  Ethernet adapter Local Area Connection:
  
  Connection-specific DNS Suffix . :
  Link-local IPv6 Address . . . . . : fe80::64e8:a27b:99f8:a598%18
  IPv4 Address. . . . . . . . . . . : 10.200.112.57
  Subnet Mask . . . . . . . . . . . : 255.255.248.0
  Default Gateway . . . . . . . . . :
  
  Wireless LAN adapter Local Area Connection* 11:
  
  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix . :
  
  Wireless LAN adapter Wi-Fi:
  
  Connection-specific DNS Suffix . : home.com
  Link-local IPv6 Address . . . . . : fe80::9846:4d6e:d58a:8b25%13
  IPv4 Address. . . . . . . . . . . : 192.168.1.11
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Default Gateway . . . . . . . . . : 192.168.1.1
  
  Ethernet adapter Ethernet:
  
  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix . :
  
  Tunnel adapter isatap.{D0BF78A3-6002-4DF8-8B69-FD44F41CCCFC}:
  
  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix . :
  
  Tunnel adapter Teredo Tunneling Pseudo-Interface:
  
  Connection-specific DNS Suffix . :
  IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:3c98:2e9:f537:8fc6
  Link-local IPv6 Address . . . . . : fe80::3c98:2e9:f537:8fc6%16
  Default Gateway . . . . . . . . . : ::
  
  Tunnel adapter isatap.home.com:
  
  Connection-specific DNS Suffix . : home.com
  Link-local IPv6 Address . . . . . : fe80::5efe:192.168.1.11%29
  Default Gateway . . . . . . . . . :

[bigfoot65]

Check using

Code: Select all

IPCONFIG /ALL

.

That should show the DHCP and DNS pointing to the HDA if it's working correctly.

[mshall]

Well...I checked the ipconfig /all and it shows everything as it should be and then I redid the nslookup and it is now working, though I didn't think I have changed anything since I last checked!!! I must have !!!!!

So Thanks, another wonderful mystery and everything is fine.

[cpg]

Glad it was sorted out (including logging in to the site!).

[mshall]

The logging in problem persists. I only got in by using Chrome. Maybe there is a bug which leads Firefox cookies to get corrupted or out of step. I will try clearing all cookies for Amahi and see if that clears the firefox issue. Otherwise I will just switch to Chrome if I need to post!

Thanks for your help and inspiring me to try Chrome!

Mike

[mshall]

Okay I deleted cookies and the behaviour was the same. I wonder if others have same problem with firefox (18.0.1). (and If that is a correct diagnosis). So I will just have to switch browsers when I need to post!

Mike