Release of isa + vro and Intranet servers

The release of the isa + router and Intranet server requires that the Intranet host can access the Internet and publish www, ftp, and exchange server on isa! (Questions given by the instructor during training) www.2cto.com I thought of two solutions: 1. Add an ip nat port-to-port ing on the router! Ip nat inside source static tcp 192.168..2 .2 80 172.16.201.2 80 ip nat inside source static tcp 192.168.201.2 21 172.16.201.2 21 ip nat inside source static tcp 192.168.201.2 25 172.16.201.2 25 then published www and ftp server on ISA release the 172 address! This is a success, and it is also possible on the Internet! 2. The second method is to add a static route on isa to point to the 192 CIDR block. (This is the solution provided by the instructor). You can use route add 192.168.201.0 mask 255.255.255.0 172.16.201.2 or use RRAS in windows server 2003 at a command prompt! Then add the 192 CIDR block to the internal network of isa! The effects of www.2cto.com are the same. I think the first solution is better, because nat on the router will make the configuration of isa simpler and more stable. Because too many configurations on isa may affect the performance and stability of isa, it is also difficult to estimate troubleshooting in the future! But my teacher told me that the second one is better, because the first one may make the router a bottleneck!