Got it. Forget about UAC. And in terminal settings, in the "Server" tab, is "Use proxy server" ticked by any chance? And one more thing: have you tried unloading antivirus/firewall completely?
Karputov Vladimir: Got it. Forget about UAC. Is the "Use proxy server" option in the "Server" tab of the terminal settings ticked by any chance? And one more thing: have you tried unloading antivirus/firewall completely?
Yes, there was a tick in the terminal settings, I unchecked it.
Karputov Vladimir: Now restart the terminal and log file again in the studio please.
107:01:11.710 MQL5.community: authorization failed
107:01:12.426'7773899': connect failed [Нет связи]
007:01:27.987'7773899': login on Alpari-Demo through demo.ru.0 a
007:01:28.916'7773899': login datacenter on Alpari-Demo through demo.ru.0 a
007:01:29.146'7773899': previous successful authorization performed from78.85.179.29007:01:29.465'7773899': Signal - connecting to signal server
007:01:32.380 MQL5.community: activated for'IvanovSt', balance: 0.00007:01:33.491'7773899': auto connecting to a better access point demo.nl.3 a (ping is87.58 ms)
007:01:34.074'7773899': login on Alpari-Demo through demo.nl.3 a
007:01:34.961'7773899': login datacenter on Alpari-Demo through demo.nl.3 a
007:01:35.190'7773899': previous successful authorization performed from78.85.179.29107:01:35.690'7773899': Signal - connect to (null) through proxy failed
007:01:35.692'7773899': Signal - connecting to signal server
107:01:46.526'7773899': Signal - connect to (null) through proxy failed
007:06:05.376'7773899': Signal - connecting to signal server
107:06:16.366'7773899': Signal - connect to (null) through proxy failed
007:11:05.538'7773899': Signal - connecting to signal server
107:11:16.394'7773899': Signal - connect to (null) through proxy failed
007:16:05.898'7773899': Signal - connecting to signal server
107:16:16.546'7773899': Signal - connect to (null) through proxy failed
007:21:06.059'7773899': Signal - connecting to signal server
107:21:16.695'7773899': Signal - connect to (null) through proxy failed
007:26:06.231'7773899': Signal - connecting to signal server
107:26:16.825'7773899': Signal - connect to (null) through proxy failed
007:31:05.322'7773899': Signal - connecting to signal server
107:31:15.904'7773899': Signal - connect to (null) through proxy failed
007:36:05.492'7773899': Signal - connecting to signal server
107:36:16.492'7773899': Signal - connect to (null) through proxy failed
007:41:05.641'7773899': Signal - connecting to signal server
107:41:16.600'7773899': Signal - connect to (null) through proxy failed
007:46:05.761'7773899': Signal - connecting to signal server
107:46:16.307'7773899': Signal - connect to (null) through proxy failed
113:48:55.766'7773899': connect failed [Нет связи]
113:48:58.787 MQL5.community: authorization failed
013:49:06.439'7773899': login on Alpari-Demo through demo.nl.3 a
013:49:07.350'7773899': login datacenter on Alpari-Demo through demo.nl.3 a
013:49:07.694'7773899': previous successful authorization performed from78.85.179.29013:49:09.489'7773899': Signal - connecting to signal server
013:49:11.247 MQL5.community: activated for'IvanovSt', balance: 0.00013:49:12.322'7773899': auto connecting to a better access point demo.ru.0 a (ping is110.51 ms)
013:49:12.952'7773899': login on Alpari-Demo through demo.ru.0 a
013:49:13.927'7773899': login datacenter on Alpari-Demo through demo.ru.0 a
013:49:14.226'7773899': previous successful authorization performed from78.85.179.29113:49:14.499'7773899': Signal - connect to (null) through proxy failed
013:49:14.502'7773899': Signal - connecting to signal server
113:49:25.371'7773899': Signal - connect to (null) through proxy failed
115:40:47.716'7773899': ping failed
015:40:56.544'7773899': login on Alpari-Demo through demo.uk.6115:40:56.922'7773899': Signal - connect to (null) through proxy failed
015:40:58.342'7773899': login datacenter on Alpari-Demo through demo.uk.6015:40:58.580'7773899': previous successful authorization performed from78.85.179.29015:41:03.561'7773899': auto connecting to a better access point demo.ru.0 a (ping is108.73 ms)
015:41:04.353'7773899': login on Alpari-Demo through demo.ru.0 a
015:41:05.442'7773899': login datacenter on Alpari-Demo through demo.ru.0 a
015:41:05.683'7773899': previous successful authorization performed from78.85.179.29015:45:48.409'7773899': Signal - connecting to signal server
115:45:59.117'7773899': Signal - connect to (null) through proxy failed
015:50:47.683'7773899': Signal - connecting to signal server
115:50:58.576'7773899': Signal - connect to (null) through proxy failed
015:55:47.813'7773899': Signal - connecting to signal server
115:55:58.410'7773899': Signal - connect to (null) through proxy failed
016:00:47.995'7773899': Signal - connecting to signal server
116:00:58.744'7773899': Signal - connect to (null) through proxy failed
016:05:48.139'7773899': Signal - connecting to signal server
116:05:58.930'7773899': Signal - connect to (null) through proxy failed
016:55:38.388'7773899': Signal - connecting to signal server
116:55:43.512'7773899': ping failed
116:55:43.627'7773899': datacenter connecting failed [6]
016:55:44.206'7773899': login on Alpari-Demo through demo.nl.3016:55:44.929'7773899': login datacenter on Alpari-Demo through demo.nl.3016:55:45.130'7773899': previous successful authorization performed from78.85.179.29116:55:45.385'7773899': Signal - connect to (null) through proxy failed
016:55:45.387'7773899': Signal - connecting to signal server
016:55:50.102'7773899': auto connecting to a better access point demo.ru.0 a (ping is108.51 ms)
016:55:50.816'7773899': login on Alpari-Demo through demo.ru.0 a
016:55:51.740'7773899': login datacenter on Alpari-Demo through demo.ru.0 a
016:55:51.975'7773899': previous successful authorization performed from78.85.179.29116:55:52.197'7773899': Signal - connect to (null) through proxy failed
016:55:52.199'7773899': Signal - connecting to signal server
116:56:02.885'7773899': Signal - connect to (null) through proxy failed
117:00:38.466'7773899': Signal - connect to (null) through proxy failed
017:00:38.471'7773899': Signal - connecting to signal server
117:00:49.347'7773899': Signal - connect to (null) through proxy failed
017:05:38.582'7773899': Signal - connecting to signal server
117:05:49.448'7773899': Signal - connect to (null) through proxy failed
017:10:38.814'7773899': Signal - connecting to signal server
117:10:49.448'7773899': Signal - connect to (null) through proxy failed
017:15:39.070'7773899': Signal - connecting to signal server
117:15:49.988'7773899': Signal - connect to (null) through proxy failed
017:20:39.140'7773899': Signal - connecting to signal server
117:20:50.037'7773899': Signal - connect to (null) through proxy failed
017:25:38.681'7773899': Signal - connecting to signal server
117:25:49.613'7773899': Signal - connect to (null) through proxy failed
120:28:25.312 MQL5.community: authorization failed
020:28:29.252'7773899': login on Alpari-Demo through demo.ru.0 a
020:28:30.757'7773899': login datacenter on Alpari-Demo through demo.ru.0 a
020:28:31.037'7773899': previous successful authorization performed from78.85.179.29120:28:31.737'7773899': Signal - connect to (null) through proxy failed
020:28:31.739'7773899': Signal - connecting to signal server
020:28:32.760 MQL5.community: activated for'IvanovSt', balance: 0.00020:28:36.968'7773899': auto connecting to a better access point demo.nl.3 (ping is86.61 ms)
020:28:38.609'7773899': login on Alpari-Demo through demo.nl.3020:28:39.563'7773899': login datacenter on Alpari-Demo through demo.nl.3020:28:39.777'7773899': previous successful authorization performed from78.85.179.29120:28:40.179'7773899': Signal - connect to (null) through proxy failed
020:28:40.181'7773899': Signal - connecting to signal server
120:28:51.180'7773899': Signal - connect to (null) through proxy failed
020:33:21.958'7773899': Signal - connecting to signal server
120:33:32.570'7773899': Signal - connect to (null) through proxy failed
020:38:22.133'7773899': Signal - connecting to signal server
120:38:33.116'7773899': Signal - connect to (null) through proxy failed
020:43:21.702'7773899': Signal - connecting to signal server
120:43:32.678'7773899': Signal - connect to (null) through proxy failed
020:48:21.800'7773899': Signal - connecting to signal server
120:48:32.736'7773899': Signal - connect to (null) through proxy failed
121:09:11.873'7773899': Signal - connect to (null) through proxy failed
021:09:11.876'7773899': Signal - connecting to signal server
021:09:18.037'7773899': login on Alpari-Demo through demo.nl.3021:09:18.808'7773899': login datacenter on Alpari-Demo through demo.nl.3021:09:19.022'7773899': previous successful authorization performed from78.85.179.29
Степан Иванов: rebooting does not work, same story
I only have the latest version: for the correct work of the terminal on Windows XP must have the serispac 3 update and Internet Explorer not lower than 8,0.
Karputov Vladimir: I have only the latest version: for the correct work of the terminal on Windows XP should be the update serispac 3 and Internet Explorer not lower than 8,0.
The client terminal can work under Microsoft Windows XP (SP3)/2003/Vista/2008/7/8/8/10 operating systems. It also requires a processor with SSE2 instruction set support. Other hardware requirements depend on specific scenarios of terminal usage - load from running MQL4 programmes, number of active tools, charts, etc.
What operating system do you have? UAC must have been disabled?
windows xp, what is UAC?
Got it. Forget about UAC. Is the "Use proxy server" option in the "Server" tab of the terminal settings ticked by any chance? And one more thing: have you tried unloading antivirus/firewall completely?
Yes, there was a tick in the terminal settings, I unchecked it.
Now restart the terminal and log file again in the studio please.
rebooting does not work, same story
I have only the latest version: for the correct work of the terminal on Windows XP should be the update serispac 3 and Internet Explorer not lower than 8,0.
So it is - https://www.metatrader4.com/ru/trading-platform/help
The client terminal can work under Microsoft Windows XP (SP3)/2003/Vista/2008/7/8/8/10 operating systems. It also requires a processor with SSE2 instruction set support. Other hardware requirements depend on specific scenarios of terminal usage - load from running MQL4 programmes, number of active tools, charts, etc.