Sun Ray Connector proxy : Child closed socket prematurely, session shutdown

Dear All,
I'm using SRS 5 & SRWC 2.2 :
$ pkginfo -l SUNWuttsc
   PKGINST: SUNWuttsc
      NAME: Sun Ray Connector for Microsoft Windows Operating Systems (opt)
CATEGORY: system,sunray
      ARCH: i386
   VERSION: 2.2_32
   BASEDIR: /opt
    VENDOR: Sun Microsystems, Inc.
      DESC: Commands, configuration, resources and Man Pages
    PSTAMP: SunOS_5.10_20091021175007
INSTDATE: févr 05 2010 10:34
   HOTLINE: Please contact your local service provider
    STATUS: Installation complète.
     FILES:       26 chemins d'accès installés
                   9 répertoires
                  10 exécutables
                   1 exécutables setuid/setgid
                9037 blocs utilisés (env.)
The SRWC crash and restart immediately...
As you can see I've some log like this :
Feb 7 03:03:15 SRS Sun Ray Connector proxy:[18056]: [ID 855542 user.error] Child closed socket prematurely, session shutdown
Feb 7 03:03:15 SRS Sun Ray Connector proxy:[18089]: [ID 855542 user.error] Child closed socket prematurely, session shutdown
Feb 7 03:03:23 SRS Sun Ray Connector proxy:[18254]: [ID 855542 user.error] Child closed socket prematurely, session shutdown
Feb 7 03:03:23 SRS Sun Ray Connector proxy:[18214]: [ID 855542 user.error] Child closed socket prematurely, session shutdown
Feb 7 03:03:23 SRS Sun Ray Connector proxy:[18219]: [ID 855542 user.error] Child closed socket prematurely, session shutdown
Feb 7 03:03:23 SRS Sun Ray Connector proxy:[18221]: [ID 855542 user.error] Child closed socket prematurely, session shutdown
Feb 7 03:03:23 SRS Sun Ray Connector proxy:[18220]: [ID 855542 user.error] Child closed socket prematurely, session shutdown
...I'm using a separate DHCP on LAN. DTU & TSE (W2K8) are working 95% of time and sometime and randomly, one DTU has a full black screen. The only way to get the login screen of win 2K8 is to reset his own session.
Help will be really appreciated.
Florent.

I have the same issue . . .
1. Sun Ray 5 (Sun Ray 4.2)
2. SRWC 2.2
3. Solaris 10 u9 X86 on two x2200
4. Terminal Server on Win2K3 R2 Standard x64 Edition SP2
I have a handful of users and they all logon the same way, which is to enter username & password then I have the following lines at the end of the users' individual .dtprofile file . . .
<begin snip>
DTSOURCEPROFILE=true
/opt/SUNWuttsc/bin/uttsc -b -m -O -u uname 192.168.100.29
exit
<end snip>
Of course 'uname' is actually the user name followed by the Terminal Server IP address and as you can see I am using the '-O' option, but every morning all the users on a server have their Sun Ray sessions reset and I find this in the messages file . . .
Mar 16 09:38:31 sunraya Sun Ray Connector proxy:[12941]: [ID 855542 user.error] Child closed socket prematurely, session shutdown
. . . . Using cron, I reset the Sun Ray service twice a day on both servers at 7AM and 7PM . . .
# cat /sunray-restart.script
# This is to restart SunRay 5 service due to
# what I think may be a memory leak that disconnects
# the SunRay Windows Connector every day
/opt/SUNWut/sbin/utrestart -c
echo "#" >> /var/adm/messages
date >> /var/adm/messages
echo "#" >> /var/adm/messages
echo " RESTARTING SUNRAY SERVICE " >> /var/adm/messages
echo "#" >> /var/adm/messages
echo "#" >> /var/adm/messages
. . . But this does not appear to having an affect.
I will be looking around the forums for any other bits of information about this. The "Known Issues" can probably be found in the Release Notes.

Similar Messages

Sun Ray Connector proxy i on debug mode - VDI 3.1.1 -

Hi,
On each connection to a windows session with VDI I use the Sun Ray Connector Proxy, each user launch a daemon called uttcpd everytihnings is ok but this daemon is launch on debug mode so my /var/ad/messages is full of usesless debug message. I don't find any option or configuration file on the doc to change the daemon logging mode.
Thanks per advance for your help,
Sylvain.

