Default Gateway problem in embedded lan P3

[carballada]

I use 5.00m in a P3.

I can connect from the same net to P3's web without problems but I can't connect from other net.

P3 ip config is
ip 192.168.5.34
mask 255.255.255.0
default gateway 192.168.5.1

I use a Cisco 877 in 192.168.5.1 and I can test with other machine replacing P3 and works...

seems some problem with default gateway parameter and embedded LAN, no problems with the router, for testing I disabled firewall and now it's working another webserver in port 8081 for Reef Status (pc with 192.168.5.7)

some suggestion?

[carballada]

I make more test and I confirm no problems with 10001 port connection from outsite net (ProfiluxControl 5.0.0.9)

NAT seems work for other ports (not 80) and 80 in other machines, I believe that the problem maybe is in P3 webserver, but I am not sure, some suggestion?

thanks in advance

[legaultrm]

I'm seeing the same problem. I can view my web server only if I'm on the same subnet. If I try to view the webserver from my office which is tied together with a VPN, it does not work. I can use the Profilux Control from work with out any problems.

[Matthias]

I tested it with these subsystems: 192.168.0.xxx and 192.168.1.xxx (VPN)

my PC has 192.168.0.6 and the ProfiLux 3 192.168.1.64

I was able to access the P3 over the webinterface (port 80) and with ProfiLuxControl (port 10001) - no problems at all in both cases

maybe you check the settings in your routers?

[carballada]

I tested it with these subsystems: 192.168.0.xxx and 192.168.1.xxx (VPN)

my PC has 192.168.0.6 and the ProfiLux 3 192.168.1.64

I was able to access the P3 over the webinterface (port 80) and with ProfiLuxControl (port 10001) - no problems at all in both cases

maybe you check the settings in your routers?

Sorry Matthias, I can't understand what happen, my Cisco routes seems ok (without firewall for this testing and simply NAT addressing)

I make another test: I change my P3 for a desktop with the same ip address and apache and I can access from Internet to this 'substitute', it works.

I am using now another server with apache and reverse proxy for to access to my P3 but it's no a solution.

Matthias in your test you are making NAT between your two nets? port 80 and 10001 only? remember that my ProfiluxControl (port 10001) works ok from Internet, I have only problems to access my P3's web server in port 80

Maybe something with 192.168.5.xx net, but it is strange only for this range.

[boboxx]

I had the same problem when I tried to setup Michael P3, I could access port 10001 with PLC but not the web...

Michael network class is 192.168.1.0

[aqua_digital]

yep as above same issue, unable to connect, Christian spent about an hour trying all methods, and he really knows his stuff, but no conection.

Seems we have a building case matthias here :(

[boboxx]

I had no issue configuring mine, took me 1 min max... I simply could not configure the one for Michael.

I tried port forwarding port the same internal port to external port 80 -> 80, same internal to something different on the outside to make sure ISP was not blocking 80 -> 8080, random to random (above 1000) 4002 -> 4002, I tried putting it in the DMZ and we could never access port 80 from the outside. On the inside it was working fine.

Is the web server binding to the internal IP/Port or is it binding to the listening port only? It could be a problem with some routers if it's binding to IP/port.

[AQUA-IT]

I think it works. On your system is Port 80 the internal Webserver from the Internet-Router? This could be the problem! For a test please map external Port 90 to internal Profilux Port 80.

[boboxx]

I tried that with Michael, it did not work, I even tried 80 local to 10001 external witch I knew worked because I could connect with PLC….

[boboxx]

hey mike, sure send me a pm

[dr.dotti]

Hi,

my experience is sometime it works and sometime not without any change.

[Matthias]

we have it here working now for weeks, everytime I want to connect over browser or ProfiLuxControl I get immediately a response from any P3 we have connected on both subnets

maybe it has something to do with using dynamic IPs for the ProfiLux? Is it working when the IP is static?

[boboxx]

no that's not the issue, I could connect using PLC no problem

[boboxx]

Hey Mike I tought you could connect internaly if you where connecting to http://192.168.1.128:8090?

Is that still working internaly?