Hi,
Obviously I know that the webserver defaults to port 80 so that is a port I have forwarded so I can access the status screens. However, the standard 10001 port that appears to the only one required to access the P3 using ProfiluxControl doesn't seem to be right. If I open port 10001 on the router it won't connect, however if I set the P3 as a DMZ it DOES connect.
Are there additional ports that need to be opened in order to access the P3 using ProfiluxControl?
This has all come about because of the issues with a P3 in a corporate network environment, so I have done as suggested and bought a second router and connected that to the corporate LAN. That effectively creates a WAN port on the new router with a corporate IP address, and I'm accessing the P3 using that address.
The numbers are:
New router: 172.16.1.174 (corporate WAN) // 192.168.1.1 (new router LAN)
P3 static IP: 192.168.1.2
DHCP: Off
Port forwarding: 80 -> 192.168.1.2:80 and 10001 -> 192.168.1.2:10001
As said, if I type in 172.16.1.174 into a web browser on the corporate LAN side it DOES access the P3 status page correctly. So that means the static 192.168.1.2 IP is correct and working. However, trying to access using ProfiluxControl set to AUTO doesn't work, and doing it manually with the WAN IP also doesn't seem to work which suggests there is another port it needs forwarding - when DMZ is on (ie. all ports being requested go through the new router) it DOES work.
I could of course leave DMZ on but I'm now fairly sure the whole reason this is needed is because the P3eX is responding badly to DHCP messages and hence the LAN port breaks. Ideally the DMZ should not be on so it can filter only the packets it knows how to respond to.
Thanks.
Bookmarks