Tricky routing with XP Pro?

L

LifeBoy

I have read a number of articles by now regarding routing and Windows
XP. I have enabled ip routing in the registry and also start routing &
remote access services. Here's my scenario:

1. A corporate network (of which I'm the admin) with static and DCHP
clients
2. One specific machine used by a developer has two NIC's, NIC1
connects to the network, the other connects via crossover cable to his
notebook as below:

notebook <----> [nic1 --- DEV MACHINE --- nic2] <-----> corporate
network.

The reason for this setup is that he does large transfers between his
notebook and desktop via a gigabit link and the direct link does a
great job. But now he needs to access the rest of the network via this
setup as well. (No, we can't replace the OS with something else,
basically we need to get XP routing going).

The addresses are as follows:

notebook: 192.168.110.2 def gateway: 192.168.110.1

nic1: 192.168.110.1 no def gateway

nic2: 192.168.100.60 def gateway: 192.168.100.1 (which is our firewall
LAN port)

I pressume that I should add some static routes, but where and how? I
understand that this is not that simple, since there is a route to be
added to each machine on the LAN, right? I can do that with policies
(or possibly DHCP?), but exactly which routes and where. I did a lot
of this kind of stuff a few years back, so I have a basic understanding
of routing, but the details now have me scratching my head.

All help much appreciated.
 
G

Guest

A good place to start would be using your command line.

Start > Run> command <press enter> or ok

type route ...this will list the commands on how to set up a static route
for your computers to travel.

hopefully this helps
 
L

LifeBoy

Marbles said:
A good place to start would be using your command line.

Start > Run> command <press enter> or ok
Click to expand...
:) I live on the command line! (First house on the left)
type route ...this will list the commands on how to set up a static route
for your computers to travel.
Click to expand...
Jokes aside, I have been there, but as I said, I'm a bit rusty and am
hoping for some real advice on how to set up the routes so that this
will work.
 
G

Guest

That was real advice... oh well ...lol

You say you want to set routes..thats the place to do it. Not unless your
looking for registry tweaks or a 3rd party program ?

If your rusty, you should get an upgrade to replace those parts

...good luck
 
S

Steve Winograd [MVP]

I have read a number of articles by now regarding routing and Windows
XP. I have enabled ip routing in the registry and also start routing &
remote access services. Here's my scenario:

