timdepourcq Posted September 20, 2011 Share Posted September 20, 2011 Hi All, I successfully installed my new i-on40 panel with the internal web server. It is connected to my internal home network via the onboard ethernet port. Accessing it locally from my lan works fine. What I tried now is opening that port in my router (port forwarding) so I would be able to access it via my ddns host name. (http://ddnshostname:port) But I keep seeing a blank page. Is the internal webserver only accepting connections from within it's own LAN? (what I could understand from a security perspective off course) Thanks in advance. Link to comment Share on other sites More sharing options...
fozzies Posted September 20, 2011 Share Posted September 20, 2011 You could try putting it into a DMZ on your router to be certain that you have port forwarded correctly Link to comment Share on other sites More sharing options...
timdepourcq Posted September 21, 2011 Author Share Posted September 21, 2011 As it is not the first port I'm forwarding I am sure I forwarded it correctly. But apparently putting it in the DMZ did the trick, so I suspect the web server uses more than 1 port, so thanks for the tip. Not sure though, this is a desired final situation. Link to comment Share on other sites More sharing options...
fozzies Posted September 21, 2011 Share Posted September 21, 2011 Whilst the unit is in the Dmz, run the command line application netstat /a. then run it again without the unit on, and work out which other ports are being used by comparing the two lists. make sure to quit unneeded applications before doing both tests to keep the list of used ports to a minimum. There is also a downloadable utility called something like ipstat that will show all comms for you, but i cant remember the name, giyf for that one. a network sniffer would also do the job, but you may find the results confusing. Link to comment Share on other sites More sharing options...
fozzies Posted September 21, 2011 Share Posted September 21, 2011 The utility is called tcp view Link to comment Share on other sites More sharing options...
james.wilson Posted September 28, 2011 Share Posted September 28, 2011 you might find your isp blocks port 80, plus its usually a breach of your bb terms to run a server over it.... which you are doing etc securitywarehouse Security Supplies from Security Warehouse Trade Members please contact us for your TSI vetted trade discount. Link to comment Share on other sites More sharing options...
fozzies Posted September 28, 2011 Share Posted September 28, 2011 Cant be isp blocking, it works in a dmz Link to comment Share on other sites More sharing options...
james.wilson Posted September 28, 2011 Share Posted September 28, 2011 there you go then. There are implications to that as you are now shoving everything that your router gets from the whole world into your alarm panel. Use DMZ with caution securitywarehouse Security Supplies from Security Warehouse Trade Members please contact us for your TSI vetted trade discount. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.