"Connecting to transport service" while trying to connect to multiplayer

[K2-smoking bum]

I've changed nothing on my end. Updated graphics drivers, signed out/in of XBL account, nothing has helped. Anyone experience this recently?

Edit: trying to see if deleting/redownloading everything helps

Edit2: redownloading everything did nothing, still same message...

[Jimmy Hunter]

Originally posted by Rejsyg:

Originally posted by emp_gregg_turkington:

Update: got a reply from support they are looking in to it. Anyone else who has this issue submit a ticket if you haven't already might help them resolve it faster.

Same reply I got: "This is a known issue and the team is working to resolve this."

So the consensus still stands that only Windows 7 users are experiencing this?

Someone else and myself reported it happening on Windows 10 laptops, as well as Windows 7.

[GabeKirk24]

Originally posted by WHITEWOLF660:

same issue and NO stick your windows 10 up your tech butt. ive read online that its 343 server side issues not the users fault in the past. i miss bungi :(

Server side for most and not others, mainly win 7 users though, it will be server side, but you can't deny what's put in front of us

[emp_gregg_turkington]

still having this problem today

[Jimmy Hunter]

Originally posted by emp_gregg_turkington:

still having this problem today

Yep, no difference today from yesterday on either Win 7 or 10.

[GabeKirk24]

Originally posted by Jimmy Hunter:

Originally posted by emp_gregg_turkington:

still having this problem today

Yep, no difference today from yesterday on either Win 7 or 10.

Serious question where are ya based in the world, because I've had no issues whatsoever, and if its server side, surely alot more would be having prominent issues

[Vyrtualis]

Originally posted by Vysebane:

Originally posted by FireHawk117:

If not try that then verify, that fails then go play something else and hope that it fixes itself

You sound like a lazy dev on an alt account. Would you mind not flailing around your fanboy ♥♥♥♥ and maybe ya know... be generally more helpful than a tantalizing prick of a human being?

Even "Try Windows 10" is an absurd comment. How about you try and give me your bank account info and your free labor to update my windows 7 to 10 and saving my TBs of data along with it.

These asinine comments made by asinine people make me sick. When people need help and the solution is either to defend the game/studio or forcing people to play on a different platform or OS that they may not prefer (which is a committed change to make), then it's really ♥♥♥♥♥♥ up of you. And I take it further when a game studio doesn't let me play off my external hard drive over my internal one. (Uplay and Assassin's Creed come to mind). So I find this solution of yours to just sit around and let it fix itself the most BS position for you to be in.

I hope you toss your computer out a 3-story window, have it break, and have someone tell you the solution to your problem to be "just do something else and hope that it fixes itself".

A Win10 Pro OEM key is 10-15 dollars, and you can update without losing any data.

Don't take your anger out on us because you choose to continue to use an End of Life OS. You get to accept the risks and problems that are inherent therein.

[Pyrocitor]

Originally posted by Jimmy Hunter:

Originally posted by emp_gregg_turkington:

still having this problem today

Yep, no difference today from yesterday on either Win 7 or 10.

From what I can tell, there's an issue generally affecting windows 7 users in large numbers - otherwise there are other reasons for getting stuck at "contacting server" that have existed for a while that can affect anyone, including windows 10 - but these older reasons are usually fixed by the sign-out-sign-in.

The part where a large number of people are stuck, in the past 24 hours or so that can't just sign back in seems to be tied to windows 7, however.

I'm not sure if they're connected to the same cause.

People here have submitted tickets, and it's been mentioned on waypoint and the halo discord, and I'm looking/asking around again if there's any notice about a service issue i can bring back for you lot here.

[Jimmy Hunter]

Originally posted by Pyrocitor:

Originally posted by Jimmy Hunter:

Yep, no difference today from yesterday on either Win 7 or 10.

From what I can tell, there's an issue generally affecting windows 7 users in large numbers - otherwise there are other reasons for getting stuck at "contacting server" that have existed for a while that can affect anyone, including windows 10 - but these older reasons are usually fixed by the sign-out-sign-in.

That's why I went and tested it on my laptop to see if it was my end. Even the normal troubleshooting stuff didn't fix the connection on Win 10, so I can only chalk it up to something odd on their end.

People here have submitted tickets, and it's been mentioned on waypoint and the halo discord, and I'm looking/asking around again if there's some statement about a known issue I can bring back to here.

I figured it wouldn't take long to spread around about the issue. But thanks for keeping an eye out for us effected by this. Hopefully this problem gets fixed sooner than later and doesn't end up getting pushed out until next week.

[::(R)aptor007::]

Hopefully they're working on this. After the crap MS tried to pull with Halo 2 PC requiring Vista, I made sure Windows 7 was listed in the requirements for MCC before I purchased it.

[Pyrocitor]

I do also want to nip that here: while staying on Windows 7 is probably bound to come with some issues in general after being EOL'd, Halo: The Master Chief Collection is officially supported on Windows 7 - they aren't just randomly cutting it off.

So arguing that others have to upgrade to 10 just for this issue is off the mark.

[TheShadows793]

Originally posted by Relentless_Games:

Y'all lucky it even worked before, ever since I bought this I've never been able to play MP. It's always been stuck when I get to match making with the message "contacting server to get matchmaking data" and now its stuck on "connecting transport server"

I had your first issue for Firefight and MP "Contacting server to get matchmaking data" and never connecting, not when it came out but right after they added Halo 3, thought it was a bug due to the new game since it had been working fine for MONTHS, waited for about a week until I had time to mess around with my comp.

Finally, after a few hours of surfing forums, someone put out the exact update needed that was somehow missing from my windows 7 system (KB3020369). Took a bit of finagling, and a lot of patience, (Specially cuz I was stressed that I wouldn't be able to play with my siblings on our online gamenight anymore. Since none of the other fixes had worked for me, "Sign in and out of Xbox Live, uninstall reinstall the entire thing, run as admin, make sure compatibility mode is on, etc. Like I said this was hours later and many restarts..) but the update solved the problem for me.

Hope this might help someone else too =)

[El-Neko]

Well its working now since I was able to play on matchmaking again on normal MCC and the Flight.

[emp_gregg_turkington]

I just updated to win 10 and it works. free update just google it if you want to try it and other solutions haven't worked for you.

[GabeKirk24]

Originally posted by emp_gregg_turkington:

I just updated to win 10 and it works. free update just google it if you want to try it and other solutions haven't worked for you.

there you go

[Trueblade]

Originally posted by Pyrocitor:

I do also want to nip that here: while staying on Windows 7 is probably bound to come with some issues in general after being EOL'd, Halo: The Master Chief Collection is officially supported on Windows 7 - they aren't just randomly cutting it off.

So arguing that others have to upgrade to 10 just for this issue is off the mark.

Just wanna bring a bit of extra attention to this. While there's been one instance of an upgrade working in this thread, it is by no means the absolute solution here. Switching OS to fix a sudden connection issue with one game that supports your OS is definitely the nuclear option.

Pretty frustrating to see little from 343 on this matter, doubly so given the ODST flight is currently running.