troubles for connection
Moderator: French Moderator
Re: troubles for connection
If you don't have those lines in your hosts file, it's good.
Did you search for "maniaplanet" in all files under Windows folder?
Which anti virus, firewall or other security programs are you using?
Because it is probably there... the block...
Did you search for "maniaplanet" in all files under Windows folder?
Which anti virus, firewall or other security programs are you using?
Because it is probably there... the block...
Re: troubles for connection
I have reinstall maniaplanet (after properly delete all files) , for more safety i hv reinstalled it in c (before it was in another partition) , nothing change.
i have check antivir , firewall & nothing block maniaplanet.
in folder i got a file UGCErrorsLog.txt saying :
<manialink> file://Media\Manialinks\station.xml?size=3: File 'Manialinks\station.xml' not found.
here my first log file after reinstall , i saw some "fail" but i don't know what to do
http://sd-4.archive-host.com/membres/up ... -17-02.txt
i have check antivir , firewall & nothing block maniaplanet.
in folder i got a file UGCErrorsLog.txt saying :
<manialink> file://Media\Manialinks\station.xml?size=3: File 'Manialinks\station.xml' not found.
here my first log file after reinstall , i saw some "fail" but i don't know what to do
http://sd-4.archive-host.com/membres/up ... -17-02.txt
Re: troubles for connection
A different partition is not a "safety" issue, I have installed everything on e.g. D: (not only game files, also personal data for ManiaPlanet) and it's working absolutely fine.
You still have the issue that your internet is not working properly for ManiaPlanet, I can see this from the log, by comparing to one recent on my machine:
What makes me also wonder, is that your ManiaPlanet is connecting to
where I have
And at the following line, I don't have the port :0 at the end.
On the other hand, your stations were updated, so some connection is possible.
Also the updater checked file consistency.
I presume another application is blocking important ports ManiaPlanet normally uses, especially for the menus, which are fetched using http requests.
Which applications are running in Autosart, which applications are visible in the task bar / tray symbols?
Please close everything!!!
Ideally have a naked Windows!
Did you copy your existing Profile.Gbx file, or did you connect to ManiaPlanet server "Using an existing account" after the reinstallation?
If you have time, later we could do a TeamViewer session together.
You still have the issue that your internet is not working properly for ManiaPlanet, I can see this from the log, by comparing to one recent on my machine:
Code: Select all
Assert Failed in source\Net_Win32.cpp Line 451
=> 'InternetSetOptionA(m_Wininet.hInternetSession, 77, &Enable, sizeof(Enable))' failed.
Code: Select all
[MasterServer] => [9 304] Request sent : GetConnectionAndGameParams (init.maniaplanet.com:80)
Code: Select all
[MasterServer] => [10 538] Request sent : GetConnectionAndGameParams (mp02.maniaplanet.com:80)
Code: Select all
[Net] ForceServerAddress : 0.0.0.0:0
Also the updater checked file consistency.
I presume another application is blocking important ports ManiaPlanet normally uses, especially for the menus, which are fetched using http requests.
Which applications are running in Autosart, which applications are visible in the task bar / tray symbols?
Please close everything!!!
Ideally have a naked Windows!
Did you copy your existing Profile.Gbx file, or did you connect to ManiaPlanet server "Using an existing account" after the reinstallation?
If you have time, later we could do a TeamViewer session together.
Re: troubles for connection
i made the update while i was on the debug version , & i had deleted profile.gbx too so i have click on "using existing account" .
In taskbar i have avira, sounds gestionnary & screen gestionnary .
In autostart i got adobearm , e_sfd (drivers printer ), catalyst control center, avira , realteck control panel, nwizz(nvidia), dumprep 0-k (windows memory dump processus) & net session akamai ( a prgm for adobe apparently).
I will try with the 2 last off.
I play sometimes at WarThunder , is it possible that this game (maybe using same ports) made a bug in my mania ?
In taskbar i have avira, sounds gestionnary & screen gestionnary .
In autostart i got adobearm , e_sfd (drivers printer ), catalyst control center, avira , realteck control panel, nwizz(nvidia), dumprep 0-k (windows memory dump processus) & net session akamai ( a prgm for adobe apparently).
I will try with the 2 last off.
I play sometimes at WarThunder , is it possible that this game (maybe using same ports) made a bug in my mania ?
Re: troubles for connection
If any application is using the same ports, after closing it, you will have to wait some time (typically 2 minutes, standard TCP/IP timeout) before you can use ManiaPlanet. Otherwise those ports will be blocked at the first start.
But since you probably also tried to launch ManiaPlanet somewhen, it is less likely.
However you can open a commandline window,
and use the following command to see a list of currently open and used ports:
ManiaPlanet typically uses the ports 80 (http) and 443 (https), 2350 and 3450 (P2P services), and 5000 (only for dedicated server). If you have configured different ports or port ranges for ManiaPlanet, then you have to check for those as well.
And if you open the command line with administrator rights, you can even see which application is blocking which port:
The result is the following, I have removed all other stuff:
But since you probably also tried to launch ManiaPlanet somewhen, it is less likely.
However you can open a commandline window,
and use the following command to see a list of currently open and used ports:
Code: Select all
netstat -na
And if you open the command line with administrator rights, you can even see which application is blocking which port:
Code: Select all
netstat -nab
Code: Select all
Active Connections
Proto Local Address Remote Address Status
TCP 0.0.0.0:2350 0.0.0.0:0 LISTENING
[ManiaPlanet.exe]
TCP 0.0.0.0:3450 0.0.0.0:0 LISTENING
[ManiaPlanet.exe]
TCP 192.168.0.196:49203 173.194.44.66:80 WAITING
TCP 192.168.0.196:49209 91.121.43.95:80 CONNECTED
[ManiaPlanet.exe]
TCP 192.168.0.196:49212 178.33.248.27:80 CONNECTED
[ManiaPlanet.exe]
TCP 192.168.0.196:49214 178.33.43.29:80 WAITING_CLOSE
[ManiaPlanet.exe]
TCP 192.168.0.196:49215 87.98.132.169:5222 CONNECTED
[ManiaPlanet.exe]
TCP 192.168.0.196:49216 178.33.43.29:80 CONNECTED
[ManiaPlanet.exe]
TCP 192.168.0.196:49217 91.121.43.95:80 CONNECTED
[ManiaPlanet.exe]
TCP 192.168.0.196:49224 62.149.140.106:80 CONNECTED
[ManiaPlanet.exe]
TCP 192.168.0.196:49225 87.98.247.24:80 WAITING_CLOSE
[ManiaPlanet.exe]
TCP 192.168.0.196:49226 178.33.43.29:443 WAITING_CLOSE
[ManiaPlanet.exe]
TCP 192.168.0.196:49227 91.121.184.149:80 WAITING_CLOSE
[ManiaPlanet.exe]
TCP 192.168.0.196:49229 85.214.99.117:80 CONNECTED
[ManiaPlanet.exe]
TCP 192.168.0.196:49231 178.33.43.29:443 WAITING_CLOSE
[ManiaPlanet.exe]
TCP 192.168.0.196:49232 178.33.43.29:80 CONNECTED
[ManiaPlanet.exe]
TCP 192.168.0.196:49233 178.33.43.29:80 CONNECTED
[ManiaPlanet.exe]
TCP 192.168.0.196:49234 178.33.43.29:80 CONNECTED
[ManiaPlanet.exe]
TCP 192.168.0.196:49235 178.33.43.29:80 CONNECTED
[ManiaPlanet.exe]
TCP 192.168.0.196:49236 178.33.43.29:80 CONNECTED
[ManiaPlanet.exe]
TCP 192.168.0.196:49237 178.33.43.29:80 CONNECTED
[ManiaPlanet.exe]
TCP 192.168.0.196:49238 173.194.44.73:80 CONNECTED
[ManiaPlanet.exe]
UDP 0.0.0.0:2350 *:*
[ManiaPlanet.exe]
UDP 0.0.0.0:59620 *:*
[ManiaPlanet.exe]
Re: troubles for connection
i tried with all autostart prgm disabled but nothing change.
When i do the cmd netstat -nab , the window just stay 10 sec & i can't read all ...
My java don't want to update too , i saw that today , i think my windows is bugged somehow & i should reinstall it (or repare if i find a cd of it).
Thx for your help marc , very efficient & reactiv help , i give you 5 stars on 5 for your support.
When i do the cmd netstat -nab , the window just stay 10 sec & i can't read all ...
My java don't want to update too , i saw that today , i think my windows is bugged somehow & i should reinstall it (or repare if i find a cd of it).
Thx for your help marc , very efficient & reactiv help , i give you 5 stars on 5 for your support.
Re: troubles for connection
thanks
for the netstat cmd, you should open a cmd console as administrator, and execute it there.
If you simply use the execute bar in Windows, netstat -nab won't execute, because of missing priviledges.

