Johannes Nohl wrote:
This normally is a problem with dns resolution. The resolv.conf file
should be updated automatically updated by dhclient when you get your
ip. If it isn't, then something is wrong.
But that's exactly what happens. All three nameservers are working and
I can look up my dial in IP using nslookup. There are no delays.
Also I read that the resolving problem is causing a delay before you
are prompted for password. I experienced the delay AFTER password
prompt.
Hi,
I also encountered this problem when I upgraded from 10.2 to 10.3. On
10.2 using putty from either a linux box or winx box to the 10.2 server
it was almost instantaneous. After the upgrade to 10.3 it took a LONG
time to get the password prompt after entering the login name -
sometimes the problem was also seen on the login prompt. It was not a
dns issue as my dns and resolv were working fine in all other aspects -
only ssh was affected. This was when 10.3 first came out - however now
it seems to be back to normal - not sure if the updates had anything to
do with it. In fact when this originally happened after the upgrade to
10.3 - i did monitor the log files as well as using tripwire but nothing
came of it as there were no errors or anything - just a timing issue.
After entering the login name, it would just sit there for between 15 to
35 secs and EVENTUALLY the password prompt came up. I guess you perform
all the updates and the prob seems to disappear (at least it did so in
my case!). Rgds. Otto.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
