Hi all,
I'm having problems logging in.
Initial login takes an age (~1 minute). Sudo in a terminal takes also take an age, but if I log out and log back in again, I get an immediate login.
I think I've had a problem like this before where I had set up something wrong, so that the thing that was handling the login was trying to connect to a non-existant windows server to verify the login, waiting for a time-out, then handling the login itself. On subsequent logins, it's like it knows it's timed out, and doesn't bother trying.
This is on my server, and it should be responsible for it's own log-ins. It's running dnsmasq, and is a samba server. I've set samba so that it says it is the authoritative nameserver. Any idea what's going wrong, or what I can look at to work out what's going wrong. There's nothing obvious to me in the log file viewer, or Dmesg. Any other log files to look at or config files to tweak? Any way to view what the login process is doing??
Ubuntu server 10.04.4 LTS
Any help gratefully received.
Steve
All login attempts or ssh login attempts (local or otherwise) ?
You didn't accidentally install the winbind stuff did you when you were installing Samba ? That may have messed with PAM so it is now looking for a Domain that doesn't exist or something ?
Otherwise another common reason for slow ssh logins is if sshd is failing to resolve reverse dns queries.
if 'UseDNS no' in your sshd config speeds things up then this is the problem. Although the cause is that your DNS setup is broken.
On 18/03/12 18:50, Wayne Stallwood wrote:
All login attempts or ssh login attempts (local or otherwise) ?
All logins
You didn't accidentally install the winbind stuff did you when you were installing Samba ? That may have messed with PAM so it is now looking for a Domain that doesn't exist or something ?
Aha! Winbind was installed. Winbind is no-longer installed, and normal speed logins have returned.
Is winbind necessary for Windows machines to connect to this server via SMB as this machine is also a samba server, or does winbind just allow *nix machines to join a windows domain? I've tried googling but it's not immediately obvious to me, pro'lly because I'm knackered!
Thanks for the help :-)
Steve
On 19/03/12 00:40, steve-ALUG@hst.me.uk wrote:
Is winbind necessary for Windows machines to connect to this server via SMB as this machine is also a samba server, or does winbind just allow *nix machines to join a windows domain? I've tried googling but it's not immediately obvious to me, pro'lly because I'm knackered!
Thanks for the help :-)
No you only need it if you are going to authenticate Domain Users on your *nix machine (so for example if the *nix machine is going to be a file server in a Windows Domain)
On 22/03/12 21:38, Wayne Stallwood wrote:
On 19/03/12 00:40, steve-ALUG@hst.me.uk wrote:
[Winbind?]
No you only need it if you are going to authenticate Domain Users on your *nix machine (so for example if the *nix machine is going to be a file server in a Windows Domain)
Ah, well it is going to be a file server in a Windows domain, but the only server, and it controls the domain via Samba.
So I've uninstalled Winbind. My login problems went. My Windows machines can still connect and authenticate to the server.
All's good.
Ta Very Much! Steve
On 24/03/12 23:07, steve-ALUG@hst.me.uk wrote:
On 22/03/12 21:38, Wayne Stallwood wrote:
On 19/03/12 00:40, steve-ALUG@hst.me.uk wrote:
[Winbind?]
No you only need it if you are going to authenticate Domain Users on your *nix machine (so for example if the *nix machine is going to be a file server in a Windows Domain)
Ah, well it is going to be a file server in a Windows domain, but the only server, and it controls the domain via Samba.
So I've uninstalled Winbind. My login problems went. My Windows machines can still connect and authenticate to the server.
Ahh the only problem with that might be I am not sure if winbind is involved if Samba is providing the domain authentication services and Windows users want to change their domain password.
It's been a while since I did this but I am sure winbindd plays some part in that.