Another update: Well, as of this afternoon, RDP to my server starting working on the .212 address. I'm guessing that there *was* a problem on the ISP side, but they just didn't want to admit it, and only finally found and fixed it after my persistent calls.
So, for now, everything seems to be working how I want. Now I get to try and plug in a video conference camera and assign it one of the last 2 IPs; we'll see how that goes.
Thanks again everyone for their input.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bob Cagle
Sent: Saturday, March 8, 2014 6:10 PM
Subject: New public IP address not working
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)
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l