I have the same issue . . .
1. Sun Ray 5 (Sun Ray 4.2)
2. SRWC 2.2
3. Solaris 10 u9 X86 on two x2200
4. Terminal Server on Win2K3 R2 Standard x64 Edition SP2
I have a handful of users and they all logon the same way, which is to enter username & password then I have the following lines at the end of the users' individual .dtprofile file . . .
<begin snip>
DTSOURCEPROFILE=true
/opt/SUNWuttsc/bin/uttsc -b -m -O -u uname 192.168.100.29
exit
<end snip>
Of course 'uname' is actually the user name followed by the Terminal Server IP address and as you can see I am using the '-O' option, but every morning all the users on a server have their Sun Ray sessions reset and I find this in the messages file . . .
Mar 16 09:38:31 sunraya Sun Ray Connector proxy:[12941]: [ID 855542 user.error] Child closed socket prematurely, session shutdown
. . . . Using cron, I reset the Sun Ray service twice a day on both servers at 7AM and 7PM . . .
# cat /sunray-restart.script
# This is to restart SunRay 5 service due to
# what I think may be a memory leak that disconnects
# the SunRay Windows Connector every day
/opt/SUNWut/sbin/utrestart -c
echo "#" >> /var/adm/messages
date >> /var/adm/messages
echo "#" >> /var/adm/messages
echo " RESTARTING SUNRAY SERVICE " >> /var/adm/messages
echo "#" >> /var/adm/messages
echo "#" >> /var/adm/messages
. . . But this does not appear to having an affect.
I will be looking around the forums for any other bits of information about this. The "Known Issues" can probably be found in the Release Notes.

Sun Ray connector interface is invalid

I think I have some kind of configuration problem with my Sun Ray server. When I try to run the utadm -A "I.P. address" command, it comes up at the end with a message about the "Sun Ray connector interface is invalid" or something like that. The problem seems to be with this because the Sun Ray server will not update the firmware on the Sun Ray Clients. Even using the utfwadm -A -e "MAC address" to force an update it just sets it up in the dhtptab.conf file with the macro to download the firmware but when I power cycle the Sun Ray client it does not update the firmware. The only thing I can think of is that it must have something to do with the "Sun Ray connector interface is invalid" error that is preventing it from updating.
The DHCP server will also not update the "LeaseTime" nor the "LeaseNeg" options that I have configured.
Can someone tell me how to get rid of the "Sun Ray connector interface is invalid" error and/or if this might be what is preventing my firmware updates to my Sun Ray clients?
Thanks,

I have the same issue . . .
1. Sun Ray 5 (Sun Ray 4.2)
2. SRWC 2.2
3. Solaris 10 u9 X86 on two x2200
4. Terminal Server on Win2K3 R2 Standard x64 Edition SP2
I have a handful of users and they all logon the same way, which is to enter username & password then I have the following lines at the end of the users' individual .dtprofile file . . .
<begin snip>
DTSOURCEPROFILE=true
/opt/SUNWuttsc/bin/uttsc -b -m -O -u uname 192.168.100.29
exit
<end snip>
Of course 'uname' is actually the user name followed by the Terminal Server IP address and as you can see I am using the '-O' option, but every morning all the users on a server have their Sun Ray sessions reset and I find this in the messages file . . .
Mar 16 09:38:31 sunraya Sun Ray Connector proxy:[12941]: [ID 855542 user.error] Child closed socket prematurely, session shutdown
. . . . Using cron, I reset the Sun Ray service twice a day on both servers at 7AM and 7PM . . .
# cat /sunray-restart.script
# This is to restart SunRay 5 service due to
# what I think may be a memory leak that disconnects
# the SunRay Windows Connector every day
/opt/SUNWut/sbin/utrestart -c
echo "#" >> /var/adm/messages
date >> /var/adm/messages
echo "#" >> /var/adm/messages
echo " RESTARTING SUNRAY SERVICE " >> /var/adm/messages
echo "#" >> /var/adm/messages
echo "#" >> /var/adm/messages
. . . But this does not appear to having an affect.
I will be looking around the forums for any other bits of information about this. The "Known Issues" can probably be found in the Release Notes.

Sun Ray Connector for Windows OS 2.3

Hi,
I use Sun Ray Connector for Windows OS 2.3.
I want to show in windows logon screen ''domain logon'', now show in windows logon screen ''local server logon''.
What the uttsc parameters I must use?
I try the use in Sun Ray Connector for Windows in filed parameters:
for example:
domain_name_serwer -d my_domain but session sun ray all the time restart.
If I dont use -d my_domain in Sun Ray Connector for Windows:
for example:
domain_name_serwer it´s ok (but show in windows logon local serwer logon).
Thanks

