Route Add

  • Thread starter Thread starter Lion
  • Start date Start date
L

Lion

Hi,

I have a WinXP machine with Address 192.168.1.2/24 (there is a reason for
this) that is connected to my 10.1.0.0/21 network. The gateway on the
10.1.0.0/21 is 10.1.1.1. using Route Add on the XP box what do I need to
type to make it accessible from a host on 10.1.0.0/21 network.

Thank you in advance.
 
Lion said:
Hi,

I have a WinXP machine with Address 192.168.1.2/24 (there is a reason for
this) that is connected to my 10.1.0.0/21 network. The gateway on the
10.1.0.0/21 is 10.1.1.1. using Route Add on the XP box what do I need to
type to make it accessible from a host on 10.1.0.0/21 network.

Thank you in advance.
Click to expand...

Two steps:

1. Clean up the Nic's TCP/IP settings. Don't forget to look in the Advanced
section to see if any "extra" IP#s were added and remove them. If the
machine has two nics leave the one you are not using set to "Automatic
Addressing". Most likey all your nics will just be Automatic.

2. From a command prompt type "route /f" and reboot. Anything in the
Routing Table after that is supposed to be there.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
 
I need a PC to keep the 192 address.


Phillip Windell said:
Two steps:

1. Clean up the Nic's TCP/IP settings. Don't forget to look in the
Advanced section to see if any "extra" IP#s were added and remove them.
If the machine has two nics leave the one you are not using set to
"Automatic Addressing". Most likey all your nics will just be Automatic.

2. From a command prompt type "route /f" and reboot. Anything in the
Routing Table after that is supposed to be there.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or
Microsoft,
or anyone else associated with me, including my cats.
Click to expand...
 
Let's be a little less "cryptic"...

"Spill the guts",...what are you really doing and more importantly *why* are
you doing it the way you are doing it?

Just because something is done a certain way for a certain reason does not
mean it is the right way or the right reason. All things have to be looked
at an considered.

What are the IP specs of the machine?
Paste in the output from "IPConfig /all"
Do not "fake" the numbers.

I do not need a Route Table output,...it is not important because if the IP
specs of the machine are correct & proper and you run "route /f" and
reboot,... the Table *will* be correct.

--
Phillip Windell
www.wandtv.com



Lion said:
I need a PC to keep the 192 address.
Click to expand...
 
OK Perhaps I should have explained myself better first time.

LAN 1
I have a machine connected to a Switch that controls a Video Wall. The
screens are on 192.168.1.0/24 network hence why the IP address of the
controlling PC it's set to 192.168.1.10/24

LAN 2
On the same site I have a 10.1.0.0 / 21 network with a switch and router for
internet access. The router IP addresses its 10.1.1.1/21 and all devices on
the 10.1.0.0 / 21 use this router to access internet.
LAN 1 and LAN 2 are not connected and I cannot change the 192.168.1.0/24
network to have 10.1.0.0 / 21 addresses.
Without installing the additional NIC in to 192.168.1.10/24 PC and giving it
10.1.0.0 / 21 how else can I access the 192.168.1.10/24 PC.
I understand that I physically need to join the LAN 1 and LAN 2 Switches
using Ethernet cable which is not an issue.

On the 192.168.1.10/24 how can I use the route add to add a permanent route
to have communication between LAN 1 and a device on LAN 2 with IP address of
192.168.1.10/24 PC?
Can I add a 10.1.0.0 / 21 static IP address to the existing NIC on device in
LAN two with current IP of 192.168.1.10/24?

Hope this is clear.



Phillip Windell said:
Let's be a little less "cryptic"...

"Spill the guts",...what are you really doing and more importantly *why*
are you doing it the way you are doing it?

Just because something is done a certain way for a certain reason does not
mean it is the right way or the right reason. All things have to be
looked at an considered.

What are the IP specs of the machine?
Paste in the output from "IPConfig /all"
Do not "fake" the numbers.

I do not need a Route Table output,...it is not important because if the
IP specs of the machine are correct & proper and you run "route /f" and
reboot,... the Table *will* be correct.
Click to expand...
 
On the same site I have a 10.1.0.0 / 21 network with a switch and router
for internet access. The router IP addresses its 10.1.1.1/21 and all
devices on the 10.1.0.0 / 21 use this router to access internet.
LAN 1 and LAN 2 are not connected and I cannot change the 192.168.1.0/24
network to have 10.1.0.0 / 21 addresses.
Without installing the additional NIC in to 192.168.1.10/24 PC and giving
it 10.1.0.0 / 21 how else can I access the 192.168.1.10/24 PC.
I understand that I physically need to join the LAN 1 and LAN 2 Switches
using Ethernet cable which is not an issue.
Click to expand...

Put the PC on the regular LAN with the 10.1.0.0/21 address.
Add the 192 address to the same nic as a "secondary" address in the Advanced
section of the nics TCP/IP properties. The 10 address will be the *primary*
address.
The "Video Wall" must be on the "same wire" as the rest of the LAN.

It is a "kludge",..there is no way I would do it that way,...but it would
work
If you have intrusion detection systems on the 10 LAN they will go nuts
seeing the 192 addresses on the same wire,...and you 'll have to ignore the
alerts
On the 192.168.1.10/24 how can I use the route add to add a permanent
route to have communication between LAN 1 and a device on LAN 2 with IP
address of 192.168.1.10/24 PC?
Can I add a 10.1.0.0 / 21 static IP address to the existing NIC on device
in LAN two with current IP of 192.168.1.10/24?
Click to expand...

There is no "Route",...because there is no "routing" happening here. The PC
is just simply having dual identities off the same nic,...again,..bad
idea,...I wouldn't do it.

Side note:

Ethernet begins to nose-dive on effieciency as it gets over 250-300 Hosts.
You should never use a Mask smaller than /24 unless you are Supernetting
over a Backbone. So you should not be using /21. If you have exceeded 254
Hosts on the LAN then you should add a LAN Router to the LAN and add one or
more subnets with all subnets using a 254 Host segment (/24). Not only
would this make the LAN more efficient, but it would have solved the issue
with the Video Wall before it ever happened.

Any company with more than 254 hosts is never going to convince me that they
cannot afford to buy a simple LAN Router. If they can't,...they are about
to go out of business any day now and you should flee. Some commercial
grade Firewalls can have muliple LAN Interefaces and can pull "double-duty"
as a LAN Router although they tend to not have all the routing features that
a real LAN Router can have.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
 
Back
Top