for the netstat cmd, you should open a cmd console as administrator, and execute it there.
If you simply use the execute bar in Windows, netstat -nab won't execute, because of missing priviledges.
Re: troubles for connection
here are the results , it seems my ports for mania are closed & many bugs on all try
maybe should i hv done that with the game open .
C:\WINDOWS\system32>netstat -na
Connexions actives
Proto Adresse locale Adresse distante Etat
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:843 0.0.0.0:0 LISTENING
TCP 0.0.0.0:44080 0.0.0.0:0 LISTENING
TCP 0.0.0.0:44081 0.0.0.0:0 LISTENING
TCP 0.0.0.0:48113 0.0.0.0:0 LISTENING
TCP 0.0.0.0:48114 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1088 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1113 127.0.0.1:1114 ESTABLISHED
TCP 127.0.0.1:1114 127.0.0.1:1113 ESTABLISHED
TCP 127.0.0.1:9000 0.0.0.0:0 LISTENING
TCP 127.0.0.1:9000 127.0.0.1:2298 TIME_WAIT
TCP 127.0.0.1:9040 0.0.0.0:0 LISTENING
TCP 192.168.1.10:139 0.0.0.0:0 LISTENING
TCP 192.168.1.10:2291 216.58.210.163:80 TIME_WAIT
TCP 192.168.1.10:9000 0.0.0.0:0 LISTENING
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:4500 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1030 *:*
UDP 127.0.0.1:1900 *:*
UDP 192.168.1.10:123 *:*
UDP 192.168.1.10:137 *:*
UDP 192.168.1.10:138 *:*
UDP 192.168.1.10:1030 *:*
UDP 192.168.1.10:1900 *:*
C:\WINDOWS\system32>netstat -nab
Connexions actives
Proto Adresse locale Adresse distante Etat
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
Impossible d'obtenir les informations de propriétaire.
TCP 192.168.1.10:139 0.0.0.0:0 LISTENING 4
Impossible d'obtenir les informations de propriétaire.
TCP 127.0.0.1:1113 127.0.0.1:1114 ESTABLISHED 2252
Impossible d'obtenir les informations de propriétaire.
TCP 127.0.0.1:1114 127.0.0.1:1113 ESTABLISHED 2252
Impossible d'obtenir les informations de propriétaire.
TCP 127.0.0.1:9000 127.0.0.1:2299 TIME_WAIT 0
UDP 0.0.0.0:445 *:* 4
Impossible d'obtenir les informations de propriétaire.
UDP 0.0.0.0:4500 *:* 1304
Impossible d'obtenir les informations de propriétaire.
UDP 0.0.0.0:500 *:* 1304
Impossible d'obtenir les informations de propriétaire.
UDP 127.0.0.1:123 *:* 1772
Impossible d'obtenir les informations de propriétaire.
UDP 127.0.0.1:1030 *:* 2368
Impossible d'obtenir les informations de propriétaire.
UDP 127.0.0.1:1900 *:* 3804
Impossible d'obtenir les informations de propriétaire.
UDP 127.0.0.1:1900 *:* 2368
Impossible d'obtenir les informations de propriétaire.
UDP 127.0.0.1:1900 *:* 2368
Impossible d'obtenir les informations de propriétaire.
UDP 192.168.1.10:1030 *:* 2368
Impossible d'obtenir les informations de propriétaire.
UDP 192.168.1.10:138 *:* 4
Impossible d'obtenir les informations de propriétaire.
UDP 192.168.1.10:137 *:* 4
Impossible d'obtenir les informations de propriétaire.
UDP 192.168.1.10:1900 *:* 2368
Impossible d'obtenir les informations de propriétaire.
UDP 192.168.1.10:1900 *:* 2368
Impossible d'obtenir les informations de propriétaire.
UDP 192.168.1.10:1900 *:* 3804
Impossible d'obtenir les informations de propriétaire.
UDP 192.168.1.10:123 *:* 1772
Impossible d'obtenir les informations de propriétaire.
...........
avec le jeu lancé y'a ça en plus
avec -na
TCP 0.0.0.0:2350 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3450 0.0.0.0:0 LISTENING
UDP 0.0.0.0:2312 *:*
UDP 0.0.0.0:2350 *:*
avec -nab
UDP 0.0.0.0:2350 *:* 504
Impossible d'obtenir les informations de propriétaire.
UDP 127.0.0.1:2314 *:* 504
Impossible d'obtenir les informations de propriétaire.
maybe should i hv done that with the game open .
C:\WINDOWS\system32>netstat -na
Connexions actives
Proto Adresse locale Adresse distante Etat
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:843 0.0.0.0:0 LISTENING
TCP 0.0.0.0:44080 0.0.0.0:0 LISTENING
TCP 0.0.0.0:44081 0.0.0.0:0 LISTENING
TCP 0.0.0.0:48113 0.0.0.0:0 LISTENING
TCP 0.0.0.0:48114 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1088 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1113 127.0.0.1:1114 ESTABLISHED
TCP 127.0.0.1:1114 127.0.0.1:1113 ESTABLISHED
TCP 127.0.0.1:9000 0.0.0.0:0 LISTENING
TCP 127.0.0.1:9000 127.0.0.1:2298 TIME_WAIT
TCP 127.0.0.1:9040 0.0.0.0:0 LISTENING
TCP 192.168.1.10:139 0.0.0.0:0 LISTENING
TCP 192.168.1.10:2291 216.58.210.163:80 TIME_WAIT
TCP 192.168.1.10:9000 0.0.0.0:0 LISTENING
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:4500 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1030 *:*
UDP 127.0.0.1:1900 *:*
UDP 192.168.1.10:123 *:*
UDP 192.168.1.10:137 *:*
UDP 192.168.1.10:138 *:*
UDP 192.168.1.10:1030 *:*
UDP 192.168.1.10:1900 *:*
C:\WINDOWS\system32>netstat -nab
Connexions actives
Proto Adresse locale Adresse distante Etat
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
Impossible d'obtenir les informations de propriétaire.
TCP 192.168.1.10:139 0.0.0.0:0 LISTENING 4
Impossible d'obtenir les informations de propriétaire.
TCP 127.0.0.1:1113 127.0.0.1:1114 ESTABLISHED 2252
Impossible d'obtenir les informations de propriétaire.
TCP 127.0.0.1:1114 127.0.0.1:1113 ESTABLISHED 2252
Impossible d'obtenir les informations de propriétaire.
TCP 127.0.0.1:9000 127.0.0.1:2299 TIME_WAIT 0
UDP 0.0.0.0:445 *:* 4
Impossible d'obtenir les informations de propriétaire.
UDP 0.0.0.0:4500 *:* 1304
Impossible d'obtenir les informations de propriétaire.
UDP 0.0.0.0:500 *:* 1304
Impossible d'obtenir les informations de propriétaire.
UDP 127.0.0.1:123 *:* 1772
Impossible d'obtenir les informations de propriétaire.
UDP 127.0.0.1:1030 *:* 2368
Impossible d'obtenir les informations de propriétaire.
UDP 127.0.0.1:1900 *:* 3804
Impossible d'obtenir les informations de propriétaire.
UDP 127.0.0.1:1900 *:* 2368
Impossible d'obtenir les informations de propriétaire.
UDP 127.0.0.1:1900 *:* 2368
Impossible d'obtenir les informations de propriétaire.
UDP 192.168.1.10:1030 *:* 2368
Impossible d'obtenir les informations de propriétaire.
UDP 192.168.1.10:138 *:* 4
Impossible d'obtenir les informations de propriétaire.
UDP 192.168.1.10:137 *:* 4
Impossible d'obtenir les informations de propriétaire.
UDP 192.168.1.10:1900 *:* 2368
Impossible d'obtenir les informations de propriétaire.
UDP 192.168.1.10:1900 *:* 2368
Impossible d'obtenir les informations de propriétaire.
UDP 192.168.1.10:1900 *:* 3804
Impossible d'obtenir les informations de propriétaire.
UDP 192.168.1.10:123 *:* 1772
Impossible d'obtenir les informations de propriétaire.
...........

avec le jeu lancé y'a ça en plus
avec -na
TCP 0.0.0.0:2350 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3450 0.0.0.0:0 LISTENING
UDP 0.0.0.0:2312 *:*
UDP 0.0.0.0:2350 *:*
avec -nab
UDP 0.0.0.0:2350 *:* 504
Impossible d'obtenir les informations de propriétaire.
UDP 127.0.0.1:2314 *:* 504
Impossible d'obtenir les informations de propriétaire.
Re: troubles for connection
tu avais lancé la cmd en tant qu'administrateur?
alors "Impossible d'obtenir les informations de propriétaire." pourrait bel et bien un signe que c'est bloqué par antivirus, pare-feu, defender, ou autres...
alors "Impossible d'obtenir les informations de propriétaire." pourrait bel et bien un signe que c'est bloqué par antivirus, pare-feu, defender, ou autres...
Re: troubles for connection
tellement vieux pc que j'ai sais plus trop tout ce qu'il y a dessus .....
merci pour ton aide , j'vais faire appel a un ami pour upgrader mon pc ^^
merci pour ton aide , j'vais faire appel a un ami pour upgrader mon pc ^^
Who is online
Users browsing this forum: No registered users and 1 guest