The-d option requires the -u option.
In what way are you using uttsc and what version of Windows are you connecting to?

Sunray 4.2 Connector Proxy messages

I recently upgraded one of the 5 sunray servers in a failover group from SRSS 4.0 to SRSS 4.2 All of the 250+ sunray sessions connect via a kiosk script to one of 4 windows terminal server farms running win 2003 and win 2003 R2.
I upgraded the SRWC (2.2) as well as the SRSS (4.2). In addition I have also installed SRSS 4.2 patch (140994-03), Kiosk 4.2 patch (143535-01) and SRWC 2.2 patch (143215-03) All servers are X4100 running Solaris 10 update 8.
SInce the upgrade, I have had no complaints from users, but my /var/adm/messages file is filled with entries every few minutes as shown below :
Sun Ray Connector proxy: [12349] : [ID 855542 user.error] Child closed socket prematurely, session shutdown.
Sun Ray Connector proxy: [12553] : [ID 855542 user.error] Child closed socket prematurely, session shutdown.
Sun Ray Connector proxy: [12588] : [ID 855542 user.error] Child closed socket prematurely, session shutdown.
Sun Ray Connector proxy: [12620] : [ID 855542 user.error] Child closed socket prematurely, session shutdown.
Sun Ray Connector proxy: [12652] : [ID 855542 user.error] Child closed socket prematurely, session shutdown.
Sun Ray Connector proxy: [12684] : [ID 855542 user.error] Child closed socket prematurely, session shutdown.
Also I have noticed that the upgraded server doesn't seem to have as many sessions as the other 4.0 servers
Any ideas /suggestions much appreciated.
Frank
Auckland, New Zealand.

Sorry for later answer, we are deploying a vSphere and things got complicated.
Nice to meet Frank (Paco, Curro ...) ;-). You're one of 'the Line'!!!, CADIZ! hehe
How small is this world ... I'm from Granada, you are welcome to my land ..
On the subject of black screens, I can tell you that my infrastructure consists of two servers in cluster with SSRS and SRWC. On the back I have a Windows Terminal Server farm with two servers.
At first, all servers were virtualized with VMware 3.5, but later changed the SSRS per physical server (Sun Fire X2100 (x86) with the latest version of Solaris and the latest patches sunray), but the problem persists. Since I can only remove the WTS and pass it to the new platform vSphere.
As I said in my first message, after a short period of inactivity, the DTU are blocked without responding to the mouse or keyboard, although the WTS session is still active, because I can connect from the server itself.
I do not know if you can guide me in some way things look, to cancel, etc.
First of all, thank you very much for your interest, even calling to SUN.
Nice to talk to you ...
Jose Garrido
Granada
SPAIN

Sun Ray Server x64 or T2?

Hi,
I have been searching around looking for some advice/benchmarking for what hardware is best for Sun Ray servers. My plan is to use the Sun Ray VMware View Connector and so the Sun Ray server will only be managing the sessions rather than providing the desktop.
Therefore, would a T2 system give more consistent performance than a x64 system? and, how many Sun Ray sessions could be expected to be managed by a T5120 or a X4100?
Finally, is running the Sun Ray server in a VM a supported config?
cheers,
Simon.

We have found that x86 series server far out strip the T series boxes for Sun Ray.
A X4100 with 8GB RAM should be able to handle 100 odd sessions. We build for our Customers on a model of around 125 sessions per server. We used to use X4100 but have moved to X4140, if you bumped the RAM on these to 16GB you should get more.
Sun Ray runs poorly under VMware and if you need to go down that route run lots of little Sun Ray servers with no more than 20 odd DTU per server.
Hope this helps

Sun Ray device sharing among DTU

Hi All,
Anyone has experience on how to share attached device of a DTU among other DTUs in the same LAN? or perhaps some pointers if any? Thanks in advance.
Cheers,
Jonathan

I tried getting my iphone to connect up. It is recognized but
there is some kind of error so it doesn't get seen my itunesIt's because iPhone USB device appear as isochronous USB device and Sun Ray Connector USBR feature doesn't support isochronous devices yet. I am not sure if blackberry is also an isochronous USB device or not.

Sun Ray USB Redirector 1.1

Hi Guys,
I am using the Sun Ray Redirector 1.1 on my test XP VM machine. I am trying to connect a blackberry device via the DTU's USB slot but it only plugs and plays as a "Sun Ray Generic device".
Has anybody got this working?
Many thanks.
Gavin.

