MT5 Tester problem - local agent closes connection

 

I have problem with testing strategies locally. For some reason local agents don't seem to respond. I get such infornmations in log:

2011.08.17 12:05:07    Core 1    disconnected
2011.08.17 12:05:07    Core 1    EURUSD: history synchronization completed [3337 Kb]
2011.08.17 12:05:07    Core 1    EURUSD: history for 2010 year synchronized
2011.08.17 12:05:07    Core 1    EURUSD: history for 2009 year synchronized
2011.08.17 12:05:06    Core 1    common synchronization completed
2011.08.17 12:05:06    Tester    EURUSD,M1 (MetaQuotes-Demo): testing of Experts\tauzentrader2010_FIN.

ex5 from 2010.01.01 00:00 to 2010.08.16 00:00 to be started
2011.08.17 12:05:06    Core 1    authorized (agent build 489)
2011.08.17 12:05:06    Core 1    connected
2011.08.17 12:05:06    Core 1    connecting to 127.0.0.1:3000

2011.08.17 12:05:05    Core 1    agent process started

After that local agent remains busy all the time although testing is finished.

I tried different versions of MT but without successs.


I use intel i7 processor and 64bit Windows 7 with 64bit Metatrader.

Did anyone have such problems also?

Metaquotes  - please help


 
ttauzo:

I have problem with testing strategies locally. For some reason local agents don't seem to respond. I get such infornmations in log:

2011.08.17 12:05:07    Core 1    disconnected
2011.08.17 12:05:07    Core 1    EURUSD: history synchronization completed [3337 Kb]
2011.08.17 12:05:07    Core 1    EURUSD: history for 2010 year synchronized
2011.08.17 12:05:07    Core 1    EURUSD: history for 2009 year synchronized
2011.08.17 12:05:06    Core 1    common synchronization completed
2011.08.17 12:05:06    Tester    EURUSD,M1 (MetaQuotes-Demo): testing of Experts\tauzentrader2010_FIN.

ex5 from 2010.01.01 00:00 to 2010.08.16 00:00 to be started
2011.08.17 12:05:06    Core 1    authorized (agent build 489)
2011.08.17 12:05:06    Core 1    connected
2011.08.17 12:05:06    Core 1    connecting to 127.0.0.1:3000

2011.08.17 12:05:05    Core 1    agent process started

After that local agent remains busy all the time although testing is finished.

I tried different versions of MT but without successs.

I use intel i7 processor and 64bit Windows 7 with 64bit Metatrader.

Did anyone have such problems also?

Metaquotes  - please help

 

Seems like your "port"  may be in use/Blocked by Windows Firewall or hardfirewall.

Start>search>type CMD

In dos prompt type Netstat /a

is this piggy opened 127.0.0.1:3000   ???? 

 

Try a different Port number and define a static Private Class Ip address. Loopback should work but you should alway use static ips for each computer.

 Your router must use a Wan to Private Ip Class as follows:

192.168.1.(computer number)-192.168.1.254

 

Your MT5 computer IP could be:

192.168.1.100 

255.255.255.0

192.168.1.1

 

dns

192.168.1.1 

 

Setting up rules to allow traffic into from a public IP WAN to a private IP LAN class takes some understanding...BUT it must be done.

For enterprise routers by default everything is locked down and its a PITA to add IPS one by one but hey thats security.....

I use my Local LANS at Work to render my codes while I'm at home using a single computer that is slow and way more expensive as electricity cost over 30cents KWH in NYC while its 1/3 cheaper at work NJ.

Thus utilizing my untapped resources at work saves me money in the long run. 

Its not metatrader as I too have win 7 64bit with no problems.

****Oh just remember from the wan side you can't use the same PORT NUMBER TWICE. thats a bug that should be removed but I understand that.

Basically, from the wan Public Ip 123.45.678:2000:2096 you can only use one port one time by default when you add ports metatrader likes to revert to default 2000 again but this is because the IP or Private IP number has changed

so in theory it is correct but on the WAN side it is not. just my input. Meta5 should allow IT guys to manually assign PORTS or at least from and to to prevent duplicates when going wan side. LAN is no problem.

 

Ok, so my guess is you are going INTERNAL LAN to LAN right? You want to talk to a computer you can reach out and touch in 20 seconds?

Solution:

Add a Private IP class (say goodbye DHCP headaches forever)

assign each local computer a specfic private IP number like 192.168.1.22 (hey Im 22 years old) then never use that again on your LAN.

Next or other computer would be 192.168.1.23(yes I wish I were 23) and so forth. Thus you have assigned a private IP.

Wow, now you can use a cache server and speed up your internet massively(don't ask)

Then  you should be able to talk to the computer because you have the same gateway in common 192.168.1.1 ? confused? just copy the above it works with 99% of plastic routers.

 

 in your network settings IP4

192.168.1.100

255.255.255

192.168.1.1

 

dns

192.168.1.1

Blank

 

happy trails you should be good to go...It easy just take your time.

Mike 

 

Reason: