Technical support and scripting issues
Moderators: JRL, Dorian (MJT support)
-
gknopf
- Newbie
- Posts: 12
- Joined: Thu Feb 10, 2011 11:11 pm
- Location: Germany
Post
by gknopf » Mon Nov 05, 2012 9:11 pm
I have a script that uses FTP commands. Running it on an XP environment it quits with the error message
"Socket error # 10054 Connection reset by peer"
after a while

. The compiled script and MSCHED.EXE are whitelisted in the firewall settings. So this should actually not happen.
What surprises me is that when I turn off the XP firewall the script will run without any problem. Same for the compiled script. Thus, it should be a standard XP firewall issue.
Has anyone encountered this issue and found a solution to it?
Thanks a lot!
-
olllllliii
- Pro Scripter
- Posts: 60
- Joined: Tue Dec 22, 2009 9:51 am
- Location: Mannheim ( Germany )
-
Contact:
Post
by olllllliii » Fri Nov 09, 2012 3:17 pm
Which kind of firewall do u use...??
Which ports are opend ?
Do u use a VPN ?
-------------- most time it is following ---------------------
This error indicates that an existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, ( not in your case ..i know ) the host is rebooted or the remote network was somehow disabled. (i know without the firewall its working )
A socket error 10054 can also be caused by any of the following reasons:
** Attempt configuring your FTP connection by enabling or disabling passive transfer (select or clear Passive file transfer ). (A,I)
** Try adding the Macro Scheduler to the list of trusted applications of your firewall.
Oliver Hilger Mannheim
alias Olllllliii
-
gknopf
- Newbie
- Posts: 12
- Joined: Thu Feb 10, 2011 11:11 pm
- Location: Germany
Post
by gknopf » Sat Nov 10, 2012 11:06 am
Hi olllllliii,
Which kind of firewall do u use...??
Which ports are opend ?
Do u use a VPN ?
I use a Fritz!box router with standard setup (no port changes) and a XP computer with the Windows standard firewall. VPN is not in use and the compiled script is on the whitelist of the firewall. With Win7 this problem does not occur.
Changing active / passive did not produce a different result.