Adding static routes

[Biggs]

NIC 1 is connected to ISP 1 via router 1 and is using IP 1 - default gateway

NIC 2 is connected to ISP 2 via router 2 and is using IP 2 - FTP server


For NIC 2,

1) Where should the static routes be added -- in the server's OS (Win2K) or in router 2?

2) What specific routes should be added if the purpose is exclusively an FTP server?

 

[Biggs]

Bump!

 

[Garion]

Unfortunately, it doesn't work that way. The only thing you could do would be to pick a "block" of IP addresses and route them to ISP2 and leave ISP1 as your default gateway (or vice versa, of course). You can't specify, by application, which NIC to use.

- G

 

[ColdZero]

Why not just bind the FTP server app to the IP address of the 2nd NIC?

 

[Dravic]

if at all possible

put router 1 and 2 on the same switch
then add the static routes to each router table, and let the routers due what they due.. route

for instance

ftp server x.x.x.1
default gateway y.y.y.1

router 1 192.168.0.1
router 2 192.168.0.2

in router 1
0.0.0.0 -> y.y.y.1 (for anything not listed send all default traffic to the gateway)
x.x.x.1 -> 192.168.0.2 (to get to the ftp server send all packets to router 2)

in router2
0.0.0.0 -> 192.168.0.1 (for anything not listed send all default traffic to router1)
x.x.x.1 -> ? (what ever network you use to get to the ftp server)


Any PC on the network can then use the config, and not just that one dual nic PC
And just incase anyone added router 2 as their default gateway, it will still know how to route the data correctly.