1. A corporate network (of which I'm the admin) with static and DCHP
clients
2. One specific machine used by a developer has two NIC's, NIC1
connects to the network, the other connects via crossover cable to his
notebook as below:

notebook <----> [nic1 --- DEV MACHINE --- nic2] <-----> corporate
network.

The reason for this setup is that he does large transfers between his
notebook and desktop via a gigabit link and the direct link does a
great job. But now he needs to access the rest of the network via this
setup as well. (No, we can't replace the OS with something else,
basically we need to get XP routing going).

The addresses are as follows:

notebook: 192.168.110.2 def gateway: 192.168.110.1

nic1: 192.168.110.1 no def gateway

nic2: 192.168.100.60 def gateway: 192.168.100.1 (which is our firewall
LAN port)

I pressume that I should add some static routes, but where and how? I
understand that this is not that simple, since there is a route to be
added to each machine on the LAN, right? I can do that with policies
(or possibly DHCP?), but exactly which routes and where. I did a lot
of this kind of stuff a few years back, so I have a basic understanding
of routing, but the details now have me scratching my head.

All help much appreciated.
Click to expand...

If I understand your question:

1. The developer already has access to the rest of the network on DEV
MACHINE via NIC2.

2. He now needs to access the rest of the network from the notebook
computer. You want to know how to do that by using DEV MACHINE as a
router for the notebook computer.

Is that right? If not, please explain the situation.

Here are two possible solutions that don't require creating routes or
making any changes on the other LAN machines:

=============================
Solution 1
=============================
1. Disable IP routing on DEV MACHINE.

2. Add a second NIC (USB or CardBus) to the notebook computer and
connect it to the corporate network. It will get a 192.168.100.x
address for access to the rest of the network.

3. When the developer wants to transfer files over the high-speed link
between his computers, have him access the other computer using the IP
address of its high-speed link, not using its computer name. For
example, to access DEV MACHINE from the notebook using the high-speed
link, type this in the Start > Run box on the notebook:

\\192.168.110.1

=============================
Solution 2
=============================
1. Disable IP routing on DEV MACHINE.

2. Enable Internet Connection Sharing on DEV MACHINE's NIC2
connection. If it asks what to use for the home network connection,
tell it to use the high-speed link.

3. If he needs to access other LAN computers from the notebook, create
an LMHOSTS file in %SystemRoot%\System32\Drivers\Etc on the notebook
that specifies the names and static IP addresses of those computers.
Examples of entries in the file are:

192.168.100.111 computer1
192.168.100.222 computer2
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
L

LifeBoy

Steve said:
If I understand your question:

1. The developer already has access to the rest of the network on DEV
MACHINE via NIC2. Correct

2. He now needs to access the rest of the network from the notebook
computer. You want to know how to do that by using DEV MACHINE as a
router for the notebook computer.
Click to expand...
Correct again.
Here are two possible solutions that don't require creating routes or
making any changes on the other LAN machines:

=============================
Solution 1
=============================
Click to expand...
He does use a wifi link to access the corporate network, however, I
would like to learn how to do this by using XP as a router. This is a
scenario that I have often encountered and I would like to get a
solution for more than just this specific case.
1. Disable IP routing on DEV MACHINE.

2. Add a second NIC (USB or CardBus) to the notebook computer and
connect it to the corporate network. It will get a 192.168.100.x
address for access to the rest of the network.
Click to expand...
=============================
Solution 2
=============================
1. Disable IP routing on DEV MACHINE.

2. Enable Internet Connection Sharing on DEV MACHINE's NIC2
connection. If it asks what to use for the home network connection,
tell it to use the high-speed link.
Click to expand...
This is a problem, since the corporate network policy enforced by the
domain does not allow ICS to be turned on on the DEV machine or
anywhere else for that matter. Since DHCP is in use on the network, it
would create chaos with clients not getting addresses from the correct
DHCP server.

So, although this may be a workaround in certain situations, it doesn't
solve the problem on how to set up XP as a full network to network
router.

(BTW. I have seen numerous articles and posting that refer to the
routing of subnets, when in fact the do not use subnets (ie they use
netmasks like 255.255.255.0 which is not a subnet, but a full network)
 
S

Steve Winograd [MVP]

Correct again.

He does use a wifi link to access the corporate network, however, I
would like to learn how to do this by using XP as a router. This is a
scenario that I have often encountered and I would like to get a
solution for more than just this specific case.



This is a problem, since the corporate network policy enforced by the
domain does not allow ICS to be turned on on the DEV machine or
anywhere else for that matter. Since DHCP is in use on the network, it
would create chaos with clients not getting addresses from the correct
DHCP server.

So, although this may be a workaround in certain situations, it doesn't
solve the problem on how to set up XP as a full network to network
router.

(BTW. I have seen numerous articles and posting that refer to the
routing of subnets, when in fact the do not use subnets (ie they use
netmasks like 255.255.255.0 which is not a subnet, but a full network)
Click to expand...

I understand the reason for the no-ICS policy and the need to prevent
unauthorized DHCP servers on the corporate network. However, enabling
ICS on the DEV machine in the way that I suggested would enable a DHCP
server only on the developer's private two-computer high-speed
network. It wouldn't enable a DHCP server on the corporate network,
and it wouldn't create chaos.

Since your network is set up as a domain, I recommend working with the
network administrators to see if, and how, you goal can be
accomplished without disrupting the network. In general terms, the
DEV's desktop computer must route traffic between its two network
interfaces, and the other LAN computers must have a static route
defined to send traffic to the notebook's high-speed link via the
desktop computer. If the desktop computer's IP addresses are
192.168.110.1 (high-speed) and 192.168.100.60 (LAN), those routes
would specify that traffic for the 192.168.110.0/24 subnet goes
through the interface 192.168.100.60. A command line for that is:

route add 192.168.110.0 mask 255.255.255.0 192.168.100.60

I'm sorry, but I don't know what you mean when you say that
255.255.255.0 is a full network, not a subnet. 255.255.255.0 is a
subnet mask. The logical AND of a network interface's subnet mask and
its IP address defines a subnet. For an interface with an IP address
of 192.168.100.1 and a subnet mask of 255.255.255.0 (sometimes written
as 192.168.100.0/24), the subnet consists of IP addresses
192.168.100.1 through 192.168.100.254. That interface can reach
computers with those IP addresses directly. Any other IP address is
in a different subnet, and access to such an address has to be routed
through the default gateway to a router with connections to multiple
subnets.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Win XP routing tables problem 2
ICS with 3 NIC in P2P mode 1
Windows XP & Dynamic Routing Problem 1
windows routing problem 3
Newbie simple LAN routing problem 2
Multihomed connectivity issue 1
Different Private IP's on the Same Subnet 11
IP Routing Tables 4

Top