OK. Here's one that has me baffled.
I'm trying to allow a customer to print from their remote site to a printer here. I've set up the printer on the LAN (10.10.90.60). I configured my laptop with a local IP (10.10.90.124), installed the printer drivers and I can print just fine on the LAN, using a Sophos Access point to connect.
To test outside connectivity, I fired up the hotspot on my phone and connected the laptop to the internet through the phone. Now, ipconfig on the laptop shows 192.168.0.5; ipchicken.com tells me my outside IP is 70.210.137.177.
I created a NAT rule to allow port 9100 traffic from 70..210.137.177 to one of my NATted IPs and I configured that traffic to go to 10.10.90.60 (the printer's IP).
I reconfigured the printer on my laptop to use the real world NATted IP. When I test, it fails. Nothing prints
Here's the baffling part. When I open the firewall log to troubleshoot the problem, the firewall log shows the traffic originating from 10.10.90.124, the IP I used earlier. Since that doesn't match the policy, it fails. When I run a tracert to the external IP, it goes through the phone to the internet and back in through our company circuit, so I know I'm not connecting directly through the LAN. Where is that IP coming from?
This thread was automatically locked due to age.
