• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 741
  • Last Modified:

Need to forward secondary IP address to private address on SonicWall w/SonicPoints

First, a little background.  I have a new SonicWall TZ-215 and four SonicPoints.  The SonicPoints are connected to a Dell PowerConnect 3548P where they get their Power-Over-Ethernet.  It was my understanding that the SonicPoints would 'find' the TZ firewall and provision themselves.  After several hours and failed attempts at getting this to work, I found this web page which had the answer (http://briandagan.com/fix-configuring-sonicpoint-aps-on-a-sonicwall).  Apparently, if the SonicPoints aren't directly plugged into the SonicWall, they won't be seen by the SonicWall without the workaround above.  The workaround connects the PowerConnect switch (which the SonicPoints are connected to) to the X2 and then bridges the X2 interface to X0 (the LAN interface).  The SonicPoints found the firewall and provisioned themselves just fine.

What does this have to do with forwarding a secondary IP address?  I don't know.  Maybe nothing, but I can't seem to get it to work.  I have 5 public addresses for a multi-tenant building.  The HVAC (Heating and AC) company cannot configure the listening port on their web-based system from port 80 to something else.  We've decided to use a second public IP address and forward port 80 straight to their equipment (still on port 80).  I've used the Pubic Server Wizard and it looks like it did everything it was supposed to do.  I confirmed this by visually verifying what I see in the firewall configuration with the information from this link http://www.experts-exchange.com/Hardware/Networking_Hardware/Firewalls/Q_25016206.html

I've turn Packet Monitoring on and filtered on the 2nd pubic address.  I can see in Packet Monitor that the external public address is being forwarded to the correct internal private IP address (FORWARDED) and using port 80.  When I try to http from an external browser to the 2nd public IP address, it fails.  Accessing the HVAC system from inside the building works fine.

I can't help but think that the 'workaround' for SonicPoints has created this issue.  One reason is because the Public Server Wizard is wanting to direct traffic to the WLAN zone instead of the LAN zone (as configured from the link above).  Once the rule is created, I can't edit it to LAN.  I've tried changing the NAT policy from WLAN to LAN, but that didn't seem to do anything.  I'm pretty desperate to get this work because the grand opening of the building is tomorrow and this has to work.  Any help would be appreciated.
  • 3
1 Solution
lrbarriosAuthor Commented:
UPDATE: I just looked at Packet Monitor again and can see that the internal IP address is responding back to my public IP address here at the home.
	--	X2*	9x.94.2x0.xx	IP	TCP	52074,80	FORWARDED	78[78]
	X2*(i)	X1	9x.94.2x0.xx	IP	TCP	80,52074	FORWARDED	60[60]

Open in new window

So what's the problem?  Is it the X2 interface which is bridged to X0?
lrbarriosAuthor Commented:
Turns out that the links I included above worked as advertised.  When I got onsite, I found that I couldn't connect to the HVAC equipment locally via HTTP.  Firefox kept saying 'Connection reset by server' and Internet Explorer just said 'Cannot display this webpage'.  The internal IP address was responding to ping, however.  I asked the HVAC tech to reset their server box.  After it came back up, everything worked fine.  The HVAC equipment could be accessed via the Internet.  It comes back to what I always tell my users... "Have you tried rebooting yet?"
lrbarriosAuthor Commented:
I'm glad I tried to access the HVAC device locally before spending who knows how long trying to fix a firewall configuration that wasn't broken.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now