NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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 the IP in the menu of the server, do I need to make changes in other locations aswell?
Ferdi
For example
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'))
24 Replies
Replies have been turned off for this discussion
- Did you change the IP address of the gateway and dns servers?
- Changed the ip-adress in the system menu of the Readynas dashboard (both DNS and ethernet), still got problems
- If you log in with ssh, and enter
# host lolo.sickbeard.com
# host couchpota.to
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? - how do I do that?
- How do you do what?
StephenB wrote: If you log in with ssh, and enter # host lolo.sickbeard.com
# host couchpota.to
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?
These 2 steps.- ok. It sounds like the sticking point is that you don't know how to log in with SSH. Is that correct?
Let's back up. Can you tell us why you needed to change the IP address in the first place?
Also, did you make any other changes in your network at that point? That is, a new router, or a new internet provider? - 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. # host lolo.sickbeard.com
# host couchpota.to
Both give connection timed out; no servers could be reached# ping lolo.sickbeard.com
# ping couchpota.to
These 2 give: unknown host
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
