Peeler, Elliott schrieb:
% ls /tftpboot | grep 00144F5748E5 SunRayP8.00144F5748E5 SunRayP8.00144F5748E5.parms% cat /tftpboot/SunRayP8.00144F5748E5.parms version=GUI4.2_140993-01_2010.01.21.17.35 revision=3 barrier=420 % utquery 192.168.206.10 terminalID=00144f5748e5 terminalIPA=192.168.206.10 model=SunRayP8 currentAuth=192.168.254.51 currentFW=GUI4.1_139548-01_2008.12.08.15.16 currentBarrier=325 currentBarrierLevel=325 currentMTU=1500 Subnet=255.255.255.0 Router=192.168.206.254 Broadcst=192.168.206.255 LogHost=192.168.254.51 FwSrvr=192.168.254.51 tftpSrvr=192.168.254.51 FWservType=conf configMTU=1500 confNetType=Static confIPA=192.168.206.10 confSubnet=255.255.255.0 confRouter=192.168.206.254 confBroadcst=192.168.206.255 confTftpSrvr=192.168.254.51 confLogHost=192.168.254.51 confServers=192.168.254.51 stopqon=0 bandwidth=100000000
That all looks sane - except that the DTU apparently failed to tftp the parms file. As a result it doesn't know about the newer firmware version.
As you have verified that tftp is running on the server I don't see anything obvious either.
You could try to snoop tftp on the server during a DTU restart to see if requests from the DTU come in and get a reply.
Regards - Jörg -- Joerg Barfurth Software Engineer mailto:[email protected] Desktop Technology http://blogs.sun.com/joergb/ Thin Client Software http://www.sun.com/software/sunray/ Sun Microsystems GmbH http://www.sun.com/software/vdi/ Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten Amtsgericht Muenchen: HRB 161028 Geschaeftsfuehrer: Jürgen Kunz _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
