Launcher freezing at 'authenticating'

TSRCoryS

So, no one has called them to verify all the ports are opened and that they don't have any settings, either on their end or within their software, that could cause the problem?

Battleboomer

i will ask them tomorrow SMILEY

Demonicon

Sorry, didn´t have time. Today is my birthday and I had to drink very much and stuff like that SMILEY

Demonicon

Okay, I just phoned the T-Online support personell. They clearly said, that they are not blocking any ports or address ranges, also not the ones from matrix. The administrator ask me for a specific address so that he could check whether he can access the patch server from his side. Unfortunately, as you have this virtual server thing, I couldn´t come up with anything specific. Can you give me a real address from any of your patch servers?

Oh, the above statement was verified to be true for both the software and the ISP´ side.

I am not sure, and I asked him about peering issues, but again we had no address to check for that- although we verified that I could reach at least the game servers. Seems we are stuck again and I hope that my german friend may come up with a solution SMILEY

As a sidenote: I played and patched Starwarsgalaxies, Planetside, World of Warcraft, Anarchy Online and many more with this ISP and the exact same software- I really don´t think it´s something on my end. At least you seem to have a very unique configuration on your side.

Is there a way to download the patch manually? As I seem to be able to connect to the game servers okay...

Demonicon

Oh and btw, I have been in the matrix beta, too and the game worked with the exact same configuration I have now.

**phi** · 01/17/2006 14:09:14

Despite what is listed a bazillion times on these forums, the ports you need are not complete.

You need ports:

10000 to 11000 (TCP & UDP, inbound & outbound)

7030 (TCP outbound)

9700 (UDP outbound)

5190 (TCP inbound & outbound) - Not needed anymore, this is the AOL port.

also check that you have local admin rights on your machine (I don't think that's the problem)

It is possible that T-Online are blocking the outbound UDP requests to 9700 or tcp 7030 (crazy Germans) SMILEY

These 2 ports are required for the auth and patch servers. The launcher will not work propely without them.

As for the "can't run multiple instances" error, if it happens again just open the task manager (ctrl-alt-del then chose task manager) and manually kill the matrix.exe task.

I am behind a WatchGuard Firebox and I had to explicitly allow those outbound connections. It took a lot of "change config, watch blocked packet log, repeat" to get it right.

It's not usually a problem as most firewalls allow anything outbound. But some along with some service providers don't so that you can't spread an infection as easily, should you get one.

Message Edited by phi on 01-18-200608:09 AM

TSRCoryS

I am surprised to see the port 7030 in there-- that is within the port range that the Launchpad (used for all of our other games) uses to connect to the login server. however, we were never made aware that the Launcher for MxO had been updated with this. We believed a DNS redirect was taking place (which would explain UNEXPECTED_AUTH_MESSAGE errors if the Launcher was receiving data from our servers, but had not yet been updated with the new launcher code to support it). I will be getting in touch with someone on the MxO team about this when I have a chance to clarify exactly what is ocurring.

Battleboomer · 01/19/2006 09:16:00

Hi ,
i got the same answer as Demonicon "T-online is not blocking any ports or address ranges"!
I have given the ports free, deactivedet the firewall and have admin rights, installt the Matrix launcher .

Nothing has changed SMILEY

same problems as befor.

(Launcher Version: v7.5415 / Client version: vunknown)

Nachricht bearbeitet von Battleboomer am 01-19-200606:06 PM

Nachricht bearbeitet von Battleboomer am 01-19-200606:15 PM

TSRCoryS

I will be contacting the 2 of you for some advanced connectivity troubleshooting via PM after my shift today.

TSRCoryS

As an update, I wanted to let you know that I did get your network troubleshooting e-mails. There is a curiosity that both of your trace results share across all of your traces:

4 --- 100/ 100 =100% 100/ 100 =100% 62.156.138.214

0/ 100 = 0% |

5 --- 100/ 100 =100% 100/ 100 =100% tbr2-p013802.n54ny.ip.att.net [12.122.12.53]

0/ 100 = 0% |

6 --- 100/ 100 =100% 100/ 100 =100% tbr2-cl15.wswdc.ip.att.net [12.122.10.54]

