If he calls into pm3-1 ( 206.176.32.1 ) i am able to properly see the
connection by telneting to his machine.
If he calls into pm3-2 ( 206.176.32.2 ) I am not able to see the connect.
If you try and traceroute to 206.172.32.240 it goes all the way to pm3-1,
bounces back to the router, bounces back to pm3-1, back to the router and
so on and so on untill teh traceroute reaches it max hop count.
The same thing happens if he connects to pm3-3 ( 206.172.32.3 )
I have all routing proto's turned OFF on my pm3's.
If i turn on RIP then its able to make its way to 206.172.32.240, but it
goes thru pm3-1 then to pm3-2 or pm3-3 .. which is weird.
Why its trying to go thru pm3-1 first I dunno and I am looking for some
insight as to why this is happening.
I shouldnt have to turn RIP on for this, I dont really want or need to run
RIP.
.-------------------------------------------------------------------.
| Steve Mickeler -- Steve@Neptune.On.Ca |
| Network Operations |
|-------------------------------------------------------------------|
| Neptune Internet Services - Voice: 905-895-0898 Fax: 905-895-1759 |
`-------------------------------------------------------------------'
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>