not recommended. If you truly have 10 NICs on the server, better off buying a consumer level switch for around $75 USD and getting the server to a maximum of 2 NICs.
on the other problem,
if your not getting to the internet, and are running an active directory environment, then the DNS server isn't forwarding queries to root hint servers or your ISP DNS servers therefore the web query goes unanswered thus no web page is display [404 or 403]. This is probably happening because the server doesn't know where to send DNS queries it can't answer. Usually it will send those queries to the default gateway specified in the NIC properties.
so a simple diagram for inbou nd traffice would be
internet [ISP] >>>>>>> WAN interface on perimeter router/firewall >>>>LAN interface [gateway]on perimeter router/firewall>>>>>>>>>>external NIC on Server >>>>>> internal NIC on Server >>>>>> switch >>>>> workstations
and just change the arrows to show outbound traffic.
From your ISP to your perimeter router WAN interface is it's own subnet using addressing, mask and DNS server addresses provided by your ISP. The perimeter router/firewall to the external interface on the server is one subnet using your ISP DNS servers in the NIC properties and using your router subnet addressing and mask. the internal interface on the server is it's own subnet using your Active Directory DNS server address in the NIC properties page as well as all workstations [DHCP can handle this for you].
This type of setup should allow workstations to get to the internet and allow the server to have internet connectivity.
Note: enable firewalls on the server and all workstations.