While I don't have a SonicWall, it seems to me that any stateful inspection firewall would automatically remap the port outbound for the same connection, thereby maintaining the "state" of the connection.
Correct. In fact, it *must* automatically re-map the port outbound. Why? Let's take a look at a sample connection:
Source IP: 192.0.2.25 Source port: 2485 Dest IP: 192.0.2.100 Dest port: 587
This is a typical case -- the source port is random. So if you can't just tell the SonicWall to send requests to port 587 on IP X to port 25 on IP X, you would need to also let it know to send requests from port 587 on IP X to port 2485 on IP 192.0.2.25. It would be impossible to do that (you would literally need billions of entries for it to work).
So I'm guessing that either the SonicWall support people were clueless, or something was lost in the translation.
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000.
Declude Virus: Ultra reliable virus detection and the leader in mailserver vulnerability detection.
Find out what you've been missing: Ask for a free 30-day evaluation.
---- This outgoing message is guaranteed to be authentic by Message Level users. Guarantee the authenticity of your email @ http://www.messagelevel.com. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
