HDA not used as DNS on my Windows 7 clients :(

[excobra]

HI,

I have just installed amahi for the first time on my ubuntu 12.04. Very excited

I used guide from docs.amahi.org. everything was fine and i successfully installe amahi.

I am using amahi's dhcp and i have TURNED OFF my Router DHCP server

This fact can be further verified by the ip address assigned by DHA to my windows machine i.e. 192.168.1.100

Now the problem is although i cannot access internet on my Windows7 Client.

so i ran the interactive network troubleshooter. Everything was fine till step 9 which is HDA used as DNS on clients.
At this point as per instruction i ran the Command

Code: Select all

nslookup hda.home.com

in my Windows 7 Command prompt the result of this command was

Code: Select all

[color=#000000]Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\RehmanCNG>nslookup hda.home.com DNS request timed out. timeout was 2 seconds. Server: UnKnown Address: 192.168.1.10 DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to UnKnown timed-out[/color]

so this means my Windows 7 is not using correct DNS. i.e of

Here are the results of my network troubleshooter till step 9

Code: Select all

[color=#800000]Step 1: Your HDA IP address is 192.168.1.10 Step 2: Your HDA domain name is home.com Step 3: Your router IP address is 192.168.1.1 Step 4: Your HDA DNS server is working fine for local hostnames. Step 5: Your router is accessible from your HDA server. Step 6: You can access the internet (ping test successful). Step 7: Your HDA DNS server is working fine for external hostnames. Step 8: Your Amahi Dashboard is accessible.[/color] [color=#FF0000]Step 9 - HDA used as DNS on clients? After having deactivated the DHCP on your router, you'll need to renew the IP address of a client computer you'll use for the rest of the tests. Once that's done, execute the following command on that client computer, using either a command prompt, or a Terminal: nslookup hda.home.com Does it result in something like this (verify the parts in red): Server: 192.168.1.10 Address: 192.168.1.10#53 Name: hda.home.com Address: 192.168.1.10 Yes No[/color]

Please help me resolve this problem.
Thanks.
PS i guess i need to manually assign hda DNS in my router settings but not sure though as i have already tried that by putting primary DNS as 192.168.1.10 but it didnt work.

Please be simple as i ma new to linux and newtrking in general.

Thanks

[bigfoot65]

Did you refresh the IP on your client? If so, then it should work with DNS. Also ensure your router does not have a DNS server entry setup pointing somewhere else. If it does, you might wanna point it to the HDA.

[excobra]

Did you refresh the IP on your client? If so, then it should work with DNS. Also ensure your router does not have a DNS server entry setup pointing somewhere else. If it does, you might wanna point it to the HDA.

Yes i did refresh the ip on my client. Before amahi it was 192.168.1.3 after installing amahi it is always 192.168.1.100 as i can also see it from amahi dashboard aswell.

So clearly it means it is assiginng from amahi dhcp range i.e >100 as <100 are reserved as statitic.

further here is screenshot of my router dhcp


As for y router it is Aztek DSL 605EW and i can only find the following settings related to DNS
First

in this option i have furtehr 4 options for selecting
i) only aut discovered DNS
ii)Only User configured DNS
iii)auto discovered then user configured
iv)user configured then auto discovered

and second is dynamic Dns client as you can see


so plz now suggest where i am wrong.

Please help as my sibling will kill if my network is not up and running at weekend.

[bigfoot65]

I would try adding your HDA IP address in the user DNS server primary and secondary blocks. Then restart your router and release/renew your client network connection.

If that does not help, then we may need to do some additional research.

[excobra]

I would try adding your HDA IP address in the user DNS server primary and secondary blocks. Then restart your router and release/renew your client network connection.

If that does not help, then we may need to do some additional research.

I did as you told me but problem is still there. I cant use internet on client machine.

however i have noticed that even if i havnt manually assigned primary and secondary DNS as 192.168.1.10. and let it be automatic and then checked my windows machine configuration it showed that it is automatically using 192.168.1.10 as primary and secondary DNS

here is the output of ipconfig /all in windows 7

Code: Select all

Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\RehmanCNG>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : RehmanCNG-PC Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : home.com Wireless LAN adapter Wireless Network Connection: Connection-specific DNS Suffix . : home.com Description . . . . . . . . . . . : Broadcom 802.11g Network Adapter Physical Address. . . . . . . . . : 00-14-A5-1C-B7-74 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::f42b:2f6c:7a47:5c41%12(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.1.100(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Friday, July 13, 2012 6:39:40 PM Lease Expires . . . . . . . . . . : Friday, July 13, 2012 10:39:40 PM Default Gateway . . . . . . . . . : 192.168.1.1 DHCP Server . . . . . . . . . . . : 192.168.1.10 DHCPv6 IAID . . . . . . . . . . . : 218109093 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-D9-DF-C6-00-C0-9F-E3-2A-07 DNS Servers . . . . . . . . . . . : 192.168.1.10 192.168.1.10 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet NIC Physical Address. . . . . . . . . : 00-C0-9F-E3-2A-07 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Tunnel adapter Teredo Tunneling Pseudo-Interface: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter isatap.home.com: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : home.com Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes

From the first fewlines in this output one can see that windows does not know Primary Dns suffix. (dont know what it is)
DNS suffix search list home.com. shouldn't it be hda.home.com ?

also further in Wlan Adapter settings Dhcp server and DNS server are all 192.168.1.10
not sure it is ok or ?

here also the output of nslookup hda.home.com

Code: Select all

C:\Users\RehmanCNG>nslookup hda.home.com DNS request timed out. timeout was 2 seconds. Server: UnKnown Address: 192.168.1.10 DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to UnKnown timed-out

[bigfoot65]

The settings look ok from what I see. Check on the HDA dashboard under Settings, then Servers to see that the DNS Server shows as running.

Another thing that might help is to shut down your network. Then power up the Modem, Router, HDA, then clients once all that is up and working correctly. I have seen cases where things get all confused, but after doing the complete restart from off all is well.

You can remove the DNS settings from your router if you choose, probably not needed.

[excobra]

Thank you for your help.

I tried everything you tol me but still it is isnt working.

I have even delete my old hda and created new one and reinstall amahi but still my windows calinet cant access internet.


Thanks again for your time.

i gave up. Apparently it cant be done.

[excobra]

i am back with a weired reply.
i decided to use different client machine althouh it is also windows 7.

Look what happend. here again i was unable to access internet. BUt then i did sth new.

i checked that windows was assigning 192.168.1.10 as DNS automatically as it should. but the problem was it wasnt working. so i decided to use dhcp ip of my ubuntu hda server machine. i got this ip from amahi dshbaord. it was 192.168.1.101 so i manually put it windows network connection in ipv4 setting as use this dns address.

it worked like a charm. and i was able to access internet on my client machine. Downside it i have to manually assign DNS to each computer on my network to acces internet.

As a work around i thought why not assign this 192.168.1.101 i.e. dhcp of ubuntu machine as user defined DNS in my router. Strangly when i did that client machines stoped accessing internet.

isnt it strage that if you assign 192.168.1.101 in router as user defined DNS it didnt work but when i put it in windows network connection settings it did work.

not sure what is the problem.

my mobile phone still cant use home network

[bigfoot65]

Is the HDA IP adress < 100? I am confused as to what is going on now. Something is not set up correctly with your network and HDA. It's just trying to figure out what that might be.