Client Timeout error

[DavidSparke]

Hi,

Anyone know why client timeout errors occur when attempting to open a remote cube..?
I've tried all the obvious stuff like increasing the network timeout on the connection, checking the processing settings on the server, but still no joy.

I can see the cubes held in the connection but as soon as I try and open one (even the great outdoors) it sits there and eventually throws up a timeout error.

Everything works ok, on our test server which is on the same part of the network, same ping responses, and tracert routes.

I have noticed that netstat -a on the problem server is very slow compared to the one that works, that may suggest problems resolving ip names from the DNS..?

I've even tried forcing the server to send over a fixed port rather than pick one between 1024 and 5000, but still no luck.

Help.....!!


cheers,

Dave Sparke

 

[RVLF]

You can mdify the CGI Timeout if you are in Version 7.

 

[collierd]

Where do you modify CGI timeouts in series 7..?

 

[WallSysAdm]

We have the exact same problem ! did you find any solution ?

Thobias

 

[dm21]

Hi There,

Are you using Enterprise sever for remote connection?

Do you have problem on performance? We are facing performance problem on remote connection through enterprise server. The same cube is faster with the local connection.