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


gencap
2011-01-14T02:31:38Z
Hello,

I have VisualCron (5.6.9) installed on a couple of machines and everything works on Windows Server 2008. I can connect to those VC servers with no issues. However when I try to connect to VC installed on Win7 64, I get this error:

Connection failed to 'dataloader'. Connection failed with error 'Connection refused. (10061)'

All the obvious things like the port seem to be setup correctly, and the configuration should be identical to the working installs on Windows Server.

Is there a setting that I need to change in Win7 to open up the connection? Or configure something specific in VC?

Thanks.

Sponsor
Forum information
Support
2011-01-14T10:01:00Z
If you connect remotely you need to have port 16444 open to the machine. I guess you can connect locally?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
gencap
2011-01-14T20:16:00Z
Still not getting it to work, but there is some more information.

I can connect to the win7 machine from a WinXP machine. It seems like it's only when connecting from Win7 to Win7 or Server2008 to Win7 that there is an issue.

Is there anything else that you can think of to try?
Is there additional logging that we can enable to get more info about what is refusing the connection?

Thanks.

Support
2011-01-17T09:52:51Z
Try opening a command prompt from the machine you can't connect to and write:

telnet servername 16444

Also, try

telnet ip 16444

If none of these works there seems to be the local firewall blocking outgoing communication (if you are able to connect remotely from another machine to this target machine).
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
gencap
2011-01-18T07:18:09Z
Turns out the issue was related to the connection, but not to the port directly. It had to do with IP6 vs. IP4. Newer machines were resloving on our our DNS to ip6 which didn't connect. Older machines resolved to IP4.

We made sure that all the machines reslove to IP4 and we can now connect.

But there still seems to be some issue with IP6. Not sure if you have seen it before.

Thanks for the help!
Support
2011-01-20T10:38:49Z
Could you test if it is related to server or client?

For example:

1. if you open a command window on server with IPV6. Do you successfully connect when writing:

telnet localhost 16444
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
gencap
2011-01-28T17:55:11Z
Support wrote:


1. if you open a command window on server with IPV6. Do you successfully connect when writing:

telnet localhost 16444



Yes. That seems to work fine.
Support
2011-02-01T14:50:38Z
We have a test version which should not replace your production machine but it would be interesting if you could connect with this version:

http://neteject.com/down...on/VisualCron5.7.2-4.exe 
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
gencap
2011-02-07T21:57:26Z
I can't connect with this test version to a 5.6.9 server either.

If I want to revert my local install (which is not a production automation machine) to 5.6.9, do I need to uninstall and re-install or can I just install 5.6.9 back on top of 5.7.2-4?

Thanks.
Support
2011-02-07T22:23:47Z
You need to uninstall first. But, can you telnet to that machine now?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
gencap
2011-02-07T22:29:15Z
No. When telnet <machinename> 16444 is not connecting, VisualCron is also not connecting. When telnet is connecting, so is VisualCron.

Ping works always, so the machine is on the network.

Support
2011-03-16T12:58:00Z
Hi again,

this time we have really tested the IPV6 connection and it works. Please test this version:

http://www.visualcron.co....aspx?g=posts&t=1692 

Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top