0/ 100 = 0% |

7 --- 100/ 100 =100% 100/ 100 =100% tbr1-cl27.wswdc.ip.att.net [12.122.9.149]

0/ 100 = 0% |

8 --- 100/ 100 =100% 100/ 100 =100% tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]

0/ 100 = 0% |

9 --- 100/ 100 =100% 100/ 100 =100% tbr2-cl6.dlstx.ip.att.net [12.122.10.90]

0/ 100 = 0% |

10 --- 100/ 100 =100% 100/ 100 =100% gbr2-p20.phmaz.ip.att.net [12.122.10.82]

0/ 100 = 0% |

11 --- 100/ 100 =100% 100/ 100 =100% 12.122.10.193

0/ 100 = 0% |

12 --- 100/ 100 =100% 100/ 100 =100% gbr1-p40.sd2ca.ip.att.net [12.122.2.6]

0/ 100 = 0% |

13 --- 100/ 100 =100% 100/ 100 =100% gar1-p360.sd2ca.ip.att.net [12.123.145.21]

0/ 100 = 0% |

14 --- 100/ 100 =100% 100/ 100 =100% mdf1-gsr12-2-pos-7-0.san2.attens.net [12.122.255.206]

0/ 100 = 0% |

5 --- 100/ 100 =100% 100/ 100 =100% tbr2-p012202.n54ny.ip.att.net [12.123.1.126]

0/ 100 = 0% |

6 --- 100/ 100 =100% 100/ 100 =100% tbr2-cl15.wswdc.ip.att.net [12.122.10.54]

0/ 100 = 0% |

7 --- 100/ 100 =100% 100/ 100 =100% tbr1-cl27.wswdc.ip.att.net [12.122.9.149]

0/ 100 = 0% |

8 --- 100/ 100 =100% 100/ 100 =100% tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]

0/ 100 = 0% |

9 --- 100/ 100 =100% 100/ 100 =100% tbr2-cl6.dlstx.ip.att.net [12.122.10.90]

0/ 100 = 0% |

10 --- 100/ 100 =100% 100/ 100 =100% gbr2-p20.phmaz.ip.att.net [12.122.10.82]

0/ 100 = 0% |

11 --- 100/ 100 =100% 100/ 100 =100% 12.122.10.193

0/ 100 = 0% |

12 --- 100/ 100 =100% 100/ 100 =100% gbr1-p10.sd2ca.ip.att.net [12.122.3.10]

0/ 100 = 0% |

13 --- 100/ 100 =100% 100/ 100 =100% gar1-p360.sd2ca.ip.att.net [12.123.145.21]

0/ 100 = 0% |

14 --- 100/ 100 =100% 100/ 100 =100% mdf1-gsr12-2-pos-7-0.san2.attens.net [12.122.255.206]

This is exactly the same for the both of you. This indicates a problem with the ISP's Tier 2 provider and their connection to AT&T's backbone. It also brings to mind a possible satellite conenction over the pond, instead of the fiber cables run on the ocean floor. If either of you could conenct to another ISP (at a friends house with a different high-speed provider (who can connect to MxO ideally)) would really help narrow this down. If eiither of you could try it, and let me know, I'd appreciate it.

I am also trying some reverse-traces to the two of you, as well as other addresses owned by T-Online, and I'll be comparing the traces for similar problems. Expect an e-mail from me end-of-shift tomorrow.

Battleboomer

still waiting for your e-mail SMILEY

TSRCoryS

Sent. Check your e-mail guys, and let me know your results please.

Realvibos

Hello,

Did you find a solution yet?

I have exactly the same problem here with the launcher freezing at authenticating and so on.

So if you know how to fix it,please let me know SMILEY

Thx alot

Volker

lynxilein

hi all,

I've the same problem since a few days. But I played mxo a week before without problems. And I changed nothing! Now the launcher hangs at Authenticating. Running no firewall, no virus-scanner and no relevant ports are blocked by my isp. Perhaps I could help to solve the problem in testing for the teech-support? Feel free to email me.

greets
Flo