Network play only limited to 2 Players?

[Snacko]

Bug description:

I recently installed Win7 64 from scratch and reinstalled Lockon FC 1.12a. I used to be able to host with no problems, but today I tried to host the same old missions (I tried 3 different missions) and only one person could connect. Myself and the one other player could play just fine! But nobody else could join. When one person would leave, then the other player could join. And when they left a third could join. But only myself and one player at a time could join my server.

 

The Server was set to 32 max players and each mission had at least 6 Client aircraft. I restarted the game several times, and even rebooted. So, I emailed the same missions to a friend who I was trying to fly with, and he also was running Windows 7 64bit and he was able to get all 4 of us to join the game with no problems. But I cannot.

 

Is there some Log file I can look at?

 

Please Help!?

 

Steps to reproduce / Conditions of occurence

Host a multiplayer mission.

 

PC Configuration

Win7 64bit

i7 965 Extreme

Asus Rampage II Extreme MB

6gig Corsair memory

 

Note: I have installed the game in this folder:

C:\My Programs\Eagle Dynamics\Lock On

Edited January 9, 2010 by Snacko

[EtherealN]

Personally I would look at your network routines, firewalls and/or router settings. My suspicion is that something is preventing LO from handling several connections at the same time. I assume that you have tried running as administrator?

[TheMoose]

I would start with verifying you Local Area connection properties.

Sometimes, a software base firewall/antivirus might want to try and bind itself with your adapter. It might cause some conflicts. If any is showing in your LAN properties, first disable your internet security software. Recheck the LAN properties, if still present the just uncheck the boxes besides them.

If you have a router, then trying isolating the network itself by bypassing the router, just connect directly to the modem. (You can use the windows firewall if you bypass the router for protection)

Ensure you have the latest NIC drivers installed.

If you can host without any problems without the router, then you have made the process of elimination. Re install your router, check for router firmware upgrades if available. Try port forwarding the 10308 UDP/TCP to the host machine.

 

http://www.portforward.com/english/applications/port_forwarding/Lock_On/Lock_Onindex.htm

Select your router type and follow the instruction.

 

Hope this helps.

Cheers

[Snacko]

Thanks for the replies.

 

I am able to host in other games... I had about 15 users on my pc flying IL2 today. Also, I have been using port forwarding for port 10308, and my 1 user was able to connect, but no one else was. I am the admin of this pc as well.

 

I don't know about this firewall/av binding to the net adapter, so I will read up on that. As well as try and bypass the router and other things to diagnose the problem. But this will take a while since I need to find at least two users to test this for me. So, it is a hassle to fix... I had been hosting Lockon, BS, and IL2 for a long time now. BS and IL2 work fine in Win7 64.

 

Thanks,

Snacko

[TheMoose]

You might want to look into these as well.

 

http://forums.eagle.ru/showthread.php?t=14350&highlight=host+timeout

 

..Eagle Dynamics\Lock On\Config\network\config.lua

 

And Edit this:

 

-- This file was automagically generated. Edit with care.

gameTimeout = 30;

maxPacketSize = 500;

playerName = "PlayerName";

idleTimeout = 120;

 

To:

 

-- This file was automagically generated. Edit with care.

gameTimeout = 500;

maxPacketSize = 500;

playerName = "PlayerName";

idleTimeout = 500;

 

 

http://forums.eagle.ru/showthread.php?t=10824&highlight=host+timeout

 

Go and change the timeout settings (everyone should do it)

It's in Lock On\Config\network\config.lua file

 

change gameTimeout to at least 120 (seconds) !

and IdleTimeout .. should be at least 120 too (I think it's default)

don't forget to save the changes

 

 

Cheers

[Panzertard]

Can you see traces of Event ID 4226 in your Event log?

Windows Vista tcpip.sys connection limit patch for Event ID 4226

You could be reaching the builtin conneciton-limiter on your hosting computer.

[TheMoose]

Can you see traces of Event ID 4226 in your Event log? Elaborate please?

 

Windows Vista tcpip.sys connection limit patch for Event ID 4226 a default installation, should not be an issue.

 

You could be reaching the builtin conneciton-limiter on your hosting computer.

 

NO disrespect but sounds like fancy talking, can you interpret in English?

Edited January 13, 2010 by TheMoose

[Panzertard]

Can you see traces of Event ID 4226 in your Event log? Elaborate please?

 

Windows Vista tcpip.sys connection limit patch for Event ID 4226 a default installation, should not be an issue.

 

You could be reaching the builtin conneciton-limiter on your hosting computer.

 

NO disrespect but sounds like fancy talking, can you interpret in English?

Windows allows for nn-amounts of network connections to your computer.

Several reason for this - but, if your computer has a lot of activity/connections (due to factors we dont know about) Windows may decide to;

- allow the first person to connect

- right after Windows notices the sum total of your (incoming) connections (from the same source - or so it belives), and starts blocking connections.

- not until some of your connections (players / bit torrent / lan traffic etc) goes away, you wont be able to let other people in to your computer.

 

Windows Home editions supports fewer connections. (Due to licensing, microsft want to force people over to the expensive editions I guess).

Pro / Ultimate editions support more connections but they too have a limit. (To prevent your computer from dying to a denial of service attack).

 

So why would you have this issue, and others not?

It depends on your sum of computer configuration and what kind of internet connection / Router config / NAT configuration you use (more tech talk, sorry).

 

So - unless you can use the "suggested patch" I linked, and see if it makes any difference.

And open teh Event-log for your computer, go look for the Event with ID 4226.

But again, this can be a dead-end leading nowhere just as the other suggestions.

Edited January 13, 2010 by Panzertard

[Panzertard]

And, just an afterthought - it can be as simple as upgrading;

- Chipset drivers for your mainboard

- network adapter drivers for your network interface.