Well I know both possibilities #1 and #4 aren't the issue - I had a Sonicwall tech check the settings himself.
I will try the tracert from my home machine to one of the non-functioning IPs.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Bipes
Sent: Monday, March 10, 2014 2:25 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: New public IP address not working
Bob,
Run a tracert from outside the new network and see where the trace starts to fail. You IP address / mask is correct for your firewall.
1. your old NAT translations are still active on your firewall 2. your ISP screwed up their subnet on the on premise router 3. your ISP screwed up the sub netting on the there router 4. Your sonic firewall allow rules were not updated for the new outside IP addresses.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
_____________________________
This is the info I got from the ISP:
Public IP network is xx.xx.xx.208 mask 255.255.255.248
Gateway IP xx.xx.xx.209
Usable range xx.xx.xx.210 - .214
So I set the main interface of my Sonicwall to be .210 with a mask of 255.255.255.248. Maybe that's what's wrong? I need to read up on IP addressing schemes...
.211 is still the only IP getting through - and the ISP is still assuring me that everything is working fine on their end.
Thanks
Bob
--
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,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
