jthomet
03-15-2006, 07:06 PM
Hi Everyone,
I'm hoping someone out there has a solution for this... I've managed to find people with the same problem on google; but thus far no solutions. Anyways, here goes:
I've got a Fedora Core 4 box that authenticates to our Active Directory server via winbind. Everything works fine when I connect to the box via telnet, SSH, or Samba and local logins work fine (using domain credentials). However, when I try to log in via rlogin, my connection is rejected, and the following is displayed in my /var/log/messages log:
Mar 15 15:35:26 suds pam_winbind[26446]: write to socket failed!
Mar 15 15:35:26 suds pam_winbind[26446]: internal module error (retval = 3, user = `bill')
Mar 15 15:35:26 suds in.rlogind[26446]: PAM authentication denied for in.rlogind
For contrast, here is the contents of the messages log when I SSH to the box:
Mar 15 15:35:50 suds pam_winbind[26513]: user 'bill' granted access
Mar 15 15:35:50 suds pam_winbind[26513]: user 'bill' granted access
Mar 15 15:35:50 suds sshd(pam_unix)[26515]: session opened for user bill by (uid=0)
So, obviously winbind is working, but for some reason when invoked by rlogin, the sucker is unable to write to a socket. Anyone else ever seen this, or have any idea how I can get around it? If needed, I can post the pertinent files from my /etc/pam.d directory, and I'll be willing to provide any other information necessary.
(Yes, I know telnet/rlogin are unsecure; but please don't flame me about that. Thats the infrastructure I've been given to work with. With any luck, we'll be pushing everyone to SSH soon.) Thanks in advance for any help you can offer!
I'm hoping someone out there has a solution for this... I've managed to find people with the same problem on google; but thus far no solutions. Anyways, here goes:
I've got a Fedora Core 4 box that authenticates to our Active Directory server via winbind. Everything works fine when I connect to the box via telnet, SSH, or Samba and local logins work fine (using domain credentials). However, when I try to log in via rlogin, my connection is rejected, and the following is displayed in my /var/log/messages log:
Mar 15 15:35:26 suds pam_winbind[26446]: write to socket failed!
Mar 15 15:35:26 suds pam_winbind[26446]: internal module error (retval = 3, user = `bill')
Mar 15 15:35:26 suds in.rlogind[26446]: PAM authentication denied for in.rlogind
For contrast, here is the contents of the messages log when I SSH to the box:
Mar 15 15:35:50 suds pam_winbind[26513]: user 'bill' granted access
Mar 15 15:35:50 suds pam_winbind[26513]: user 'bill' granted access
Mar 15 15:35:50 suds sshd(pam_unix)[26515]: session opened for user bill by (uid=0)
So, obviously winbind is working, but for some reason when invoked by rlogin, the sucker is unable to write to a socket. Anyone else ever seen this, or have any idea how I can get around it? If needed, I can post the pertinent files from my /etc/pam.d directory, and I'll be willing to provide any other information necessary.
(Yes, I know telnet/rlogin are unsecure; but please don't flame me about that. Thats the infrastructure I've been given to work with. With any luck, we'll be pushing everyone to SSH soon.) Thanks in advance for any help you can offer!