Have you found a

Shaggy — Wed, 02 Sep 2009 12:58:46 +0000

Have you found a solution?

What do you get on the host machine when you 'nslookup '?

Cheers,
Shaggy.

Yes, I set up a DNS server

davecoventry — Mon, 24 Aug 2009 13:18:47 +0000

Yes, I set up a DNS server last year and it really did my mind in.

I suppose I should have thought to that.

I guess that will probably solve the problem. I really don't want to got the static IP route and the UseDNS no actually made the problem worse. Not sure why.

Interesting. I took it to

JeevesBond — Tue, 18 Aug 2009 21:27:06 +0000

Interesting. I took it to mean that the problem is with the client having trouble finding the IP address of the Web server from the DNS server.

Unless you don't have a DNS server? To lookup host names with any speed you're going to need a DNS server connected to your DHCP server. This DNS/DHCP tutorial looks quite promising, if you're using Ubuntu, some other distro, FreeBSD or whatever, do a Google search for 'dns dynamic update dhcp '.

Yes, it is likely sshd is

Shaggy — Tue, 18 Aug 2009 16:16:47 +0000

Yes, it is likely sshd is attempting a 'reverse DNS lookup' on your IP address, and that lookup is timing out because there usually is no answer...

You could:
1) Set up an internal DNS server that reverse maps all your internal IP addresses to a 'name'

2) Set UseDNS = no in /etc/ssh/sshd_config
-- You may need the latest and greatest OpenSSH / sshd for this to work...
-- This is an all or nothing config that you may not want to apply to all incoming connections...

3) Not a fix, but a workaround: Assign your XP machine a static IP address, either through configuration your DHCP server to always hand it the same IP address, or TCP config on the machine itself... that way your /etc/hosts entry fix lasts a little longer...

Cheers,
Shaggy.