Point 1
When in server/gateway mode E-Smith blocks all inbound traffic. You can install port forwarding from your VPN connections to your internal network by installing the port forwarding rpm. You can find it and the instructions here
http://myezserver.com/docs/mitel/ipportfw-howto.html . All you will need to know is what port you are coming in on and open the port up to be forwarded to your internal network.
If this is not suitable then you could change your E-Smith server to standalone. But remember that your system is then wide open ie: if you don't run a really good firewall you could easily be hacked.
Once you have a VPN connection to your router you then have full access to whatever you have on your internal network. But E-Smith is blocking it. IF I wanted to get access to say a Metaframe server behind the e-smith box I could make my VPN connection to my router then load up my Citrix Client to talk to the outside NIC then the ipchains port forward rules kick in, I may have an entry that sends all requests from port 1409 through to an internal address of 192.168.1.1. Port 1409 is what Citrix Metaframe client uses to connect to a server and my Citrix server for example is 192.168.1.1
I hope this makes sense but you really must always stick to the side of security first. If you are satisfied that your 1720 is firewalled and protected with enough rules blocking every kind of sync, xmas, ports scans etc that are around then run the server in stand alone mode.
Point 2
Yes, basically you can get your 1720 to ignore the Nimda signature and blocks its attempts to penetrate your network and screw your IIS servers.
If you need anymore advice please let me know.
Regards
Craig Farrier