Hi Nicholas:

        I can't give you specifics (I'm not familiar with running SRSS on
Linux), but here's one possibility to look into:

        If you look through the docs, you'll see mention of "Shared
Interconnect/Sun Ray on a LAN" and "Dedicated Interconnect" (or
something like that).  Apparently the early Sun Rays needed to be on a
dedicated network fabric, and then later Sun Rays could be used on a
plain old network.

        The good news: the firmware will automatically be upgraded when the SR1
is connected to a current version of SRSS.  The bad news: The older
firmware only works on the dedicated interconnect.  So what you have to
do is setup a second ethernet port as a dedicated interconnect and plug
the Sun Ray into it (personally I used an Ethernet crossover cable, but
if you have a spare hub around that would probably work too).  The
firmware will update, then you can use it on the LAN interconnect.  In
your case, i don't know how that will react with running in a vmware
environment.  Matter of fact, I don't know how SRSS in general reacts to
vmware.

        I've bought two Sun Rays off eBay, and they've both needed this
treatment.

        I mentioned this on my blog at:

http://jroller.com/page/trasukg?entry=tried_a_sun_ray_wow

Cheers,

Greg.

On Mon, 2006-09-04 at 23:07, Nicholas Lee wrote:
> I picked up a couple second hand SR1s of Trademe (like ebay for NZ) to
> expt with SRSS and rdesktop, and I'm having trouble getting them
> going.
> 
> I've install Centos 4.4 in a vmware server guest, on top of a 2
> interface machine. The SR1 and CentOs host with SRSS 3.1.1 installed
> are on a seperate bridged network segment, eth1.
> 
> I can see the requests coming for the SR client, but it doesnt seem to
> find the srss server.
> 
> 14:52:27.996862 IP centi-i.field.afs3-rmtsys >
> 224.101.101.101.afs3-rmtsys:  rx type 114 (315)
> 14:52:29.780210 rarp who-is 08:00:20:c3:16:b9 (oui Unknown) tell
> Broadcast
> 14:52:30.280055 rarp who-is 08:00:20:c3:16:b9 (oui Unknown) tell
> Broadcast
> 14:52:30.280326 IP 0.0.0.0.bootpc > 255.255.255.255.bootps:
> BOOTP/DHCP, Request from 08:00:20:c3:16:b9 (oui Unknown),
> length:                                 548
> 14:52:47.285748 IP 0.0.0.0.bootpc > 255.255.255.255.bootps:
> BOOTP/DHCP, Request from 08:00:20:c3:16:b9 (oui Unknown),
> length:                                 548 
> 
> At this point I can't tell if the DTUs are hardwired some way or I'm
> stupid and can't set the server up correct.  What's the best way to
> figure this out?
> 
> Thanks
> Nicholas
> 
> 
> ______________________________________________________________________
> _______________________________________________
> SunRay-Users mailing list
> [email protected]
> http://www.filibeto.org/mailman/listinfo/sunray-users
-- 
Greg Trasuk, President
StratusCom Manufacturing Systems Inc. - We use information technology to
solve business problems on your plant floor.
http://stratuscom.com

_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to