Moshe Posted March 24, 2010 Posted March 24, 2010 I have enabled internet access for my ISY. I did not receive any errors messages but the IP returned is 0.0.0.0. I am using version 2.7.13. Any suggestions. Thanks
Michel Kohanim Posted March 24, 2010 Posted March 24, 2010 Hi Moshe, It seems that your router does not support UPnP. What you want to do is to manually create port forwarding rules in your router: http://www.universal-devices.com/mwiki/ ... PnP_Router With kind regards, Michel I have enabled internet access for my ISY. I did not receive any errors messages but the IP returned is 0.0.0.0. I am using version 2.7.13. The static IP for my ISY is 192.168.1.200 Any suggestions. Thanks
Moshe Posted March 24, 2010 Author Posted March 24, 2010 Michel - The port forwarding worked great. Thanks
Moshe Posted March 26, 2010 Author Posted March 26, 2010 I am using port forwarding with my ISY 99. I have changed the default port number from 443 to a different port. The ISY rebooted and new port is shown. However, when I use my dyndns account without any port number in the address my ISY page comes up just fine. It seems like it is still using the default port number 443. Thanks
markens Posted March 26, 2010 Posted March 26, 2010 I am using port forwarding with my ISY 99. I have changed the default port number from 443 to a different port. The ISY rebooted and new port is shown. However, when I use my dyndns account without any port number in the address my ISY page comes up just fine. It seems like it is still using the default port number 443. Sounds like port forwarding in your router is configured to forward port 443 received from the WAN (dyndns address) to the changed port on the ISY. Perfectly valid configuration, although evidently not what you want. What happens when you try to access the ISY locally via its LAN address? --Mark
Moshe Posted March 26, 2010 Author Posted March 26, 2010 Mark - When I access the ISY locally via IP address it works just fine. I thought if the router is forwarding to 443 it should not see my ISY, because the ISY's port number is not 443 any longer. Thanks
Michel Kohanim Posted March 26, 2010 Posted March 26, 2010 Hi Moshe, Two questions: 1. Locally, you are not using the HTTPS port. Please note that there are two ports in ISY: one is HTTP and the other HTTPS. Please ensure that you use the HTTPS port and that you are accessing your isy using https://your.dyndns.url 2. In your router configuration for port forwarding, there are two ports: one is public (from outside) and one is private (your ISY's port number). As such, there will be a mapping from the public to private. Make sure these two values are EQUAL to your ISY's new HTTPS port 3. Make sure your ISY is not in the DMZ With kind regards, Michel
Moshe Posted March 26, 2010 Author Posted March 26, 2010 Hi Michel - Question 1: I am not using HTTPS locally. I have checked my ISY and the port that was changed is the HTTPS port. When I use my dyndns address off site (not locally) without any any port definition the ISY home page is resolved. Question 2: I need to check my fios router to make sure my port number is the same for the private as well as the public. However, I did not see this the first time I setup the forwarding. I still don't not understand why I am able to resolve my ISY's home page if I changed the HTTPS port number. Thanks
Davonavo Posted March 26, 2010 Posted March 26, 2010 Hey Michel, us older guys understand step # 3. Younger guys may not.
Michel Kohanim Posted March 27, 2010 Posted March 27, 2010 Hi Moshe, I would certainly look at the DMZ ... you will find it under firewall section. DMZ basically means that your ISY is on the internet and all traffic is forwarded to it. Davonavo, thanks so very much. Sometimes I forget that some of these terms are a little technical. With kind regards, Michel
Moshe Posted March 28, 2010 Author Posted March 28, 2010 Michel - I forgot to say that my ISY was not in the DMZ. I doubled checked to make sure. Any other ideas. Thanks
Michel Kohanim Posted March 28, 2010 Posted March 28, 2010 Hi Moshe, I am completely at a loss! From what I know of routers and NAT (network address translation), your case is simply an anomaly! Are you sure you do not have any port forwarding rules for port 443 pointing to ISY? Beyond that, unfortunately, I really do not know what else could be wrong except perhaps a bug in the router. Have you tried rebooting the router? With kind regards, Michel
Moshe Posted March 28, 2010 Author Posted March 28, 2010 Michel - I did have port 443 forwarded to the ISY, but I thought when I changed the port # in the ISY for HTTPS to different port that rule (443 rule) would no longer work, but it still does. I am trying to get it to work for a differnet port number (not port 443). Do I need to port forward TCP and UDP? Thanks
Michel Kohanim Posted March 28, 2010 Posted March 28, 2010 Hi Moshe, Can you let me know which one of the following URLs work on your local network (not internet): httpS://your.isy.ip.address httpS://your.isy.ip.address:new_isy_port With kind regards, Michel
Moshe Posted March 28, 2010 Author Posted March 28, 2010 Michel - HTTPS://my.isy.ip.address:new_isy_port works on my local network. The other does not resolve.
Michel Kohanim Posted March 28, 2010 Posted March 28, 2010 Hi Moshe, What this means is that you have a mapping between port 443 to the new port on your ISY. In most routers, when you create port forwarding rules, they allow you to provide an public port (i.e. 443 in your case) and a private port (i.e. your ISY's new port in this case). What you want to do is to make sure that the public port is EQUAL to the private port (=ISY's new port). With kind regards, Michel Michel - HTTPS://my.isy.ip.address:new_isy_port works on my local network. The other does not resolve.
Moshe Posted March 29, 2010 Author Posted March 29, 2010 Hi Michel - I have figured out the problem I was having. 1. The Action Tec router from Verizon needed a firmware upgrade. 2. The firewall at my place of work had my new ISY port number shutdown. Thanks for all your help.
Michel Kohanim Posted March 29, 2010 Posted March 29, 2010 Moshe, Excellent and so very glad to hear. And, thanks for the update. With kind regards, Michel
Recommended Posts