On 9/7/06, Nicholas Lee <[EMAIL PROTECTED]> wrote:
On 9/8/06, Bob Doolittle <[EMAIL PROTECTED]> wrote: I've made some progress, by using tftp-hpa and manually start it rather than using inetd. Also realised I needed to turn on udp listening for syslog.
Now that you have syslog running, what did the user.error syslog message sent by the Sun Ray at the end of the packet trace say?
The SR seemed have updated partially, but have still having some tftp issues.
I don't think you're having TFTP issues, aside from the fact that your TFTP server seems to have a stutter. But that shouldn't hurt anything. Your packet trace shows that the DTU retrieved a parms file and decided that it didn't need to download firmware, so presumably it already has the 3.1_32,REV=2005.08.24.08.55 load. The Sun Ray then tried to contact the Sun Ray auth daemon on port 7009/tcp on the server, but that connection attempt was rejected. It then tried to find another Sun Ray server by broadcasting to 7009/udp but got no response. You need to figure out why the server's Sun Ray auth daemon is not accepting connections. The reason for that is very likely to be that the daemon is not running (check by running 'ps -efa | grep authd'). One reason why it isn't running might be that its startup script can't find your Java executable. What happens if you run '/etc/opt/SUNWut/jre/bin/java -version'? What's in the server's /var/opt/SUNWut/log/auth_log file? 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
