Help With SecuritySpy Remote Access

crm
crm
edited October 2015 in SecuritySpy
I have two SecuritySpy servers setup in two properties using the same router (Billion). On one I can access SecuritySpy remotely but the other I can't (Web page Unavailable error.) The difference between the two is that they use different ISPs but I have used a port checker on the non-working setup which reports that 8000 is open. I am not getting anything in the SS log or the router log. Any advice on what I can do to troubleshoot the problem will be gratefully received.

Comments

  • Update. It is now working
    It seems that the Bonjour setting must be on.
  • Good to hear everything is working now. The Bonjour setting shouldn't have to be on for remote access to work, but in any case it can't hurt to have it on. Sometimes routers need a restart and/or some time to apply port forwarding settings, so perhaps this played a part too.
  • Unfortunately it seems my remote tester was accessing the setup that is working so the Bonjour setting, as you say, has no bearing on the problem so I am back to square one. The router has been restarted and the Mini Mac. Anything I can check to narrow down the problem?
  • Update. I have used http://canyouseeme.org/ to check port 8000 and it tells me that it gets a 'connection refused' error? I have another http service on 8050 and this service is accessible. Is it possible that this error comes from SecuritySpy?
  • It could be that your ISP is blocking port 8000 for some reason. Are you able to find out a list of ports that they block for incoming connections? If your router allows specifying a different external (WAN) port to the internal (LAN) port (most do), try other external ports (80, 88, 8080) to see if they work. In all cases the internal port should be 8000, as this is what SecuritySpy uses by default (I'm assuming you haven't changed this).

    Also, check whether there is a firewall enabled in the router on on the Mac (System Preferences -> Privacy & Security -> Firewall), and turn both off.

    If you are still having problems, please email us screenshots of all relevant settings (router settings, Mac IP settings, SecuritySpy Web Server Settings etc.) and we will take a look to see if we can spot anything wrong.
  • Is there a way of testing the browser on port 8000 from the internal network? This would help narrow the problem.
  • Yes - the best way to do this is to use your phone with the WiFi turned off, so that it is connected over 3G or 4G, then try to connect to your system from a web browser on your phone.
  • I have given up for the time being and will use Teamviewer to access the Mac remotely and use Security Spy on the server. I haven't changed the website port numbers. The local address of the Mac is 192.168.1.220 so I assume I should be able to use a browser on another Mac on the local network to point to 192.168.1.220:8000. When I do, i don't get a response. The Mac network utility indicates that 8000 is open - it shows the application as irdmi but I guess this is just what is in the known port list. I am starting to think it is a Mac issue (10.6). Please let me know if there is anything I can check.
  • If the Mac running SecuritySpy has an IP address 192.168.1.220, then yes you should be able to access it from another Mac by using a web browser and pointing it to 192.168.1.220:8000. If you can't, then this indicates a problem with the configuration on the Mac itself, rather than with your router.

    In the Web Server Settings window, make sure the "HTTP server enabled" option (i.e. the first check box in that window) is checked, and that the "Access control" checkbox is NOT checked (just in case this is set to block connections). Go to System Preferences -> SecuritySpy & Privacy -> firewall and make sure it's not on (it might be called something slightly different on OS X 10.6, but hopefully you'll be able to find it).

    Finally, you could try a different HTTP port (the first text box in the Web Server Settings window), just in case there is some configuration issue on your Mac that is prevening the use of 8000. Try 8080, for example. Then from another Mac try to connect to 192.168.1.220:8080.
  • Thanks for the advice but unfortunately still no go after following all your points. It may be time to rebuild the Mac Mini. Until I get around to that, Teamviewer will do.
  • crm,

    double check your ip address information is correct. maybe even triple check.
    then you might want to spend some time delving into your firewall configuration of the mac itself.
  • I have now replaced my mac mini and the new one, with the same setup (copied preferences file from the old one) and same port forward setup on the router and remote access is working fine.