Recently, players who share a LAN connection are being kicked for unknown GUID. This is due to the recent PB update which references the same IP, not GUID numbers. To combat this issue during matches, server admins can peruse the following release notes from PB.
"PB_SV_GUIDRELAX 1" is the recommended solution for unknown GUID kicks. Originally, PB would verify only the first instance of an IP, which disallowed any subsequent authorization of same IP addresses, resulting in a kick for that GUID. For matches, use said PB command, which will enable the CoD authentication server to recognize different GUID's within one internet protocol.
Please alter your PB cfg accordingly to fix this issue.
I will be keeping you all up todate on this issue when anything new arises.
TWL|FastNFurious
TeamWarfare Competition Staff
Email: FastNFurious@teamwarfare.com
IRC: #teamwarfare, #twl_cod
Thursday 02.03.2005 [8:45PM]
Release Notes for PB Server v1.134:
the pb_sv_task command no longer requires quotes around the third [command] parameter when spaces are embedded now kicks players with "UNKN" GUID status; note: admins may set pb_sv_lan and/or pb_sv_lanmask appropriately for LAN players who would otherwise receive UNKN GUID status
"PB_SV_GUIDRELAX 1" is the recommended solution for unknown GUID kicks. Originally, PB would verify only the first instance of an IP, which disallowed any subsequent authorization of same IP addresses, resulting in a kick for that GUID. For matches, use said PB command, which will enable the CoD authentication server to recognize different GUID's within one internet protocol.
Please alter your PB cfg accordingly to fix this issue.
I will be keeping you all up todate on this issue when anything new arises.
TWL|FastNFurious
TeamWarfare Competition Staff
Email: FastNFurious@teamwarfare.com
IRC: #teamwarfare, #twl_cod