• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 469
  • Last Modified:

Route traffic to a specific interface in XP

I have looked and I cannot find a simple answer to this question...If there is one.  I have a Windows XP SP 2 laptop with both a wired and wireless network connection.  The Wired connection goes to a corporate lan with all sorts of restrictions and rules - AS IT SHOULD.  The wireless is a direct connection to a test LAB.  My intention is not to bridge these connections, but rather to route remote desktop traffic to the WIreless connection so that I can work on TEST servers that are outside of the corporate environment.

Here is a "ROUTE PRINT" display:

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 08 02 b9 bb d4 ...... Intel(R) PRO/100 VE Network Connection - Determi
nistic Network Enhancer Miniport
0x40004 ...00 0b cd 8e 3b a4 ...... Compaq WLAN MultiPort W200 - Deterministic N
etwork Enhancer Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0    10.164.81.254    10.164.81.72       1
          0.0.0.0          0.0.0.0      192.168.0.1   192.168.0.118       2
      10.164.81.0    255.255.255.0     10.164.81.72    10.164.81.72       1
     10.164.81.72  255.255.255.255        127.0.0.1       127.0.0.1       1
   10.255.255.255  255.255.255.255     10.164.81.72    10.164.81.72       1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
      192.168.0.0    255.255.255.0    192.168.0.118   192.168.0.118       2
    192.168.0.118  255.255.255.255        127.0.0.1       127.0.0.1       2
    192.168.0.255  255.255.255.255    192.168.0.118   192.168.0.118       2
        224.0.0.0        240.0.0.0     10.164.81.72    10.164.81.72       1
        224.0.0.0        240.0.0.0    192.168.0.118   192.168.0.118       2
  255.255.255.255  255.255.255.255     10.164.81.72    10.164.81.72       1
  255.255.255.255  255.255.255.255    192.168.0.118   192.168.0.118       1
Default Gateway:     10.164.81.254
===========================================================================
Persistent Routes:
  None

I have changed the Interface Metric on both cards trying to make this work, but I can easily change it back.  I tried adding a statement like:

ROUTE ADD x.x.x.10 192.168.0.118

to the route table in an attempt to get the  traffic to flow. But no success.  So I am stumped.  Any help out there?  My only other alternative is to keep enabling / disabling the wired network which will defeat part of the purpose.

Thanks!
0
Wyant Niswonger
Asked:
Wyant Niswonger
  • 2
1 Solution
 
Rob WilliamsCommented:
If the wired and wireless networks are on different subnets, as they should be and appear to be, you shouldn't need any routing statements. Any device on the 10.164.81.0 network would be routed through the 10.164.81.72 device and 192.168.0.0 through the 192.168.0.118 device. Name resolution might be another issue, but if you can connect using IP's you should be fine.
0
 
Wyant NiswongerPresidentAuthor Commented:
I am going to accept the answer, becuase I did a newbie thing here.  I didn't check to make sure that the server on the other end was up and running (it was not).  You are correct that name resolution is not working.  The reason for the route statements is that there is another router between the wireless and the test lab so that people from other parts of the country can get to the test lab.

Sometimes it helps to just write things down.  

Best Regards:

Wyant
0
 
Rob WilliamsCommented:
Thanks Wyant. Good luck with it.
--Rob
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now