changed IP address/router, cannot connect remotely
Posted: September 9th, 2015, 10:43 pm
I have sickbeard and sab running on the same computer. Tonight I swapped out a router (192.168.1.x) with a new router (192.168.0.x).
In my sabnzbd config, I have my host value set at 0.0.0.0. The port is 8080.
Now, I can reach sickbeard after the change at 192.168.0.x 8081, but sabnzbd won't allow connections remotely. On the computer running sabnzbd I can 'telnet localhost 8080' or 'telnet 192.168.0.x 8080' and get a connection. But if I try from another computer on the network, it doesn't work.
At first I thought the router might be blocking 8080, but 8081 works... so I doubt it is some sort of firewall thing.
host = 0.0.0.0
port = 8080
I did try restarting sabnzbd after the computer it was running on got the new 192.168.0.x IP address. No luck. Any ideas?
edit: I just did an nmap scan of the computer running sab from another computer. Just as my telnet commands showed, 8081 is accessible, 8080 is not. I tried port forwarding 8080 to the IP address of the computer hosting sab, but that didn't work.
edit2: I set the host value to the IP address that the router assigned the sab computer instead of using 0.0.0.0. Waiting for a download to finish then I'll restart sab and try that.
edit3: setting the host value to the computer's IP address did not work. I can still reach that computer on 8081 (sickbeard) but not sab on (8080). And I can still type http://192.168.0.100:8080 in a browser on the computer running sab and reach the service.
The new router I bought is a TP Archer C7 if that gives anyone an idea about what may be happening.
edit 4: I posted the same question on the TP router forums just in case there is something odd/unique about the Archer C7 router.
edit 5: I just figured it out. The windows firewall was blocking the connection. I turned off the 'private/lan/local' firewall. No change. I turned off the public firewall, and it connected. For some reason, windows 8.1 considers 192.168.0.x "public" access, but 192.168.1.x is "private" access. Weird.
In my sabnzbd config, I have my host value set at 0.0.0.0. The port is 8080.
Now, I can reach sickbeard after the change at 192.168.0.x 8081, but sabnzbd won't allow connections remotely. On the computer running sabnzbd I can 'telnet localhost 8080' or 'telnet 192.168.0.x 8080' and get a connection. But if I try from another computer on the network, it doesn't work.
At first I thought the router might be blocking 8080, but 8081 works... so I doubt it is some sort of firewall thing.
host = 0.0.0.0
port = 8080
I did try restarting sabnzbd after the computer it was running on got the new 192.168.0.x IP address. No luck. Any ideas?
edit: I just did an nmap scan of the computer running sab from another computer. Just as my telnet commands showed, 8081 is accessible, 8080 is not. I tried port forwarding 8080 to the IP address of the computer hosting sab, but that didn't work.
edit2: I set the host value to the IP address that the router assigned the sab computer instead of using 0.0.0.0. Waiting for a download to finish then I'll restart sab and try that.
edit3: setting the host value to the computer's IP address did not work. I can still reach that computer on 8081 (sickbeard) but not sab on (8080). And I can still type http://192.168.0.100:8080 in a browser on the computer running sab and reach the service.
The new router I bought is a TP Archer C7 if that gives anyone an idea about what may be happening.
edit 4: I posted the same question on the TP router forums just in case there is something odd/unique about the Archer C7 router.
edit 5: I just figured it out. The windows firewall was blocking the connection. I turned off the 'private/lan/local' firewall. No change. I turned off the public firewall, and it connected. For some reason, windows 8.1 considers 192.168.0.x "public" access, but 192.168.1.x is "private" access. Weird.