Well, previously https://michaelellerbeck.com/2009/11/30/so-you-bought-an-equallogic-san-now-what-part-two/

I would use the venerable rinetd to handle portforwarding on windows. But alas, along comes server 2008 R2 and it doesn’t working anymore (actually I never tested, it might work)

But, Server 2008 R2 has built in functionality for port forwarding (nifty!)

http://www.rickwargo.com/2011/01/08/port-forwarding-port-mapping-on-windows-server-2008-r2/

So I just gave it a

netsh interface portproxy add v4tov4 listenport=25 listenaddress=10.10.50.51 connectport=25 connectaddress=192.168.1.1

Now I point the equallogic to 10.10.50.51 (an address reachable on the san network) (It requires two nics on the ‘bridge’ server of course one on each network)

And now I can get the email alerts out! Nifty