I tried getting my iphone to connect up. It is recognized but
there is some kind of error so it doesn't get seen my itunesIt's because iPhone USB device appear as isochronous USB device and Sun Ray Connector USBR feature doesn't support isochronous devices yet. I am not sure if blackberry is also an isochronous USB device or not.

Sun Ray Kiosk Mode Timeout Settings

For the Kiosk mode I see two different places for timeout settings. I have copied them in below. My issue is that I am seeing a lot of Login Greeter/Idle Sessions and I think the first "Timeout" setting should be set lower, but I don't want to disconnect good sessions.
One here in the admin gui under "Advanced" and "kiosk mode"
Session:
Sun Ray Connector for Windows OS
Timeout:
24000 seconds
Under that is a place for "Arguments"
where I see:
-t 3600

I recreated the kiosk user accounts (utconfig -k) and the problem has been resolved. Thanks to those who sent comments.

Sun Ray Windows Connector Terminal Services licenses issue

Hi!
I've installed the latest Sun Ray 4 09/07 as well as the Windows Connector (srwc) recently released on a machine. I've followed the instructions given in the installation guide. But when 'uttsc' is executed I received the following error message.
"No Terminal Services licenses are available"
I have no issue in connecting to other Windows server (say windows-02) only to this particular Windows server (windows-01). Surprisingly, I have no problem 'uttsc'-ing to windows-01 using pre-existing Sun Ray 4. Any idea why and how to resolve this?
Appreciate anyone who responds. Thanks.
Regards,
Jonathan

What Terminal Server license model are you using? And what does Windows Terminal Server License Manger show for number of licenses in use and availble?

Smart Cards slow with Sun Ray Windows Connector

I'm succesfully using smart cards to log on to Windows 2003. But the problem is that it's very slow!
If i enter a wrong pin code, its fairly quick to respond with an error but when entering the right one it takes like 13-15 seconds to log on. The smart card slot on Sun Ray 2 is flashing all that time, so it seems like it's reading the certificate takes that long?
Any ideas how to make it quicker?

I have done the same setup with SunRay 170.
Approx the same delay is experienced with my setup.
When I meet my Card Vendor next time around I will ask about
how many times the CERT is read.
The Sunray 2 is faster , alot faster than sunray 170 so the delay
must be the speed that card transactions can be performed.
//lars

Sun Ray Smart Card User Authentication

Hello All,
I recently installed SRSS 4.1 I created 6 users for testing, 3 of which use SRWC to connect to Windows VM's. My problem is with the smart cards. They are required for the user access the SunRay and that part works, however it doesnt seem the cards are binded to any particular user. For instance any of the 6 cards can be inserted and logged into any of the accounts (correct username and pw of course). I thought that each card was linked to one user account which provided increased security. The way it is working now is kind of useless.
Any Suggestions?

Hi,
It depends very much on which type of card you are using and what authentication mechanism you set up.
The SIMPLE card that SUN ships as the Sun Ray card does AFAIK not have any options for personalisation on the Card.
What you can do with it is to use AMGH ( Advanced Multi Group Homeing is a SunRay server feature ) and tie
the CARD ID to a user name. So that when the card is inserted in the Sun Ray , you user ID will be pre-entered in the
UNIX login dialoge. But this does not prohibit the card from being used to log in as a differernt user ID .
If you use the Sun VDI 2.0 ( virtual desktop infrastructure ) software. You need to Populate the Sun Ray Server DataStore
with the Names that will be used as machine names of the virtual PC's in VMware. It is almost nessesary that the
User name is equal to the Vmware Virtual Machin name.
So in VDI the the Username in SRS-DS assoiated with a CARD becomes the virtual Machine name.
( this is not the same as the user name in AMGH but keeping the two the same probably limits the confusion )
If you get hold of a more advanced Public KEY Interchange card, it is possible to set up PKI login to a windows session
this involves some software in the windows XP client to read the smart card in the Sun Ray and to authenticate the card
whit PKI to a known certificate that you have stored for the Card in a Directory ( Active Directory or some other one )
The Sun Ray server can be loaded with the PC/SC - bypass software that allows a Windows server/client using the
Sun Windows Connector RDP software, to read and write directly to the SmartCard inserted in the SUnRay.
The Virtual PC or terminal server will work with the Smartcard reader as if it was local on the WIndows machine.
The "Active CARD" company has such a solution amongst others.
Regards
//Lars

