Date:  Mon, 7 Dec 2009 19:09:06 +0000
From:  "Colin Jack" <colin (at mark) mainline.co.uk>
Subject:  [coba-e:16194] Re: Slow login
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <45DACA7BE1DEA245AF6C95E5B94E531B1C9EE50D8B (at mark) datastore.mainline.local>
In-Reply-To:  <200912071926.10913.bq (at mark) solarspeed.net>
References:  <45DACA7BE1DEA245AF6C95E5B94E531B1C9EE50D81 (at mark) datastore.mainline.local> <200912071847.36354.bq (at mark) solarspeed.net> <45DACA7BE1DEA245AF6C95E5B94E531B1C9EE50D87 (at mark) datastore.mainline.local> <200912071926.10913.bq (at mark) solarspeed.net>
X-Mail-Count: 16194

Hi Michael,

> 
> Ok, so it works in general. But how fast?

Instant

> 
> Example:
> 
> 	nslookup bbc.co.uk 192.168.2.1
> 
> If that works (and works fast) then you can rule out a DNS issue.

All respond instantly (faster than fast)

> In an environment like yours (Firewall in front of thingss, public IP bound to
> the router, then server on private NAT'ed IP's) FTP is a bit tricky in
> general. The Firewall needs to have ports 49152-65534 open in order to allow
> passive FTP. That's the IANA port range assigned for this. You can also make
> that range smaller if you like to (or use different ports), but then you also
> have to make sure your Proftpd knows about it and only uses ports from that
> smaller range.

I do not think it is the firewall. If I FTP from one of the internal servers (so LAN to LAN through the switch) it is still very slow.

I have UseReverseDNS   off in proftpd.conf

Also SSH login is also slow (but not as slow as FTP).

> --
> With best regards,
> 
> Michael Stauber
> 
Regards

Colin




Mainline company details are available at http://www.mainline.co.uk/disclosure.html