NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Ferdi1
Jul 14, 2013Aspirant
Change in IP adress
Hello, Recentley I had to change the internal IP-adress of my NAS from 192.168.0.100 to 192.168.2.100. Ever since apps (like sickbeard and coachpotato) are giving connection errors. I only changed ...
StephenB
Jul 24, 2013Guru - Experienced User
WinSCP does both FTP and SSH. I use putty myself, so I am not clear the details of WinSCP.
If you are using SSH, then when you connect to the NAS you'd log in as root, but use your admin password. You'd only be able to connect if you've previously installed Netgear's enablerootssh add-on (which you can find here: http://www.readynas.com/?p=4203).
Once connected, you'd see a command line prompt, which ends with a # symbol. From there, you just type the commands above (omitting the #), and note the response.
I am thinking there is probably an issue with DNS, the "host" commands are checking for that.
Something else you could try: configure the NAS to use DHCP, and see if the behavior changes.
If you are using SSH, then when you connect to the NAS you'd log in as root, but use your admin password. You'd only be able to connect if you've previously installed Netgear's enablerootssh add-on (which you can find here: http://www.readynas.com/?p=4203).
Once connected, you'd see a command line prompt, which ends with a # symbol. From there, you just type the commands above (omitting the #), and note the response.
I am thinking there is probably an issue with DNS, the "host" commands are checking for that.
Something else you could try: configure the NAS to use DHCP, and see if the behavior changes.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!