[wellylug] Just discovered server is not serving up pages

[Mark Foster]

John

Actually I found your email less than clear too.

If you're on Cable you have a single IP address. I'm assuming it's
121.73.82.180 (which responds to ping) and not 121.73.82.1 (which doesn't).

Cable with a single IP means the router you have sitting behind your
surfboard is doing NAT.  It must be forwarding traffic to an RFC1918 address
(10.0.0.0/8, 192.168.0.0/16 or 172.16.0.0/20) sitting behind it, and you
have port 80 forwarded to a designated IP... ?

This is all at IP level and has nothing to do with a domain name, or any
sort of registration. Either the IP is listening or it's not.

If I browse to http://121.73.82.180/ I get a website back. Looks like
there's an Apache 2.0.52 server on a CentOS host there.

So can you explain what you're trying to achieve, and what is or isn't
happening? Your original email to the list was quite confusing.

Mark.



-----Original Message-----
From: wellylug-bounces at lists.wellylug.org.nz
[mailto:wellylug-bounces at lists.wellylug.org.nz] On Behalf Of John Durham
Sent: Friday, 31 December 2010 2:13 p.m.
To: Wellington Linux Users Group
Subject: Re: [wellylug] Just discovered server is not serving up pages

I'm sure the server is in good order. It's mainly a matter of
>> redirecting traffic to it. At the moment I have decided to try using 
>> kiwi host (as it is easier to trade in $NZ). If I'm correct about 
>> this, once the IP information is registered, the problem should be over.
>>
> Ok now I'm even more confused. The server is in your wgtn office 
> connected to what exactly?
>
> I'm really not sure what those IP addresses have to do with anything.
>
> D
To be certain the server is responding, I pinged its IP address moments ago.
It responded exactly the way it was supposed to.