On Wed, 10 Nov 2004, Yuval Kogman wrote:

> Howdy!
>
> We have some windows machines running Cygwin to which we'd like to
> connect via rsh.
>
> It all works well if the passwd entry's home field points to a local
> directory, and the .rhosts file in that directory contains the proper
> values.
>
> The accounts are hosted on a linux based file server. The unixes get the
> home directory via NFS, and the fileserver also shares via samba.
>
> If you set the home to //fileserver/share in the cygwin box's
> /etc/passwd, then .rhosts suddenly stops being valid, and you're asked
> for a password. What's funny is that if you put the right password in,
> then a shell is started, and the pwd is the share, and the files therein
> are available, including .rhosts.
>
> So basically:
>
> 1. does anybody know why rlogind doesn't like SMB shares?

<http://cygwin.com/cygwin-ug-net/ntsec.html#NTSEC-SWITCH>, or see
/usr/share/doc/Cygwin/inetutils-1.3.2.README

> 2. does anybody know where rlogind logs it's complaints to?

Should be in /var/log/inetd.log or the Windows Event Log (Application).

> 3. while we're added, how do you get rlogind to be promiscuous?  Or
> actually, what's the cygwin equivelent of /etc/pam.d/rlogind ?

If by "promiscuous" you mean "persistent", go to the Service Control
Manager and set Startup Type for the "inetd" service to "Automatic".
        Igor
-- 
                                http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_                [EMAIL PROTECTED]
ZZZzz /,`.-'`'    -.  ;-;;,_            [EMAIL PROTECTED]
     |,4-  ) )-,_. ,\ (  `'-'           Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL     a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Reply via email to