Why am I getting kicked for PB Guid Auth: UNKN?
The "PB GUID AUTH: UNKN" kicking means that your Game client is not sending a valid cdkey to Raven's cdkey auth server. Usually this is due to a problem with your cdkey entry. Exit SoF2 and then use your Windows explorer program to find the "base\mp" folder where SoF2 is installed on your system and delete the file called sof2key. Launch SoF2 directly and before you get to the game's main menu, it should ask you to enter your cdkey. If this does not fix the problem, then perhaps there is some type of firewall or security software blocking your game's communication to Raven's cdkey auth server. Be sure that UDP port 20112 is open for clear communication if you have a firewall or some type of security software.
If you are running a SoF2 dedicated server with PB on your own PC or in your LAN and have internet connection on this server, you have to use the pb_sv_lanmask setting added since PB Server v1.039 as described in our documentation. If you do not use this you will be kicked. The reason is that when you connect to a LAN game your game client does not send any information to the Auth Server. However, the PB Server will contact the Auth Server and find that your GUID is unknown.
As of PB Client 1.043, we have a new PB command called pb_cdkeyver which forces PB to send a Cdkey Authorize packet to Raven's Cdkey Auth Server for players who get GUID UNKN on PB Servers. Try entering /pb_cdkeyver into your console before joining a server to see if that helps.
Note: A cdkey is only valid if you bought the game and have a cdkey on your cd-case! Using a cdkey generator will allow you to overcome the checksum check within SoF2, stating that your cdkey is valid - it is only valid for single player though and will not allow you to play on the internet.
ni dus eh