This is the network in a nutshell:
(Ip Address of
+----------------+ Cisco Ethernet)
Ser0 | Cisco 2501 | 206.100.242.12
Internet<---------+ +-------------------+------+-----
| (Ser1) | |
+-------+--------+ +-------+-------+
10.1.1.1 | | 206.100.242.11|
| +---------------+
|
10.1.1.2 |(W1)
+-----------+----------+
| Remote Pop PM2ER |
| Ethernet Ip Address |
| 206.100.243.129 |
+----------------------+
Scenario, I telnet from 206.100.242.11 to 206.100.243.129, log in to the
remote Portmaster. Telnet back from the Portmaster to 206.100.242.11 and
do a who, and see myself logged in from address 10.1.1.2. Since the
10.1.1.2 is in the reserved addresses for internal addresses, I'm sure I
can't go anywhere on the outside world and expect to get any replies
back. My cry for help was a false alarm, because everyone that logs in on
the remote portmaster can surf just fine. They are assigned one of the
addresses from the pool which is routed back just fine.
How come, when I telnet from the remote PM2ER does it say I am
originating from 10.1.1.2? I'll have to dig in my TCP/IP books to see why
a traceroute works but a ping doesn't, but that is my problem, and I will
do my homework.
Later
Kelley
On Sat, 16 Nov 1996, Michael Blackstock wrote:
> We have the same problem and were told it was a routing problem from our
> upsteam provider ? Everything seems to work just fine so we haven't
> pursued it. If you get an answer, let us know.
>
>
> On Fri, 15 Nov 1996, Kelley Lingerfelt wrote:
>
> > We just moved and we are trying to get started back up, but we have a
> > remote pop with a pm2er, I can telnet to the remote pop, but if I try to
> > ping from the remote pop it will not,(no answer) but if I try a
> > traceroute it will succeed. Does this sound familiar to anybody, I am at
> > a loss. Any details needed just ask, will supply all I know of.
> > HELP!!
> >
> > Later
> > Kelley
> >
>