My user, (Firefox 1.5 Windows XP) gets often a Dialog Box:
title: "SOAP Fault -Secure Global Desktop client"
Text:
"The following SOAP Fault was recieved from the server:
Invalid connection cookie.
Please contact your Secure Global Desktop administrator.
"
(Thats me!)
Button: "Ok"
How can I help him?
I often see this message when a SGD Array has been broken?
Do you have an array if so try to detach and attach all the secondaries and see if the problem resolves.
To check if the array is working correctly try an extended status message:
/opt/tarantella/bin/tarantella status --verbose --byserver
Its a "Stand-Alone" Server.
/opt/tarantella/bin/tarantella status --verbose --byserver
gives:
Health check:
- centos: Accepting peer connections.
- All responsive servers report consistent array topology.
Contacting centos for server status.
Contacting centos for application server information.
desktop:
- Array member (secondary): Accepting standard and secure connections.
- Last started: Thu Jul 06 22:14:19 CEST 2006
- Webtop sessions (0):
- Emulator sessions (0):
.../_ens/o=digitec/ou=d3-linux/cn=vm-d3p-dev:
- Application server.
- Emulator sessions (1):
- X Protocol Engine: 1
Hi,
I am afraid your user is loosing it's network connection. Please check the Secure Global Desktop Client options are set to never reconnect. This is the way it should be set, otherwise he might not be able to reconnect to it's sessions.
Regards,
Arno Staal
Divider B.V.
Hello,
you say you are using a single machine as a server, try this:
sometimes with a single machine people don't set up full naming services. you need (or should have) DNS entries for your machines.
If you don't have full DNS entries then put them into your host file. this includes any windows servers you are running apps from and any windows clients you may be connecting from.
you may even want to handle DHCP connections in the following way. if you have 20 DNS connections, then make entries in the hosts file like this (example only, use your own network address):
192.168.1.100dhcp100
192.168.1.101dhcp101
192.168.1.103dhcp103
etc. the name is not important. just the entry.
this seems to have worked for me in connecting from hardwired and dhcp addresses.
regards,
tucker
