Its a sparc/solaris 9 with Sunray server 3.1. I'd foud the same
information about de "26D", but since the problem began when I
configured the LDAP client, I dont think it may be the Xsun problem.
I think the problem is in the pam.conf. I've tryed to do something in
there, but still not working....
Here is some LOG from my dmesg:
Jan 17 14:00:22 microelsv3 ipf[259]: [ID 293258 user.error] libsldap:
Status: 2 Mesg: Unable to load configuration
'/var/ldap/ldap_client_file' ('').
Jan 17 14:00:22 microelsv3 ipmon[261]: [ID 293258 local0.error]
libsldap: Status: 2 Mesg: Unable to load configuration
'/var/ldap/ldap_client_file' ('').
Jan 17 14:00:22 microelsv3 last message repeated 1 time
Jan 17 14:00:22 microelsv3 ipsecconf: [ID 293258 auth.error] libsldap:
Status: 2 Mesg: Unable to load configuration
'/var/ldap/ldap_client_file' ('').
Jan 17 14:00:22 microelsv3 last message repeated 3 times
Dorst.
On 1/17/07, Garry Robbins <[EMAIL PROTECTED]> wrote:
You did not specify what versions of software / hardware you are using.
That helps.
According to the V3.1 Administrators Guide, a "26D" code means:
Wait for Session OSD
This OSD represents the transition state for the Sun Ray DTU. If it is
displayed for an extended period, there is probably no X Window server
running.
Does that mean anything to your situation?
Carlos Eduardo Dorst wrote:
After I configured my SUNRAY server as an ldap client all the appliances
stop working. They can get an IP ADDRESS, but freezes with a "26D" code.
I can log with SSH, XDMCP, but not in SUNRAY appliances.
Can anyone help?
Dorst.
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
