Have searched and found numerous reports on how to fix the ReadyNas (in my case ultra) DNS problems. Most of them refer to switch to DHCP. None of them are resolving my problem, which is that the readynas cannot connect to the internet.
It sits on the same network as my other computers (and Handhelds), All of them have internet access and no problem accessing sites using DNS. IP address in correct range, Gateway correct, DNS-server address correct, Subnet mask correct.
The ReadyNas (ultra 4) behaves correctly inside my network, no problems with accessing shares or using time machine or DLNA.
The ReadyNas cannot get time from time servers, can not connect to ReadyNas remote servers, cannot send alerts, cannot get updates.
Are you using DHCP? If not, what IP address and subnet are you using?
I'm using DHCP, and all IPs seem correct (same Gateway and DNS-adresses as all my other computers. All Computers (Including the ReadyNas) are behind a NetGear Prosafe FVS338, all computers except for the ReadyNas can access internet.
Last night I also did a factory reset and after that a test SSH:ing to the ReadyNas, and tried to ping some external adresses (including the DNS). All packets Lost. Did the same at the same time with another computer on the same network, and no packets were lost.
These are the Network settings (all assigned by DHCP): IP: 192.169.0.19 SubnetMask: 255.255.255.0 Gateway:192.169.0.1 DNS:192.168.1.254 (have also tried with 192.169.0.1)
All Computers (working) on the network use the above settings for subnet, gateway, DNS.
Sounds like you are double-routed (or else you mistyped the 192.168.1.254) Is the ProSafe the 192.168.x.x device, or is there another router in front of it?
BTW, did you pick 192.169.0.x as an address range? That is a routable internet address, it is not intended for NAT. 192.168.x.x, 10.x.x.x, and 172.16.0.0 to 172.31.255.255 are the three ranges of private (non-routable) addresses.
What happens if you resolve the DNS name on a computer, and then ping the actual IP address (not the name) on the ReadyNAS?
Well, there is another router (ADSL-modem) in front of the FVS338. That's where the 192.169.1.254 adress is originating from. The ProSafe is the 192.169.0.1. The reason I'm using 192.169 is pure inheritance. I doubt however that that would be the reason for why the ReadyNas is not resolving or even being able to ping adresses outside the Network.
Adresses resolved by other computers, also behind the nat, (for instance www.google.com or ftp.sunet.se) will not work on the ReadyNas, but works perfectly on other computers behind the NAT.
Pinging from the ReadyNas: ultra:~# ping 194.71.11.69 PING 194.71.11.69 (194.71.11.69) 56(84) bytes of data. ^C --- 194.71.11.69 ping statistics --- 7 packets transmitted, 0 received, 100% packet loss, time 6000ms
Pinging from another computer: $ ping 194.71.11.69 PING 194.71.11.69 (194.71.11.69): 56 data bytes 64 bytes from 194.71.11.69: icmp_seq=0 ttl=52 time=33.784 ms 64 bytes from 194.71.11.69: icmp_seq=1 ttl=52 time=33.458 ms 64 bytes from 194.71.11.69: icmp_seq=2 ttl=52 time=33.741 ms 64 bytes from 194.71.11.69: icmp_seq=3 ttl=52 time=34.637 ms 64 bytes from 194.71.11.69: icmp_seq=4 ttl=52 time=33.883 ms 64 bytes from 194.71.11.69: icmp_seq=5 ttl=52 time=35.148 ms 64 bytes from 194.71.11.69: icmp_seq=6 ttl=52 time=33.948 ms ^C --- 194.71.11.69 ping statistics --- 7 packets transmitted, 7 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 33.458/34.086/35.148/0.547 ms
Then you assigned the ProSafe to 192.169.0.1? If so, you would do better to change that to 10.0.0.1.
192.169.0.1 is a "real" (public) internet address, part of a block of addresses owned by a company in state of Washington (US). Using a public IP address inside a NAT can create problems with some protocols (though I don't think that is happening to you in this case, it would happen later on). You really shouldn't use someone else's public IP address, you should use one of the private address ranges I listed above.
Also, based on your post, your problem is more fundamental than DNS. Pinging the IP address 194.71.11.69 caused the timeout - DNS was not involved in that ping, as there was no address resolution involved.
What happens if you ping the ADSL modem? Nor sure from your post if that would be 192.168.1.1 or 192.168.1.254.
