Ok, about this forwarding, If I declare some IP's on the PC behind the gateway that are neither virtual nor the fixed ones the ISP gave me, will the routing be possible - can a user see my index.html.
This webserver I place behind the GWay PC if all of the files-pages are on it, browsing the site hosted there should be no problem, but if the pages are across several computers will the browsing work, and what will be displayed (which IP) in the users internet browser.
(this with static IP i got from my ISP and with virtual-automatic IPs behind the GWay PC - will it work)
the visible IP will be the gateway's IP, the static IP your ISP gave you. The internal IP's should be non-routable i.e. 192.168.x.x or 10.x.x.x networks. This helps protect the machines. If the pages are mirrored across the network on several other machines, you could set up load-balancing on the gateway, which would average out all the requests so each machine is hit minimally. However, each request requires a lot of synchronization. If you seperate the machines, you'll need synchronization still, however, it's a little less complicated. The forwarding can be done on the main web server, via proxy like caching, or through the gateway.