Re: Routing problem, proprietary equipment

Phillip:

I think that that is way I need to go. Remote users in the 192.168.1.x
subnet need to access the PC but not the device beyond it.

So the device is 192.168.1.35 & the corresponding NIC in the PC is
192.168.1.36. The second NIC in the PC will be 192.168.2.151 and this NIC
will be connected to the local network at the second site with the
192.168.2.x subnet. I will then add the route command to its' table so that
it knows that the device is connected to its one NIC and ALL other
192.168.1.x traffic will go out the 192.168.2.151 NIC and get handled by the
router (as I understand it).

I will test this tomorrow and let you know what transpires.

Thanks,

Gary Drost

"Phillip Windell" wrote:

> "Gary Drost" <Gary Drost@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:6C23AF0B-46D8-4D93-A5A4-BACFE856C0EC@xxxxxxxxxxxxxxxx
> > Am I going to be hosed until I change my networking scheme so that it
> allows
> > this piece of equipment to run on its own network subnet so that routing
> > works?
>
> You will always be "hosed" there because you can never rework your
> networking scheme to accomidate that since the other remote network is
> already using that Subnet.
>
> > It was suggested to me by the manufacturer that I might be able to run 2
> > NIC's in the PC that controls this equipment. I did drop a 2nd NIC in the
> PC
> > but cannot figure out if there is any way to force the routing to deal to
> > with the same network number located in two different places.
> >
> > Does anyone know of a way to make this work?
>
> Depends on if just the one PC needs to work with it or it the whole network
> needs to work with it,...that is not the same thing.
>
> [If only the one PC uses the device]
> 1. Let's say the Device is 192.168.1.1
> 2. Lets say the PC's nic you added is 192.168.1.2
> 3. The route in the routing table would be this
>
> "route add -p 192.168.1.2 mask-255.255.255.255 int-192.168.1.1"
>
> This tells it that anything destined for the *specific* address of
> 192.168.1.1 (the Device) is supposed to use Outbound Interface 192.168.1.2.
> This will not bother your normal routing to the remote Subnet of 192.168.1.*
> except for the one address of 192.168.1.1 which would never be reachable on
> that path for that one PC.
>
> ----------------------------------------------------------------------------
> ------
>
> [If the whole network uses the device]
> 1. Setup a NAT Device between the LAN and this "Device".
> 2. Use Static NAT to "publish" the Device to your LAN.
> 3. The IP# of the NAT device will be used to access the Device instead of it
> "true" IP#.
>
> You can use a Hardware NAT Device or build a NAT Server using windows Server
> with RRAS (http://support.microsoft.com/default.aspx?scid=kb;en-us;816581).
>
>
>
>
.

Relevant Pages

  • Re: Changing Corporate subnet address
    ... your workstations & servers after changing the subnet, ... Maybe my thinking is flawed but I believe after changing the subnet I ... VPN users must not be using the same IP network as the ... changes if you have no remote connectivity to them. ...
    (microsoft.public.windows.server.dns)
  • Re: Changing Corporate subnet address
    ... Maybe my thinking is flawed but I believe after changing the subnet I will ... VPN users must not be using the same IP network as the ... Well, the *lack* of DHCP may be a problem, as it would be much easier to ... no remote connectivity to them. ...
    (microsoft.public.windows.server.dns)
  • Re: Changing Corporate subnet address
    ... often use the same subnet as my private subnet which causes ... VPN users must not be using the same IP network as the ... Well, the *lack* of DHCP may be a problem, as it would be much easier to ... no remote connectivity to them. ...
    (microsoft.public.windows.server.dns)
  • Re: Changing Corporate subnet address
    ... and etc. through our ISA server running Routing and Remote Access. ... The problem is our private network uses IP subnet 192.168.1.XXX which is such ... The only solution I know is to change the local subnet addressing but I ...
    (microsoft.public.windows.server.dns)
  • Re: ICS questions and confusion
    ... >>>It doesn't HAVE to be on a different subnet, ... but that requires that the ICS host become a bridge. ... >> ICS is a software based NAT router, and routers work best when the ... >> network already had the required address 192.168.0.1" is confusing. ...
    (microsoft.public.windowsxp.network_web)