topic Re: ftp problem..too slow in Operating System - HP-UX

ftp problem..too slow

mw_4 — Thu, 20 Jun 2002 00:57:06 GMT

so slow after login id, passwd..about 60secdons are delayed and after login..
what is the problem.?

Re: ftp problem..too slow

Michael Tully — Thu, 20 Jun 2002 01:03:30 GMT

Hi,

Have a look first off at your system performance. 'top' is a good place to start, you could multiple runaway processes.

Michael

Re: ftp problem..too slow

steven Burgess_2 — Thu, 20 Jun 2002 01:03:31 GMT

Hi

Sounds like a resolution issue - how are you resolving your host names - DNS ?

Steve

Re: ftp problem..too slow

harry d brown jr — Thu, 20 Jun 2002 01:04:31 GMT

check dns.

nslookup server

live free or die
harry

Re: ftp problem..too slow

steven Burgess_2 — Thu, 20 Jun 2002 01:06:54 GMT

Hi

If you are using dns - set it to resolve locally -

/etc/nsswitch.conf

hosts: files [NOTFOUND=continue] dns

Regards

Steve

Re: ftp problem..too slow

KCS_1 — Thu, 20 Jun 2002 01:11:37 GMT

Hi,mw~

it's sound like resolution problem,too.
check up these file.

/etc/hosts, /etc/resolv.conf and /etc/nsswitch.conf

Re: ftp problem..too slow

Tim D Fulford — Thu, 20 Jun 2002 01:24:10 GMT

in addition to above

check lan card settings with lanadmin see if it is full or half duplex.

try doing ftp to various places (smallish file) & look at kB throughput.

if the network is sufferering from weird probs then

# netfmt -f /var/adm/nettl.LOG00 -t 6 #.. this may give you a clue

Tim

Re: ftp problem..too slow

Arockia Jegan — Thu, 20 Jun 2002 04:34:15 GMT

Use glance or top to find out whether u r having any performance issue.

If u add the system name and IP address of the system (from which system you are trying to run ftp) in the /etc/hosts file in the server, it will connect real fast.

Re: ftp problem..too slow

Michael Tully — Thu, 20 Jun 2002 04:45:34 GMT

Let's look at this problem logically:

Where are you trying to connect from?
A PC on your local LAN another server on the
same subnet?

Have your server set up in a simple manner.
Have your hosts file resolve before trying
to query a DNS server, make sure your
/etc/nsswitch file is set correctly. Make sure
the contents of your /etc/resolv.conf file
has at least one domain server listed.

/etc/nsswitch.conf
hosts: files [NOTFOUND=continue UNAVAIL=return TRYAGAIN=return] dns [NOTFO
UND=return UNAVAIL=continue TRYAGAIN=return]

/etc/resolv.conf
domain mydomain.com
nameserver 10.20.10.2
nameserver 10.32.10.3

What was the output from top, glance etc.??
Any output from the other network questions
will help us solve your problem.

Mick

Re: ftp problem..too slow

U.SivaKumar_2 — Thu, 20 Jun 2002 08:19:24 GMT

Hi,
To check whether this is a dns problem. From
a windows client,
c:>\ftp x.x.x.x
x.x.x.x is the ftp server's ip address
now log in and try to get and put a file in server. Is the same problem seen now ?. If no,
then there is some problem with DNS reverse lookup.

regards,
U.SivaKumar

Re: ftp problem..too slow

Mark Greene_1 — Thu, 20 Jun 2002 10:57:01 GMT

- are you using tcp wrappers?

- verify what the lan card is set too, particularly the duplexing, and then verify what the network component into which it is plugged is set too.

- is the the /usr/bin/ftp binary or are you running proftp or something else?

HTH
Mark

Re: ftp problem..too slow

Bill Hassell — Thu, 20 Jun 2002 11:23:51 GMT

Slow response on login (in the 20,40 and 60 second range) is always DNS. These delays are the timeout values when a DNS server is dead or unreachable. If you have one entry in resolv.conf, then 20 secs delay, 3 entries, then 60 seconds.

To avoid this issue (DNS is far too critical to rely on it unless the networks AND the DNS server are ultra-reliable), create the nsswitch.conf file and replace the hosts line with:

hosts: files[NOTFOUND=continue UNAVAIL=continue] dns [NOTFOUND=return UNAVAIL=continue TRYAGAIN=return]

(this is all one line)

Now put important hostnames and IP's into /etc/hosts. This has an added advantage of much faster response than using an external DNS machine. While some will argue that this defeats the purpose of a DNS server, the choice is: very slow or failed logins and applications if the DNS server goes down, or for the few production IP addresses, use /etc/hosts. After all, how many times per week do you change the production machines's IP address?