On May 10, 2009, at 21:53, Pablo Sanchez wrote:
When you connect to a `sshd', if UseDNS is set, `sshd' will attempt to authenticate by also using the incoming machine's host name. If DNS isn't configured (properly) on the sshd machine, you'll get timeouts which manifest themselves as long log in times from the client. For example, if my host is named `foo' and the guest is named `bar' If foo's DNS is horked and UseDNS is set in foo's sshd_config file, when `bar' (or any other client) attempts to log in to `foo', you'll get the long log in times. It's a quick test so give it a whirl.
I'm not running sshd on my host. Do you mean I should make the change on the guest where sshd is running? I'm using the OS X host as the ssh client, and the OpenSolaris guest as the ssh server running sshd. But useDNS appears in /etc/sshd_config on the host/client but not in /etc/ssh/sshd_config on the guest/server. I'm confused. But perhaps you have me on the right track: nslookup on the guest is failing with timeout. (Experimenting ...) Ah! Got it! Apparently when I started my guest, my host was connected via VPN to my employer's intranet. /etc/resolv.conf identifies (only) a nameserver inside the VPN firewall, and the guest inherited that nameserver's IP. When I disconnect from VPN, the ssh delay happens because it can't find the nameserver; when I reconnect, ssh is brisk. Should I: o disconnect from VPN and restart the guest (easy enough) o edit /etc/resolv.conf on the guest? Thanks, gil _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
