Welcome, Guest
Please Login or Register.    Lost Password?
Go to bottomPage: 12
TOPIC: Unix client problem
#258
Unix client problem 13 Years, 7 Months ago Karma: 0
Hi,
We connect to the Go Global server via Windows Clients and it works fine. Now I want to connect to the same server via a Unix Client but I cannot setup the connection. It's timed out. Is there a difference to connect from Windows and Unix Clients ??
Many thanks
wimdeg
Fresh Boarder
Posts: 4
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#267
Re: Unix client problem 13 Years, 7 Months ago Karma: 2
Hello,

Generally speaking the windows client and the native unix client are very similar. I would make sure that you have the same version, as protocol incompatibilities could cause issues like these to surface.

Also, it might be worth verifying that your UNIX client machine can successfully connect to the server. You can do this using telnet:

Code:

telnet server.some.domain 491



If you see something like:

Code:

Trying 10.10.10.10...
Connected to server.some.domain.
Escape character is '^]'.



Then the connection was successful. You can press CTRL-] and type "q" followed by return to close the connection.

If you see something like:

Code:

Trying 10.10.10.10...
telnet: Unable to connect to remote host: Connection refused



Then the connection was not successful, and you should investigate any network issues and verify that the server in question is in fact running the 'gold' daemon.

(Note that "10.10.10.10" is an example IP address, yours will likely be different, and "Connection refused" is just an example of what might be returned. You may also see any number of other errors.)

Troy
troy
Administrator
Posts: 231
graphgraph
User Offline Click here to see the profile of this user
Gender: Male Birthday: 01/14
The administrator has disabled public write access.
 
#269
Unix Client Problem 13 Years, 7 Months ago Karma: 0
Thanks for the reply, but I did this already and the connection to the port 491 is fine. Anything alse??
What do you mean with the 'gold' daemon??
Thanks,
Wim
wimdeg
Fresh Boarder
Posts: 4
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#272
Re: Unix client problem 13 Years, 7 Months ago Karma: 2
The 'gold' daemon is our authentication and session management process ('gold' stands for "GraphOn Login Daemon"). I was suggesting that you should check the output of the "ps" command on the server and verify that the "gold" process was in fact running.

What is the client and server UNIX platforms you're trying to establish the connection with?

Thanks,
Troy
troy
Administrator
Posts: 231
graphgraph
User Offline Click here to see the profile of this user
Gender: Male Birthday: 01/14
The administrator has disabled public write access.
 
#283
Re: Unix client problem 13 Years, 6 Months ago Karma: 0
Troy, sorry for the late response.
The client platform is Solaris 8.0 and the server platform is HP-UX B 11.11 9000/800

This other info i've found
license server UP (MASTER) v6.1
Vendor daemon status (on hostname):
graphon: UP v6.1
Feature usage info:
Users of bridges: (Total of 35 licenses available)

PS: Is there a difference between to 'gold' process and the 'graphon' process

As we are not the admins it takes a while to check with the administrators.
Regards,
Wim
wimdeg
Fresh Boarder
Posts: 4
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#284
Re: Unix client problem 13 Years, 6 Months ago Karma: 2
Hello Wim,

The "gold" process is the daemon that manages authentication, launching of sessions, and so on. It is the core of the product. The "graphon" process is the license management daemon (referred to as the "vendor daemon" by the license management system). Both of those should be running. The fact that you can telnet to port 491 and get an established connection confirms that.

At this point, I'm not really sure why you are having problems. Sometimes we'll get a report like this, and it will turn out to be a problem where the connection was being established against the wrong port, or will be using SSL on the TCP/IP port, etc. But it's difficult to know the right questions to ask to ascertain that sort of problem. Is there anything you're doing different between the Windows client and the Solaris client?

Also, can you send us the ${GOGLOBAL_ROOT}/etc/gold.log, showing the messages that were logged during a failed connection attempt vs. a successful one?

Thanks,
Troy
troy
Administrator
Posts: 231
graphgraph
User Offline Click here to see the profile of this user
Gender: Male Birthday: 01/14
The administrator has disabled public write access.
 
Go to topPage: 12
Moderators: troy, Andyl