Do you care about device access, or only trying to get the
Citrix client to work?
If you just need to get the Citrix client to work, restoring the symlink
as suggested by Darrel Hankerson should be sufficient. Citrix
uses it as a way of uniquely identifying Sun Rays for
the purpose of license and session management.
If you need device access, and you do have NAT, you're out
of luck until the upcoming release provides device access
for NAT'd clients.
The easiest way to tell if you have NAT or not is to run
utwho -c, note the IP for your session, and then press the
three audio keys and note the IP for your client. If they
are the same, you don't have NAT. If they are different,
somebody on the network path between client and server
is doing NAT.
-Bob
Hawes wrote:
I haven't knowingly reconfigured the server for NAT, but am unsure
whether our network person made any other changes. Would changes to the
network backbone have an impact on this? If so, is there a way that I
can check for a NAT myself?
Currently, the SunRay server has the following network configuration:
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
8232 index 1
inet 127.0.0.1 netmask ff000000
ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet xxx.xx.158.63 netmask ffffff00 broadcast xxx.xx.158.255
SunRay Lab 1:
ce1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 192.168.1.1 netmask ffffff00 broadcast 192.168.1.255
SunRay Lab 2:
ce2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
inet 192.168.2.1 netmask ffffff00 broadcast 192.168.2.255
Unused, but ready for Solaris zone
ce3: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 5
inet 0.0.0.0 netmask ff000000 broadcast 0.255.255.255
SunRay Lab 3:
ce4: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 6
inet 192.168.3.1 netmask ffffff00 broadcast 192.168.3.255
I did configure ce3 and use it with a Solaris 10 Zone, but I did not
think that NAT was involved in that.
As per Mr. Hankerson's note, I will check into creating the links with a
cron job, but would like to figure out where things went wrong.
Thank you very much.
Barb
SunRay-Users Digest, Vol 34, Issue 38 Mon, 27 Nov 2006
Message: 2
From: Brad Lackey - US-SW Desktop Product Lead <[EMAIL PROTECTED]>
Is there any NAT translation from your DTU to the SRSS server?
If so, UTDEVROOT won't get created.
There is a limitation where USB devices will not work behind NAT.
------------------------------
Message: 3
From: Craig Bender <[EMAIL PROTECTED]>
Are your Sun Ray's running in a NAT'd setup? If so, then remote devices
will not work.
------------------------------
Message: 4
From: Darrel Hankerson <[EMAIL PROTECTED]>
We had the problem on Solaris 8. The links from /tmp/SUNWut/sessions/
to /tmp/SUNWut/units/ would be missing, which breaks Citrix
connections. We did not resolve the issue, instead using a cron job
to establish the missing links by running through
/tmp/SUNWut/config/dispinfo/.
ORIGINAL QUESTION (SunRay-Users Digest, Vol 34, Issue 37 Mon, 27 Nov
2006)
Subject: [SunRay-Users] UTDEVROOT link incomplete or incorrect?
I could use some advice on figuring out why my system doesn't have the
UTDEVROOT dir/link.
$ echo $UTDEVROOT
/tmp/SUNWut/sessions/8/unit
$ ls -lLd $UTDEVROOT
/tmp/SUNWut/sessions/8/unit: No such file or directory
SYSTEM INFO
Solaris 10 (last patched 8/16/06)
SRSS3.1 (3.1_32,REV=2005.08.24.08.55)
SunRay users able to do everything except use USB devices. They get
"Invalid Sun Ray session" error message from utdiskadm.
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
