Help with routing in windows 2000 server or 2003 server

jetlee

Senior Member
Joined
Oct 31, 2006
Messages
909
Reaction score
225
Location
The Mother City
Please could someone point me to a post that maybe answers this, I have looked for about 3 days now and still am no closer to a solution.

In Linux it seems possible to add a static route using the route add command and a connection name. It appears that in windows the gateway needs to be an IP address.

I have a windows 2000 server set up with NAT and routing, I can use the NAT to give my LAN users access to the internet via a single ADSL account, but the ADSL router on the network isnt capable of Half Bridge mode. I have managed to create 2 concurrent dial on demand ADSL connections (1 int and 1 local) and either works fine, but I cant seem to set up the routing table to specify which connections should be used for which traffic..

I have a list of local routes which I can convert to a windows script or batch file, but need to know what command I can use to add a route using a connection as the target ..

Thanks for your help
 
Solved

Hi Guys thanks for the input .. have managed to successfully set up 2 concurrent ADSL connections (local and int) on a windows 2000 SP4 server and a standard (non half bridge capable) netgear dg834 router ...

For those interested a short description will follow .. will post a full solution should this be requested.

- Windows 2000 server setup RRAS (Routing and remote access Server)
- install RASPPOE protocol
- Configure a LAN adapter to allow dial on demad connections (ports - properties)
- create 2 dial on demand connections (1 x local 1 x int)
- Setup default static route for Int connection (ip 0.0.0.0 mask 0.0.0.0 metric 2 no gateway)
- setup NAT to allow standard NAT across LAN to Dial on demand
- load all local static routes via batch file

for those interested . the command to load a static route using an interface name via the command line looks as follows:

netsh routing ip add persistentroute dest=32.107.9.0 mask=255.255.255.0 name="Local" metric=1

Still waiting to see what happens overnight .. but I'm sure the "persistent connection" in the dial on demand setup should take care of all the updates ...
 
Top
Sign up to the MyBroadband newsletter
X