Port forwarding

You don't have to have port fowarding for access to the internet through the SMC Barricade [unless you are hosting your own web server]. If you are hosting your own web server, make sure your ISP hasn't blocked port 80 [a lot of them have due to worm programs. If your ISP blocks port 80, you'll have to configure IIS web server to listen on a port other than port 80 [say 8080]. You would configure your internal web server to listen on the IIS external interface port 8080 and configure the SMC Barricade to foward inbound port 80 traffic to port 8080. [note default web addresses {www.domain-name.com] assumes port 80. In other words someone who types the domain name http://www.domain-name.com is really typing a IP address like http://192.168.2.1:80 . when that gets to your router, the router will foward that inbound request on port 80 to port 8080. Outbound [back to the requestor] will be through port 8080 [which bypasses the port 80 block the ISP has].

The SMC Barricade Router is a pain to configure [I had the 7004ABR and switched to the Linksys BEFSX41. Much easier to configure and their help files are far better than SMC].

However, if you have configured your Barricade to obtain your IP dynamically, and are using the Barricade DHCP for client IP address assignment, IE LAN settings need to be configured with ALL boxes unchecked. Open IE and click stop. Click tools, intenet options, connections, LAN settings. Uncheck all boxes for Obtain IP address automatically and uncheck the box for DNS servers.
If you are not using the barricade DHCP service, then you need to specify a IP address [something like 192.168.16.1], submask [something like 255.255.255.0 and use the Barricade IP address [default is 192.168.2.1] as your gateway address. Your ISP can provide you with their Name Server addresses.

You might have to reboot for these changes to take place.

Traffic out should be no problem. If I understand, you want folks from the outside world to be able to access servers behind the firewall. This is often referred to as setting up a "virtual server" -- incoming traffic for various ports is re-directed to specific servers in your protected network.

The limitation is that you probably only have one public IP address from your ISP/cable company. Although the servers on your network all have different IP addresses, there's only one IP address that's visible to the internet.

So, the dilemma you predicted comes true; having two servers listening to port 80 means having to pick your favorite to make "visible" to the internet. The other option is to change the port one of the servers is lestening on (webaccess is probably the wiser choice)

HTH