Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


ScubaDrew
2014-04-25T15:00:31Z
I'm having trouble connecting to a remote (WAN over VPN) server with hundreds of jobs. The progress bar at the bottom sits at 35% for some time and then i get a message about cannot connect.

If i retry a number of times I can get connected.

Is there a time out value I can increase to allow the client more time to connect?

Thanks,

Drew
Sponsor
Forum information
Support
2014-04-25T16:48:27Z
There is no timeout value - yet. But have you tried turning "Use compression" on and off?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
bbusse
2014-04-25T16:49:39Z
I'm aware of no such option.

However, just to be sure... do have the 'use compression' checkbox enabled? (Manage Servers, connection settings).

EDIT: Just saw 'Support's reply. Jinx! ;-)

Brian
ScubaDrew
2014-04-28T12:09:35Z
Thank you both very much for the suggestion.

I tried turning it on, and now I have some strange behavior where I'm connected but none of the jobs show up.

ScubaDrew attached the following image(s):
ScubaDrew
2014-04-28T12:17:54Z
I rebooted my laptop and now I seem to be connecting with compression enabled.

Thank you both!

Drew
ScubaDrew
2014-05-02T12:48:01Z
Bizarre development on this one. At this time all three users have had to disable compression because upon connection we get no jobs what so ever below the server 'node' in the visual cron client.

I've attached one screen shot of us connected with out compression and answering "no dont re-connect" which leaves us at 35% connected.

And a second screen shot of the blank window w/ compression enabled.

I've shrunk the window size to hide our jobs and keep the screen shot size small.

ScubaDrew attached the following image(s):
Support
2014-05-02T14:59:34Z
The problem is that a specific object that you have contain a value which in combination with compression creates a delimiter between objects sent - this results in a communication problem. Compression of communication maybe was interesting 5 years ago but nowadays, with faster connection, compression may even slow down the connection.

Either way we will handle this in a future update when we rewrite the communication model that we use.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
ScubaDrew
2014-05-02T18:18:48Z
Scroll to Top