NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Proper Duo Network Config
I use my Duo v1 to run Backup on several desktops at home. Name resolution has been hit-or-miss over the years, and before I upgrade to a x86 product I would like to see if I can make this old box per...
After a great deal of experimenting I can offer the following results and reflections on my problem which still exists, and still exists for my new NV+ v2.
Stephen, unlike you, I need a wins server because my DHCP server, which is my router/firewall/default gateway, does not keep track of names.
So I now have the ReadyNas Duo v1 running as a WINS server, and have configured the ethernet adapter on all my computers to reflect that. By the way, this requires giving the Duo a fixed IP since the apapter settings require an IP address for the WINS server (under the TCP/IP properties).
Unfortunately, I strongly suspect that the Duo firmware is written so that whenever the Duo is configured to use a static IP it also requires static DNS I.P. entries. Because I am a home user I do not have static DNSes--they are passed to my router from my ISP.
I believe that the subnet settings of my network devices are correct (255.255.255.0).
One problem I can pinpoint is that while Windows can successfully create a network map of all devices on my network, pinging some of these same devices on my network returns completely different IP addresses that are unreachable by the ping command.
For example, right now if I hover over my new NV+ in a win 7 network map window, the IP adderess 192.168.168.151 is displayed--as one would expect since I configured it with that static IP. However pinging the NV+ by name returns 204.232.137.207, and fails to connect.
I'm baffeled that these are different!
Clearly Windows is using a different name resolution procedure than ping (or nbtstat for that matter).
Both of my NASes must be using the same name resolution process as ping which would explain why my backup jobs are failing.
As allways, I am most appreciative for any advice or suggestions since I am really in a bind.
Stephen, unlike you, I need a wins server because my DHCP server, which is my router/firewall/default gateway, does not keep track of names.
So I now have the ReadyNas Duo v1 running as a WINS server, and have configured the ethernet adapter on all my computers to reflect that. By the way, this requires giving the Duo a fixed IP since the apapter settings require an IP address for the WINS server (under the TCP/IP properties).
Unfortunately, I strongly suspect that the Duo firmware is written so that whenever the Duo is configured to use a static IP it also requires static DNS I.P. entries. Because I am a home user I do not have static DNSes--they are passed to my router from my ISP.
I believe that the subnet settings of my network devices are correct (255.255.255.0).
One problem I can pinpoint is that while Windows can successfully create a network map of all devices on my network, pinging some of these same devices on my network returns completely different IP addresses that are unreachable by the ping command.
For example, right now if I hover over my new NV+ in a win 7 network map window, the IP adderess 192.168.168.151 is displayed--as one would expect since I configured it with that static IP. However pinging the NV+ by name returns 204.232.137.207, and fails to connect.
I'm baffeled that these are different!
Clearly Windows is using a different name resolution procedure than ping (or nbtstat for that matter).
Both of my NASes must be using the same name resolution process as ping which would explain why my backup jobs are failing.
As allways, I am most appreciative for any advice or suggestions since I am really in a bind.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
