[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] raq3i FTP hangs
- Subject: Re: [cobalt-users] raq3i FTP hangs
- From: Jeff Lasman <jblists@xxxxxxxxxxxxx>
- Date: Sat Feb 19 08:19:45 2000
At 04:02 AM 2/18/00 -0900, you wrote:
QUESTION 1
On my RAQ3,
telnet- fast login
http- fast connect
ftp- slow as #((#*(@
it hangs at user and password
My co-lo says my DNS settings "are fine" There was a prob when i setup my
raq with them that they messed up the dns servers. That was supposadly fixed
because i can telnet and http normally now. but FTP is very slow.
It's probably not a DNS problem; if it were, telnet would most likely be
slow to connect, too. And it would hang BEFORE the connect, not at user
and password.
However, don't take your ISP's word that DNS is fine. It's not the DNS on
YOUR RaQ3 that slows down connections, it's the REVERSE DNS on the machine
you're using to connect FROM.
Do:
$ nslookup 00.11.22.33
(where "00.11.22.33" is the number FROM which you're trying to
connect). If there's no reverse DNS for this number, that must be fixed.
The easy way to fix it is to add an appropriate line to your /etc/hosts
file (or create one if you don't have one). The format is:
00.11.22.33<tab>hostname.domainname.ext
where the "00.11.22.33" must be the IP# from which you're trying to
connect, the <tab> is hopefully self-explanatory <smile>, and
hostname.domainname.ext can be just about anything you want, as long as
it's in a standard format.
Of course if you're using a dialup connection and there's no reverse DNS
you're in a bit of a bind, because the IP# changes every time you dial
in. If such is the case try to talk your ISP into setting up reverse DNS
for their dialup lines, or contact me offlist for other options.
It's possibly a DNS problem even though login appears to be fast. HTTP
connections don't care about reverse DNS, so shouldn't matter.
QUESTION 2
When trying to install the RAQ3e OS 2.0 package i get
RaQ3-Update-OS-1.0.pkg failed md5sum check
and the install cancels
Sounds like you've got a bad copy. Get another.
Jeff
--
Jeff Lasman <jblists@xxxxxxxxxxxxx>