Hi Bob,

Did the i previously have a publicly accessible IP address?

This whole thing kind of depends on how the firewall was setup; if it was just allowing traffic to pass through to another public IP behind it, or if it was perhaps translating a public IP address to a private internal address. I'm not exactly familiar with a Sonicwall, but if you are still having trouble I can get in touch with someone who can probably help.

Can you ping anything past the firewall from the i?

Clay Carley
Sonic.net/Sonic Telecom

On 03/08/2014 04:10 PM, Bob Cagle wrote:
First off, I'm a one-man IT shop, and networking is NOT my specialty, AND my normal network consultant is busy dealing with another customer's emergency already - so I'm grasping at straws here:

My ISP just assigned me a block of new IP addresses with our latest upgrade, so I had to assign a new public IP for the System i.

Made the changes to the firewall, and thought all was well; all I had to do was change the public IPs from old to new - but now I'm unable to connect to the System i remotely.

You would think this would be a firewall issue, but I've poured over this Sonicwall and all the routing looks correct to me. I've even confirmed with the ISP that the IP is routed correctly on their end.

Is there any TCP setting on the i that would be related to a public IP address? I've gone through the CFGTCP options and all I see is the local IP and domain referenced. (I'm able to connect to my desktop remotely via TeamViewer)


Bob Cagle
IT Manager
Lynk, Inc.

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page