Routing

Hello,
Is there a way to configure a desktop PC (Windows XP SP3 (let’s say
192.168.1.10)) that is on one subnet (192.168.1.xxx) to route directly to
another subnet (192.168.2.xxx)? The subnet 192.168.1.xxx has a W2K3 R2
server (currently configured as a domain controller and file server (let’s
say 192.168.1.2)) and a Cisco Router ((let’s say 192.168.1.1) which routes to
192.168.2.xxx). I do not want the desktop PC (not all PCs on the subnet) to
have access to the local subnet resources, except as needed to access the
other subnet. Once they get to the other subnet, I do not want that PC to
have access to those subnet resources except for a VPN router (let’s say
192.168.2.1) that is connected to a remote ISA server.
If I cannot configure the PC, is it possible to configure the W2K3 R2 server
as a Router for just that PC?
I am sure there is a paper on how to configure that on the TechNet support
site, I just can’t find it.
Any Help would be appreciated.

XP is not design to be a router. I would setup windows 2003 as router. If
you want to try XP, you may enable ip routing. These links may help.
Routing how to
How to disable ip routing/forwarding on a W2K Pro? ... For example,
the Generic Routing Encapsulation (GRE) IP protocol (protocol number 47) is
added to the ...
www.howtonetworking.com/Networking/routing.htm


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"JCLSB" <(E-Mail Removed)> wrote in message
news:3ACB0472-F0B8-42F6-863D-(E-Mail Removed)...
> Hello,
> Is there a way to configure a desktop PC (Windows XP SP3 (let’s say
> 192.168.1.10)) that is on one subnet (192.168.1.xxx) to route directly to
> another subnet (192.168.2.xxx)? The subnet 192.168.1.xxx has a W2K3 R2
> server (currently configured as a domain controller and file server (let’s
> say 192.168.1.2)) and a Cisco Router ((let’s say 192.168.1.1) which routes
> to
> 192.168.2.xxx). I do not want the desktop PC (not all PCs on the subnet)
> to
> have access to the local subnet resources, except as needed to access the
> other subnet. Once they get to the other subnet, I do not want that PC to
> have access to those subnet resources except for a VPN router (let’s say
> 192.168.2.1) that is connected to a remote ISA server.
> If I cannot configure the PC, is it possible to configure the W2K3 R2
> server
> as a Router for just that PC?
> I am sure there is a paper on how to configure that on the TechNet support
> site, I just can’t find it.
> Any Help would be appreciated.
>

"JCLSB" <(E-Mail Removed)> wrote in message
news:3ACB0472-F0B8-42F6-863D-(E-Mail Removed)...
> Hello,
> Is there a way to configure a desktop PC (Windows XP SP3 (let’s say
> 192.168.1.10)) that is on one subnet (192.168.1.xxx) to route directly to
> another subnet (192.168.2.xxx)? The subnet 192.168.1.xxx has a W2K3 R2
> server (currently configured as a domain controller and file server (let’s
> say 192.168.1.2)) and a Cisco Router ((let’s say 192.168.1.1) which routes
> to
> 192.168.2.xxx). I do not want the desktop PC (not all PCs on the subnet)
> to
> have access to the local subnet resources, except as needed to access the
> other subnet. Once they get to the other subnet, I do not want that PC to
> have access to those subnet resources except for a VPN router (let’s say
> 192.168.2.1) that is connected to a remote ISA server.
> If I cannot configure the PC, is it possible to configure the W2K3 R2
> server
> as a Router for just that PC?
> I am sure there is a paper on how to configure that on the TechNet support
> site, I just can’t find it.
> Any Help would be appreciated.
>

What exactly are you trying to do here? Are you trying to set up a
machine in one subnet but make it seem to be in another? If so, why?

If you don't want the machine it see any machines or services running in
192.168.1.0/24, why connect it to that network at all. Routers route between
subnets, they do not route between machines.

In news:(E-Mail Removed),
Bill Grant <not.available@online> typed:
>
> What exactly are you trying to do here? Are you trying to set up a
> machine in one subnet but make it seem to be in another? If so, why?
>
> If you don't want the machine it see any machines or services
> running in 192.168.1.0/24, why connect it to that network at all.
> Routers route between subnets, they do not route between machines.

Agreed. He can also probably simply identify the port the machine is on and
instead of it plugged into the switch for that subnet, plug it into a switch
for the other subnet he wants it on. If the subnet is elsewhere, but withing
the building, and the switch supports it, run a direct wire to the other
subnet on one port of the switch and plug the machine into another port and
configure a VLAN between those two ports. If the subnet is in another
location, well, that's a whole other story and may as well just keep the
machine on the main subnet and use the infrastructure's routing to the other
location.

Ace