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 the IP in the menu of the server, do I need to make changes in other locations aswell?
Ferdi
For example
[hpotato.core.plugins.base] Failed opening url in CouchPotatoApi: https://couchpota.to/api/search/jack+the/ Traceback (most recent call last): File "/usr/share/cpserver/couchpotato/core/plugins/base.py", line 148, in urlopen response = urllib2.urlopen(request, timeout = timeout) URLError: <urlopen error [Errno -2] Name or service not known>
2013-07-14 11:41:54.203820 SEARCHQUEUE-RSS-SEARCH :: Error loading Sick Beard Index URL: http://lolo.sickbeard.com/api?t=tvsearch&cat=5040%2C5030 2013-07-14 11:41:55.102853 CHECKVERSION :: Unable to contact github, can't check for update: IOError('socket error', gaierror(-2, 'Name or service not known'))
Do both resolve to IP addresses? (lolo.sickbeard.com should redirect to lolo.sickcache.com, which should give you 5 IP addresses).
If so, see if ping works:
# ping lolo.sickbeard.com # ping couchpota.to
Was this change in IP address because you changed to a new internet provider? Are you still using the same LAN/WiFi setup - if not, what changes did you make?
Do both resolve to IP addresses? (lolo.sickbeard.com should redirect to lolo.sickcache.com, which should give you 5 IP addresses).
If so, see if ping works:
# ping lolo.sickbeard.com # ping couchpota.to
Was this change in IP address because you changed to a new internet provider? Are you still using the same LAN/WiFi setup - if not, what changes did you make?
Well I'm using WinSCP that's for SSH aswell right?
My change in ip-adress is because of a change from cable internet to internet using fibreglas. So I have a new router and had to change the internal ip-adress because of the set-up in the new router. New DHCP adress pool from 192.168.2.1 to 192.168.2.252. On my previous router the ip-adress of my NAS was 192.168.0.100, so I had to change it. Otherwise I couldn't get in to the NAS.
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.
Try checking the gateway address and DNS server on your PC, and make sure it matches.
To do this (a) click on the windows start button (b) type "cmd" (without the quotes) in the "search programs and files" bar and press enter (c) a command line window with a black background will open up. Click on it, and enter "ipconfig /all" at the prompt (again without the quotes). press enter
If you scroll through the info it gives you, you will find your PC ipv4 address, subnet, DNS server and gateway (with a lot of other stuff).
While there, try entering these ping commands and see if the PC gets a response:
Ok.i think StephenB has helped you to find the problem. Your PC and the NAS are on the same network using the same gateway yet you have set different gateways for each and different dns servers. This is why I asked you whether you had changed these in my first post. The gateway cannot be 192.168.2.1 as you have stated that this is part of the dhcp pool. The gateway address should be that of your device that is connected to the Internet or WAN. It looks like this is 192.168.2.254. The DNS servers addresses are there too, although you should be able to just enter ( in the readynas) your gateway address as the DNS server address.
