Sparc SOlaris nis client to Linux NIS server
dog...@noemail.com
of frustration in the migration previously mentioned in my post
about ssh -X and VNC. Soo.
Same setup, Sunfire V240 Solaris 8 02/04. I've configured it as a
nis client. I logon as root (local account). Verify that it sees
the nis master (ypwhich), verified that it can cat the hosts file
(ypcat hosts), verified that it can see the passwd file (ypcat
passwd). These all work. I have also the ability to (when logged
in as root) su - <username> and become a user (whereas the user
is a NIS user with account information and home directory on the
Linux NIS server). What I cant do is logon via the CDE logon
screen. I get the "incorrect logon" error.
I've ran ethereal to check the connection and the closest anomaly
I found was that when logging on the Solaris box via CDE it is not sending
the logon credentials to the Linux NIS server, therefore not getting a response
back that its a valid logon. Now, this isnt the end. I also ran
ethereal against a telnet session to the solaris box, and I did see
it send the username over the wire to the NIS server, but again
got an incorrect logon error.
Has anyone seen this?? I'm thinking a patch or something since the
sparc is freshly built with no patches.
TIA again
dogdog
dog...@noemail.com
> In article <pan.2005.12.10....@noemail.com>,
> Does it work if you switch to a Solaris NIS master with either a Linux
> client or Solaris client?
>
> Some Linux kernel's NFS is just plain broken for anything other than
> Linux.
Good question, I havent tried it against one of my solaris NIS
masters.
As for the linux kernel NFS being broken with other OSs beside
linux, I really couldnt tell you. The only thing I can go by is
that its RHEL 3.0 Server, and that should be pretty stable (at
least you'd think so its a 2.4.xx kernel).
Since I'm on the subject of NFS, well I do share out /home from
the Linux server to act as the NIS users home directory repository.
The Solaris box mounts that directory exactly as it should. WHen
I logon to the Solaris box and cd over to /home I do see my users
home directories. So I dont think NFS is causing the problem in
this case.
Greg Menke
dog...@noemail.com writes:
> > Does it work if you switch to a Solaris NIS master with either a Linux
> > client or Solaris client?
> >
> > Some Linux kernel's NFS is just plain broken for anything other than
> > Linux.
>
> Good question, I havent tried it against one of my solaris NIS
> masters.
>
NFS 4 mounts from a linux 2.6 kernel are still broken last I tested
them. Mounts OK but comes unglued during significant IO, can't
unmount.. have to reboot, same old sob story...
Gregm
dog...@noemail.com
Thats not good. Maybe a good thing I'm running a 2.4 kernel?
Greg Menke
My approach is to stick with NFS 3 when Linux is a client or server.
NFS 4 if both boxes are Solaris.
Gregm
dog...@noemail.com
The solution was that I had md5 password enabled on the linux box.
The sun box couldnt understand them, so by doing
authconfig -disablemd5 took care of the problem, now the Solaris
box can authenticate.
Thanks to all who gave suggestions, they were excellent just didnt
lead up to the solution this time. again thanks all
dogdog
Casper H.S. Dik
>The solution was that I had md5 password enabled on the linux box.
>The sun box couldnt understand them, so by doing
>authconfig -disablemd5 took care of the problem, now the Solaris
>box can authenticate.
Solaris 9 update 2 and later should be able to handle those
just fine.
Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
dog...@noemail.com
> dog...@noemail.com writes:
>
>>The solution was that I had md5 password enabled on the linux box.
>>The sun box couldnt understand them, so by doing
>>authconfig -disablemd5 took care of the problem, now the Solaris
>>box can authenticate.
>
> Solaris 9 update 2 and later should be able to handle those
> just fine.
>
> Casper
Casper, I was wondering if you were going to chime in. Its always
good to see an actual sun guru step in. Unfortuneatly I cannot
use solaris 9 at this point, however I've hear good and bad
about it. Thanks for passing that information, I did find it
a bit strange that md5 would not be "supported" but now that I
know 9 handles it and I'd guess to say 10 as well? This would
probabaly be why I received responses that people had no problems
when integrating RHEL and Sun (master client).
Thanks casper
dogdog
Casper H.S. Dik
>Casper, I was wondering if you were going to chime in. Its always
>good to see an actual sun guru step in. Unfortuneatly I cannot
>use solaris 9 at this point, however I've hear good and bad
>about it. Thanks for passing that information, I did find it
>a bit strange that md5 would not be "supported" but now that I
>know 9 handles it and I'd guess to say 10 as well? This would
>probabaly be why I received responses that people had no problems
>when integrating RHEL and Sun (master client).
If you plan to upgrade, I'd recommend S10 over S9.
(Why pick a 4-year old OS over a 1 yaer old one?)
Solaris 9 update 2 and later Solaris releases support pluggable
password encryption. The standard plugins provided are
old fashioned Unix crypt, bsd/linux md5 and blowfish crypt as well
as "sunmd5" crypt.
dog...@noemail.com
> dog...@noemail.com writes:
>
>>Casper, I was wondering if you were going to chime in. Its always
>>good to see an actual sun guru step in. Unfortuneatly I cannot
>>use solaris 9 at this point, however I've hear good and bad
>>about it. Thanks for passing that information, I did find it
>>a bit strange that md5 would not be "supported" but now that I
>>know 9 handles it and I'd guess to say 10 as well? This would
>>probabaly be why I received responses that people had no problems
>>when integrating RHEL and Sun (master client).
>
>
> If you plan to upgrade, I'd recommend S10 over S9.
> (Why pick a 4-year old OS over a 1 yaer old one?)
>
> Solaris 9 update 2 and later Solaris releases support pluggable
> password encryption. The standard plugins provided are
> old fashioned Unix crypt, bsd/linux md5 and blowfish crypt as well
> as "sunmd5" crypt.
>
> Casper
Are the openwin lib's supplied with the supplemental disks for
solaris 10? I have alot of older apps that require them for
operation. That seems to be the only drawback as to why we
were told not to migrate to 10, other than its not approved
for our use (go figure that).
Casper H.S. Dik
>Are the openwin lib's supplied with the supplemental disks for
>solaris 10? I have alot of older apps that require them for
>operation. That seems to be the only drawback as to why we
>were told not to migrate to 10, other than its not approved
>for our use (go figure that).
Which particular libraries?
A number of the libraries, specifically libxview and libolgx
as well as supporting runtime files are all still in Solaris 10.
The *tool commands and the headers are gone, though.