See my other answer for handling the Local LAN traffic. The issue is then how to handle the Internet traffic. Problem is when you have the two different web sites on the same machine serviced by two different routers.
If that traffic is coming from a wide variety of addresses, a static route table solution won't work.
What I've come up with (but haven't completed the testing) involves the use of content-based routing facility in the routers. I'm testing using a couple of very low end Cisco 87x units, where we'll let the routers sort out the traffic to the correct ISP.
Here is the setup:
Router 1: NATs public traffic to 192.168.1.x subnet and 1.x web site
Router 2: NATs public traffic to 192.168.3.x subnet and 3.x web site
Router 1 and 2 are connected together through a 192.168.4.x address for inter-router traffic.
Set up the Win2K gateway to one of the two routers (lets use 1.x for this example). Now, all external addressed traffic will be routed to that router.
Use content-based routing command to examine the "source address" of the outbound traffic on the 1.x router. The source address is the address of the web server that handled the original request to the web server. It will be either from the 1.x subnet or the 2.x subnet). Set the next hop address in the content-based routing rule depending on the source. If the source is from the 1.x subnet, set the next hop to the 1.x routers normal gateway. If the source is from the 2.x address, set the next hop address to the dedicated inter-router 4.x address of the 2.x router. The packets for that ISP will have to transit the 1.x router first, but will go out through the 2.x router. On outbound traffic, NAT address translation is handled after the content based routing in the Cisco stack, so the NAT should work just fine.
I'm still experimenting with this (as well as Win2003 server Network Load Balancing). I think it might work for you, though.