well ok, I can't imagine a switch being the real culprit here where you remove the switch and replace it with a hub and volia! SBS 2003 is designed to be a "aLL in one box" network solution for small busienss. It also is designed where the one box [the server] has 2 NICS, LAN and WAN, internal interface and external interface respectively. The internal interface NIC on the server connects to the uplink port on a switch, 4,8,16,24, port, or if you prefer a hub. The External interface NIC would connect to your Modem or if you prefer a routers uplink port [though with ISA server why bother with a router]. ISA server [really a big proxy server & firewall] handles all inbound & outbound trafic. Now all clients have to use ISA server to get out and their browsers have to be configured to use ISA server [proxy]. Further, since IIS is also installed with SBS, you have to configure them to use a port other than port 80, as IIS used port 80 and would conflict with ISA server if it used port 80 as well.
Even more complications is that SBS 2003 creates a default group called Domain Internet users and restricts internet access to this group via Access Policy in ISA server. You have to add users to this group for them to access the internet.
Now, if your ISP has assigned you a static IP address, there is a Wizard you run in SBS to imput that information , including if you use a router between ISA server and the internet. This configures ISA server.
Finally if your subnetting on the LAN using routers for seperating workstations by department, personally I would chuck the routers on the LAN and go with just specifing different scopes for the groups of computers and set those scopes in DNS DHCP AD.