On 11/17/06, Sean Clarke <[EMAIL PROTECTED]> wrote:
My Sun Ray 2 starts and displays code 21, then it displays 22D (paremeters
received) and shows it's IP address - nothing more happens and then it reboots
and the cycle continues.

So it's trying (code 22, see the Troubleshooting section in the SRSS
Admin Guide) and failing to make contact with the Sun Ray auth
daemon running on the Sun Ray server.

Do you have an auth daemon running?  Do 'ps -efa | grep authd', and
if that doesn't show a Java process auth.utauthd.utauthd then look in
/var/opt/SUNWut/log/auth_log for clues.

Most likely your /etc/opt/SUNWut/jre symlink is not pointing to a
suitable Java runtime.  What is the result of running
'/etc/opt/SUNWut/jre/bin/java -version'

What does 'ls /etc/rc5.d/*ut*' show?

here is some information that might be useful:

That all looks OK.

I have noticed that the utstoraged shows that the storaged service keeps
restarting (every few seconds) but I don't think that is my problem at this
time.

That would be another symptom of a missing authd.

Quick question - on the setup it asked for the "router" IP address, what IP
what is this refering to? I have set it to be my internet/firewall router,
but in hindsight I don't know why it would need to know that as it connects
directly to my server.

The Sun Ray needs a router address in order to send traffic to
destinations that aren't on its local subnet.  If the Sun Ray is
only required to talk to on-subnet destinations (as it is in your
deployment) then the router address you give the Sun Ray
is unimportant, it will never be used.

OttoM.
__
ottomeister

Disclaimer: These are my opinions. I do not speak for my employer.
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to