Is Sun Ray a suitable solution for system administrators?

My company is deciding if Sun Ray can be a viable solution for system administrators for additional level of security since Sun Ray clients are diskless...less worries about malware or virus...etc.
However, looking through Sun's available thin client machines, there is no selection of laptop form. As you can guess, sysadmins are mostly remote and on the go...it cannot be expected that they are always at their desks or homes to access the thin client machines. I understand the availability of the web client solution...however, have my doubts about that and how much would sysadmins actually embrace it.
On the other hand, the inability of copy & paste as they are currently doing with traditional thick clients can be problematic too. One use case is when they test and build config on their desktops (say notepad), then upload to server hosts...or opposite, when they need to download logs to their machines and investigate...
I am not going into questions about support of OS X and other tools sysadmins usually use...since the support of true remote access will be the biggest hurdle up front.
Any comments?

Hmmm. Very late to this conversation, but couldn't help to throw some change into the hat.
For casual use of light-weight, non-power hungry applications, running apps via SGD over a Sun Ray (soft client or not) is probably ok. But if you were to try to do this for normal users who need PC-like performance, you'd be delusional. Display information will travel over the network 3 times and you can't take advantage of any of the new, faster graphics capabilities of the newer Sun Ray's when you introduce SGD as the means to access Windows desktop applications.
To be explicit:
Sun-Ray -> Sun Ray Server uses ALP.
Sun Ray Server -> SGD uses AIP.
SGD Server -> Windows Server uses RDP.
If you deploy this widely, better go buy some stock in Cisco.
I'd use SGD only for remote PC/Mac/Unix users who need to bounce in from the wild west.
I'd use Sun Ray -> Sun Ray Servers + Windows connector (uttsc) for thin client access.

Sun Rays with VDI 3.1 - Black screen after periods of inactivity

Running VDI 3.1 with bundled versions of SRSS on three servers in a cluster running Solaris 10 with VSphere as a desktop provider - also using meta-kiosk with all smartcards configured to run "VDA" script when inserted, DTUs require registered cards.
Bit of a strange issue that is unfortunately not always reproducible:
After what seems a random period after having removed a smartcard from a DTU (if still logged into a Windows session, or after disconnecting it) sometimes as short as 20mins, sometimes only after overnight, upon reinserting the card, the VDI login screen does not always appear immediately (as should happen), but instead a black screen with a moveable mouse pointer is shown. This persists for almost exactly 2 minutes whenever it happens, then the VDI screen appears. If you manually kill the session from the admin web-interface and power-cycle the Sun Ray, it will pop up immediately as expected.
At times, the VDI screen does simply appear immediately as expected, at others this 2-minute black screen first...
You can often force the behaviour on a working VDI login screen by choosing "More options - Quit" - this will often trigger the black screen/2 minute delay. At other times quitting in this manner does not reproduce the error and the VDI login screen appears immediately.
I've researched this for a couple of weeks, and a lot of bugs mentioning "black screens" pointed towards problems with uttsc-bin - I've already applied the patch here: http://sunsolve.sun.com/search/document.do?assetkey=1-21-143215-03-1 to no avail.
I assume that it possibly is nothing to do with the Windows connector, since it's really the VDI login screen that is not appearing in a timely manner and Windows logins/sessions always start/resume immediately after logging in from the VDI screen.
Can anyone offer any help?

Never figured out what was causing this, but an upgrade to VDI 3.2 has fixed it (for now at least!)

Black screen, Sun Ray DTUs

Users have complained that if they stop typing or moving the mouse the screen goes black within 30 secs or so.
I verified that SUNWxscreensaver-hacks-gl and SUNWxscreensaver-hacks were removed from the Solaris 10 U7 OS.
All sessions are set for Sun Ray Windows Connector kiosk only mode.
If I delete the Sun Ray Desktop under Desktops and then Terminate the user under Sessions the user has no problems. Though later in the day or maybe a couple of days later somewhere else, another Sun Ray DTU encounters this same issue. I have noticed this now at 3 different sites and we have the latest patches and run SRSS 4.1 and SRWC 2.1.
Any ideas out there?

I too have noticed this issue. The behavior is the same and my attempts to fix it(firmware screen blanking, monitor settings, Windows settings) have done nothing.
Also using full screen Windows 2008.

Sun Ray Connector proxy : Child closed socket prematurely, session shutdown

Similar Messages

Maybe you are looking for