We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Route Command Problems WIN2K Server

hexfusion
hexfusion asked
on
Medium Priority
653 Views
Last Modified: 2010-04-13
Ok I have the following setup

Router 1

eth0 192.229.13.78
eth1 192.229.23.33
subnet 255.255.255.224
eth1:1 192.229.23.65
subnet 255.255.255.224

My windows server has 1 nic and I am trying to have IP's from both pools work for the server.  If you look at the routing table below my IP's in the new pool have the wrong gateway.  All the IP's share the same netmask which should be 255.255.255.224.

IP's .53-.58 need to connect to gateway 192.229.23.33 and subnet 255.255.255.224
IP's .66-.75 must connect gateway 192.229.23.65 and subnet 255.255.255.224

I cannot get ROUTE change to work for me how can I adjust the following table to my specs using route change

I can't bother the IP's .53-.58 as they are in use.

Thanks in advance for your time and consideration

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 60 08 5a 3b 71 ...... 3Com 3C90x Ethernet Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0     24.229.23.33    24.229.23.53       1
     24.229.23.32  255.255.255.224     24.229.23.53    24.229.23.53       1
     24.229.23.53  255.255.255.255        127.0.0.1       127.0.0.1       1
     24.229.23.54  255.255.255.255        127.0.0.1       127.0.0.1       1
     24.229.23.55  255.255.255.255        127.0.0.1       127.0.0.1       1
     24.229.23.56  255.255.255.255        127.0.0.1       127.0.0.1       1
     24.229.23.57  255.255.255.255        127.0.0.1       127.0.0.1       1
     24.229.23.58  255.255.255.255        127.0.0.1       127.0.0.1       1
     24.229.23.64  255.255.255.224     24.229.23.66    24.229.23.53       1
     24.229.23.66  255.255.255.255        127.0.0.1       127.0.0.1       1
     24.229.23.67  255.255.255.255        127.0.0.1       127.0.0.1       1
     24.229.23.68  255.255.255.255        127.0.0.1       127.0.0.1       1
     24.229.23.69  255.255.255.255        127.0.0.1       127.0.0.1       1
     24.229.23.70  255.255.255.255        127.0.0.1       127.0.0.1       1
     24.229.23.71  255.255.255.255        127.0.0.1       127.0.0.1       1
     24.229.23.72  255.255.255.255        127.0.0.1       127.0.0.1       1
     24.229.23.73  255.255.255.255        127.0.0.1       127.0.0.1       1
     24.229.23.74  255.255.255.255        127.0.0.1       127.0.0.1       1
     24.229.23.75  255.255.255.255        127.0.0.1       127.0.0.1       1
   24.255.255.255  255.255.255.255     24.229.23.53    24.229.23.53       1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
        224.0.0.0        224.0.0.0     24.229.23.53    24.229.23.53       1
  255.255.255.255  255.255.255.255     24.229.23.53    24.229.23.53       1
Default Gateway:      24.229.23.33
===========================================================================
Persistent Routes: NONE

Comment
Watch Question

Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
This ended up not being my problem but you were 100% correct and i will award you the points.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.