You are not logged in.

Dear visitor, welcome to Palo Community Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

ap_OM

Professional

  • "ap_OM" started this thread

Posts: 17

Date of registration: May 21st 2009

  • Send private message

1

Thursday, May 21st 2009, 8:23pm

Jpalo Windows Client: Connection to Server failed

If I try to connect with the JPalo Windows Client to the server I get the following error:

"Connection failed: Connection to "10.0.0.200" failed null"

There is no problem to connect to this server with the Palo-Excel-Plugin with the same specifications and credentials. I tried different users, ports etc., but I can't get a connection.

Any ideas how to solve this problem?

Thanks Alex

arnd

Master

Posts: 73

Date of registration: Sep 6th 2006

  • Send private message

2

Wednesday, May 27th 2009, 12:30pm

RE: Jpalo Windows Client: Connection to Server failed

Hi Alex,

can you provide more information please?
E.g. are you using the Palo Client as a RCP app or as a plugin inside Eclipse?
Furthermore which server version, which port number, is the server running and accessable under 10.0.0.200? ...

Kind regards,
arnd

ap_OM

Professional

  • "ap_OM" started this thread

Posts: 17

Date of registration: May 21st 2009

  • Send private message

3

Thursday, June 4th 2009, 1:30pm

thanks for your answer:

some more infos:

I use the JPalo Windows Client (not a Eclipse plugin)
I use Palo-Server 3.0 (community) and the JPalo Windows Client 2.0
portnumber = 1235

The server is running and the database is accessable under 10.0.0.200 via the PALO-Excel-Plugin - that's why I don't understand why I can't access my databases via Jpalo with the same specifications as in the PALO-Excel-Plugin

kind regards

Alex

arnd

Master

Posts: 73

Date of registration: Sep 6th 2006

  • Send private message

4

Thursday, June 4th 2009, 2:57pm

Hi Alex,

I think the problem is the port number. Can you set it to a value higher 2000?
The point is that the palo client supports a very old legacy palo server, which is not available anymore. This server version used ports up to 2000 only. So if you use the port number 1235 the client thinks it should connect to this legacy server...

Kind regards,
arnd

ap_OM

Professional

  • "ap_OM" started this thread

Posts: 17

Date of registration: May 21st 2009

  • Send private message

5

Thursday, June 4th 2009, 3:16pm

Hi arndt,

thanks a lot. I'll try that.

kind regards,
Alex

Rate this thread