|
Home > Archive > alt.os.linux > August 2002 > SLOW FTP LOGIN - n00ber
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
SLOW FTP LOGIN - n00ber
|
|
| AAAAAhhh 2002-08-26, 10:28 am |
| Hey - sup... ok well my problem is when I try to login to my ftp server
(wu-ftp) it takes FOREVER to login (like 40 seconds). Once I'm in, its
fast... in smart ftp this is what it shows:
Connecting to (192.168.0.152).
Connected to (192.168.0.152) -> IP: 192.168.0.152
Socket connected waiting for login sequence. [colo
r=darkred]
>>>*** 40 second wait*** <<<[/color]
localhost.localdomain FTP server (Version wu-2.6.2-5) ready...
so, what am I doing wrong? what can I do to fix or improve this problem.
Its driving me nuts! (when replying, remember, I'm a noob)
| |
| Anoop Aryal 2002-08-26, 12:29 pm |
| wu-ftp is trying to resolve your hostname. if you have a static IP on the
client box put that in /etc/hosts of your server. if you have a dynamic IP
but has a hostname, make sure your server talks to the nameserver that can
resolve the hostname of your client machine.
i'm sorry if that's not detailed enough but with the information you've
posted i'd have to write an entire HOWTO for setting up your network. so if
you want more detailed information, tell me more about the type if IP
addresses you have. ie. does your client have a static IP? if not, does the
DHCP server give you some hostname? etc...
but then it could be a different problem altogether. others may have some
ideas...
"AAAAAhhh" <asdfasdfs@sfsdf.com> wrote in message
news:gfra9.673$Hd4.624354@e3500-atl1.usenetserver.com...
> Hey - sup... ok well my problem is when I try to login to my ftp server
> (wu-ftp) it takes FOREVER to login (like 40 seconds). Once I'm in, its
> fast... in smart ftp this is what it shows:
>
> Connecting to (192.168.0.152).
> Connected to (192.168.0.152) -> IP: 192.168.0.152
> Socket connected waiting for login sequence.
> >>>*** 40 second wait*** <<<
> localhost.localdomain FTP server (Version wu-2.6.2-5) ready...
>
> so, what am I doing wrong? what can I do to fix or improve this problem.
> Its driving me nuts! (when replying, remember, I'm a noob)
>
>
>
| |
|
| AAAAAhhh wrote:
> Hey - sup... ok well my problem is when I try to login to my ftp server
> (wu-ftp) it takes FOREVER to login (like 40 seconds). Once I'm in, its
> fast... in smart ftp this is what it shows:
>
> Connecting to (192.168.0.152).
> Connected to (192.168.0.152) -> IP: 192.168.0.152
> Socket connected waiting for login sequence.
> >>>*** 40 second wait*** <<<
> localhost.localdomain FTP server (Version wu-2.6.2-5) ready...
>
> so, what am I doing wrong? what can I do to fix or improve this problem.
> Its driving me nuts! (when replying, remember, I'm a noob)
>
>
>
>
Sounds like reverse lookup (AUTH requsets port 113 ) are being dropped,
so it waits for timeout (about 40 seconds ).
Set your firewall to either accept auth request, or reject with reset to
avoid the pause.
| |
| Anoop Aryal 2002-08-26, 1:29 pm |
| wu-ftp is trying to resolve your hostname. if you have a static IP on the
client box put that in /etc/hosts of your server. if you have a dynamic IP
but has a hostname, make sure your server talks to the nameserver that can
resolve the hostname of your client machine.
i'm sorry if that's not detailed enough but with the information you've
posted i'd have to write an entire HOWTO for setting up your network. so if
you want more detailed information, tell me more about the type if IP
addresses you have. ie. does your client have a static IP? if not, does the
DHCP server give you some hostname? etc...
but then it could be a different problem altogether. others may have some
ideas...
"AAAAAhhh" <asdfasdfs@sfsdf.com> wrote in message
news:gfra9.673$Hd4.624354@e3500-atl1.usenetserver.com...
> Hey - sup... ok well my problem is when I try to login to my ftp server
> (wu-ftp) it takes FOREVER to login (like 40 seconds). Once I'm in, its
> fast... in smart ftp this is what it shows:
>
> Connecting to (192.168.0.152).
> Connected to (192.168.0.152) -> IP: 192.168.0.152
> Socket connected waiting for login sequence.
> >>>*** 40 second wait*** <<<
> localhost.localdomain FTP server (Version wu-2.6.2-5) ready...
>
> so, what am I doing wrong? what can I do to fix or improve this problem.
> Its driving me nuts! (when replying, remember, I'm a noob)
>
>
>
| |
|
| AAAAAhhh wrote:
> Hey - sup... ok well my problem is when I try to login to my ftp server
> (wu-ftp) it takes FOREVER to login (like 40 seconds). Once I'm in, its
> fast... in smart ftp this is what it shows:
>
> Connecting to (192.168.0.152).
> Connected to (192.168.0.152) -> IP: 192.168.0.152
> Socket connected waiting for login sequence.
> >>>*** 40 second wait*** <<<
> localhost.localdomain FTP server (Version wu-2.6.2-5) ready...
>
> so, what am I doing wrong? what can I do to fix or improve this problem.
> Its driving me nuts! (when replying, remember, I'm a noob)
>
>
>
>
Sounds like reverse lookup (AUTH requsets port 113 ) are being dropped,
so it waits for timeout (about 40 seconds ).
Set your firewall to either accept auth request, or reject with reset to
avoid the pause.
| |
|
| Thanks ! - this solved my slow ftp and telnet too .
"Anoop Aryal" <aaryal@foresightint.com> wrote in message
news:_zta9.5013$yt3.2115848@newssrv26.news.prodigy.com...
> wu-ftp is trying to resolve your hostname. if you have a static IP on the
> client box put that in /etc/hosts of your server. if you have a dynamic IP
> but has a hostname, make sure your server talks to the nameserver that can
> resolve the hostname of your client machine.
| |
|
| Thanks ! - this solved my slow ftp and telnet too .
"Anoop Aryal" <aaryal@foresightint.com> wrote in message
news:_zta9.5013$yt3.2115848@newssrv26.news.prodigy.com...
> wu-ftp is trying to resolve your hostname. if you have a static IP on the
> client box put that in /etc/hosts of your server. if you have a dynamic IP
> but has a hostname, make sure your server talks to the nameserver that can
> resolve the hostname of your client machine.
|
|
|
|
|