From: Ignoramus21069 on
On 2010-01-11, David Schwartz <davids(a)webmaster.com> wrote:
> The difference is that your new server is trying to use your old
> server as a router. Is your old server configured as a router? Is IP
> forwarding on?

No, this is not the case. The router is 65.182.171.161, and neither
the old, nor the new computer have that address. The main IP address
of the old computer is .162, and of the new computer it is .174.

i


From: Ignoramus21069 on
On 2010-01-11, David Schwartz <davids(a)webmaster.com> wrote:
> On Jan 11, 11:22?am, David Schwartz <dav...(a)webmaster.com> wrote:
>> The difference is that your new server is trying to use your old
>> server as a router. Is your old server configured as a router? Is IP
>> forwarding on?
>>
>> DS
>
> Sorry, misread. Let's try troubleshooting. Can the new server ping its
> default router?

Well, yes, but that happens through the main IP address .174, which
always worked.

The problem is that when I _add another_ IP address, the address is
only accessible from inside of my subnet. Ergo, I can ping it from my
old server, or from the new server itself. But from outside, it is not
reachable.

i
From: Ignoramus21069 on
Guys, my feeling is that this may not be a Linux configuration issue,
but instead, the routing issue at my ISP. They may somehow not update
their network equipment when IPs come up. I will try to talk to them.

i
From: Ignoramus21069 on
On 2010-01-11, Ignoramus21069 <ignoramus21069(a)NOSPAM.21069.invalid> wrote:
> Guys, my feeling is that this may not be a Linux configuration issue,
> but instead, the routing issue at my ISP. They may somehow not update
> their network equipment when IPs come up. I will try to talk to them.

My brother in law thinks so too.

i