[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] Strange IP Problem
- Subject: [cobalt-users] Strange IP Problem
- From: "Ethos Subscriptions" <ethos.subscriptions@xxxxxxxxxxxxxxx>
- Date: Tue Oct 1 01:09:02 2002
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
Hi everyone!
We have a cobalt RaQ3 which is used to host sites and email for ourselves
and our clients, and is located at our provider's data centre.
We recently changed the ADSL provider we use at our office, and through our
new connection we can't properly access our server.
The server has a main IP address used for all services, and a secondary IP
address which has only a couple of sites assigned to it.
<IP ADDRESS 1> - main IP address. We can ping and traceroute this address,
but NOT access web sites, email, SSH or Telnet through it. This is our
primary nameserver address.
<IP ADDRESS 2> - second IP address. We can ping and traceroute this address,
and access the mail server, SSH and Telnet. We have only a couple of web
sites set up at this IP address, but we can access them fine. This is our
secondary nameserver address.
The server has several URLs which are all set to resolve to <IP ADDRESS 1> -
none of these work.
We get the above problem when accessing the Internet through our ADSL
connection. However, our ADSL provider also offers us dial-up access - when
we dial up to our account through a standard modem, there is no problem.
The server is a Cobalt RaQ 3, using Apache Web Server, Mail Server, Telnet,
SSH, SSL, and provides its own DNS.
Anyone have any ideas what's going on? Our ADSL connection appears to
function flawlessly apart from this problem. We seem to be able to access
other web sites, including sites located on servers in the same data centre.
A client of ours reported the same problem a few months ago with a different
ISP, and it was never resolved. Our ISP is looking into it, but is having
difficulty locating a problem as they can access the server with no problems
at their office. To us, it sounds like there is a block being put on <IP
ADDRESS 1> - but could it be a problem with the RaQ? If so what do you think
it is? If not, any ideas what the problem could be or tips on how we can
further investigate?
Any advice is greatly appreciated! Cheers everyone...
Si