Playing on the same network problems | Forums

[FireFrost]

Me and my friend are playing on the same network and the game won't let us play together. When one connects it seems to boot the other and now my friend cannot even log in anymore it says connection failure. We haven't tried rebooting but I expect that it would at least fix that part until we try again.
There is a number for the error I will provide it next time I can see it.
Also his windows firewall is currently disabled.

So does anyone know if we need port forwarding or something like that, maybe the anti-cheat is giving us some problem. (Well I think there is one) I have some other friends playing on the same network at their place and they have no problem.

thanks

Edit:
The error code is 81F60008.
thanks again

[FireFrost]

Sorry this post should be on Technical issue & Feedback, if anyone can move it.

[UbiDarla]

Hey there. It looks like this was posted when we were having some server issues. Can you update and let me know if you and your friend still can't play together?

[kyle904]

Me and my brother seem to be having the same issues.

[kyle904]

Now it seems like whoever is on the server first, the second person has issues connecting to the lobby.

[Madangry]

Do you have static IP addresses set?

[kirzan]

Hey guys this is the other dude trying to connect with FireFrost. It seems it still isn't working today.

Here's more info that could help pinpoint the issue:

- We are on a DHCP, dynamic addresses. I think this is enforced by our ISP though I could be very wrong.
- The error code that I got today was: 81F60007. The error occurs after matchmaking, when a server was found, while in a fireteam. We can both connect at the same time and play on separate servers.
- It probably isn't it, but on Steam games and more specifically Call of Duty, PunkBuster was thinking we were punks. It was part of the issue.
- To resolve the issue on Steam (because we had to do it a lot) we had to input the Launch Option "-clientport" followed by a port in the game's port range (a different specific port on each machine). We could set a launch option for GRO (using a shortcut's target line) but with the launcher being what needs to be run, I'm afraid the game EXE wouldn't have the launch option. Anyway, the game seems to use set ports and not a range per se, so I don't know.

As you can see, we are by no means professionals at this and anything I say here could be completely unrelated. That being said, I hope the information is helpful.

Cheers,
Kirzan.

[RealHempman]

Have you tried shutting down Launcher and .NET? I've personally found that 99% of the problems I had were directly related to leaving those running. Cured most of the lag, stopped disconnects and error such as you are having.

I noted two things with this last update. There was over 7 gigs of trash left behind in the install directory as well as C:\Documents and Settings\<account name>\Local Settings\Apps\2.0 - I uninstalled the update, deleted all the old trash, and reinstalled the update.

The other thing I noticed (might not help you) is that the game defaults to running at a low priority. I kicked the program up to run at above normal priority and the rest of the lag and errors are pretty much gone.

[FireFrost]

We will check it out but Im pretty sure its that punkbuster problem again.

[kyle904]

Do you have static IP addresses set?

Why would static IP Addresses be the issue if we had not have these problems prior to 5/9 and continuing today.