Persistent Route

[Guest]

Good evening,
Have a desktop with a wired network connection via router supplying DHCP.
It regularly looses it's network connection, (no other computers on the
network do so,) and I'm working through that problem.

However, I find, if I type 'Route Print' in a DOS box, I get one persistent
route listed, to an IP address in Philadelphia, (I'm in England). I have no
idea how it could have got there, (I built the computer myself).

Could this 'strange' address have any implications for my network?
(I have now removed it), and could it have any influence on my problem of
dropped network connection?

Many thanks,

Colin

 

[John Wunderlich]

Good evening,
Have a desktop with a wired network connection via router
supplying DHCP. It regularly looses it's network connection, (no
other computers on the network do so,) and I'm working through
that problem.

However, I find, if I type 'Route Print' in a DOS box, I get one
persistent route listed, to an IP address in Philadelphia, (I'm in
England). I have no idea how it could have got there, (I built the
computer myself).

Could this 'strange' address have any implications for my network?
(I have now removed it), and could it have any influence on my
problem of dropped network connection?

That depends entirely on what the entry was.

When your computer needs to send a packet to an IP address, the only
thing it knows or needs to know is where to send it next (and that
"where" has to be on the same subnet as one of your computer's
network interfaces). That's what the routing table provides. If
the destination is on the same subnet, then the packet goes directly
to the destination. If it's not on the same subnet then the packet
goes to a routing device (gateway) which supposedly will find a way
to get it to its destination.

Choosing an IP address or subnet and placing a route in the Route
Table that directs it to a non-routing device is one way to preclude
communication with that IP address or subnet.

HTH,
John

 

[Guest]

That depends entirely on what the entry was.

When your computer needs to send a packet to an IP address, the only
thing it knows or needs to know is where to send it next (and that
"where" has to be on the same subnet as one of your computer's
network interfaces). That's what the routing table provides. If
the destination is on the same subnet, then the packet goes directly
to the destination. If it's not on the same subnet then the packet
goes to a routing device (gateway) which supposedly will find a way
to get it to its destination.

Choosing an IP address or subnet and placing a route in the Route
Table that directs it to a non-routing device is one way to preclude
communication with that IP address or subnet.

HTH,
John

Thank you John,
I've further found that when the computer looses it's network connection, it
looses it's router supplied IP. It then reverts to this 'strange' IP address
being shown as the computers' IP address.
That is, it loses it's '192.x.x.x' address and gains this '169.x.x.x' address.

I will remove the persistent route and see what happens next!

Regards,

Colin