If you've changed carriers, & you haven't changed the IP settings for the inside of the router (& the outside of the SonicWall), then its a routing issue, since your new carrier won't be routing traffic back to you for 10.11.11.x addresses, since this subnet belongs to the previous carrier. Please confirm if you've changed the IP scheme on the router's inside interface & SonicWall's outside interface to reflect the new block of public IPs you've been assigned by your new ISP.
Please post your entire "sanitized" config (passwords removed, public IPs masked out like so: x.x.x.2).
>The odd thing I don't know how works is that all the 10.?.?.? were public addresses.
This is common practice, when you have a border router with a firewall behind it. And the use of public IPs on the inside of the router & the outside of the firewall gives you a simpler NAT setup: the firewall will NAT traffic for the internal 192.168.0.x subnet, & NAT is unnecessary on the router, since you have public IPs on both the inside & outside interfaces.
cheers
Main Topics
Browse All Topics
by: robinluoPosted on 2005-12-01 at 18:04:43ID: 15401990
If your web server ever worked before, the only explaination would be your previous Telco was doing NAT for you.
Your current Telco maybe only NATting 10.0.0.0/8 for you, not the 192.168.0.0/16. That's why you can PING to WWW from router (10.0.0.0/8), but not from your LAN (192.168.0.0/16). You can add NAT on Sonicwall and translate 192.168.0.0 to 10.0.0.0.
Call your service provider and they may have answer for your question.