ROUTING WINDOWS 2000 SERVER TO SEND PACKETS TO ANOTHER GATEWAY 2

[EJXPDOCS]

How can I route packets to a different gateway in Windows 2000 Server other than the default gateway. Ex. Below:

Ip - 192.168.1.24
Mask - 255.255.255.0
Default Gateway - 192.168.1.1

I want to route to another gateway for certain packets.

Destination - 192.168.168.222
Use gateway - 192.168.1.2 which is a firewall that knows about 192.168.168.222.

Any suggestions would be much appreciated.

~EJXPDOCS

 

[kbing]

Open command line, type:

route add 192.168.168.0 mask 255.255.255.0 192.168.1.2 -p

That will cause the server to send all packets for the subnet specified to the gateway you wanted.

The other method to do this would be to add the route to the firewall.

 

[EJXPDOCS]

I have tried that exact route statement without any luck.

Also, the firewall already knows to route packets with that IP (192.168.168.0) network destination to the internal LAN.

 

[LawnBoy]

Does

route print

show that new route?

 

[EJXPDOCS]

Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.223 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.223 192.168.1.223 1
192.168.1.223 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.1.255 255.255.255.255 192.168.1.223 192.168.1.223 1
192.168.168.0 255.255.255.0 192.168.1.2 192.168.1.223 1
224.0.0.0 224.0.0.0 192.168.1.223 192.168.1.223 1
255.255.255.255 255.255.255.255 192.168.1.223 192.168.1.223 1
Default Gateway: 192.168.1.1
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
192.168.168.0 255.255.255.0 192.168.1.2 1

 

[LawnBoy]

So it's in the routing table. What test have you performed to see if it works?

 

[EJXPDOCS]

That obviously does not work.

Basically the system is sitting in between 2 firewalls.
It's on the inside of our ISP's firewall and on the outside of our firewall. I did have our ISP add a route stating:

Destination - 192.168.168.0 Mask 255.255.255.0 send to gateway 192.168.1.2 and it worked. However, our VPN was affected by that route. So I had to tell them to axe it.

I have a Linux box in the same situation that works beautifully. Not sure why this Windows 2000 server is giving me problems.

 

[Stevehewitt]

OK, first off there's no need for capitals in the title of your post. Considered shouting.

That obviously does not work.

Yes it should and I don't know why it's "obvious" that it wouldn't.

I needed to route traffic to a particular IP over a seperate gateway for disaster recovery yesterday and used the following:

route add 10.3.3.1 mask 255.255.0.0 10.3.1.2

That will throw any traffic that has a destination of 10.3.3.1 to our leased line router rather than the usual internet gateway router.

May I suggest not coming across as quite so aggressive when posting for more prompt replies - if any at all.

Please see

route /?

And apply the relevant parameters to your particular needs.




Steve.

"They have the internet on computers now!" - Homer Simpson

 

[EJXPDOCS]

Relax. I capitalized everything in the title so that it would stand out. I'm not shouting. Secondly, I am not coming across aggressive, that is just my sense of humor. Try, not to take things soo seriously. You'll live longer.

Anyways, I gave up on the Windows 2000 routing (CRAP).
I just put the server on an opt interface on our firewall and used the firewall to route everything. It worked beautifully.

Thank you for all of your suggestions.

Later,

 

[LawnBoy]

I gave up on the Windows 2000 routing (CRAP).

Lol, been there, done that...

Glad you got it working.

 

[EJXPDOCS]

So am I. Now on to more frustrating, yet rewarding adventures.