03-21-2010, 01:36 AM
Er.. not sure if its permanently fixed, but for now it seems I solved the issue...
I don't know if it was that I set the IP and port in the command line or that I opened ports in the firewall (Which shouldn't have solved anything since my firewall was disabled and the issue happened before I re-enabled it).
Anyway, I opened the following in CSF:
Yes, I manually enabled each port instead of doing a port range...
Like I said, not sure if its fixed or if the valve master server somehow memorized my server IP. But I now no longer have steam_id_pending myself.
I don't know if it was that I set the IP and port in the command line or that I opened ports in the firewall (Which shouldn't have solved anything since my firewall was disabled and the issue happened before I re-enabled it).
Anyway, I opened the following in CSF:
Quote:TCP IN: 27015,27020,27021,27022,27023,27024,27025,27026,27027,27028,27029,27030,27031,27032,27033,27034,27035,27036,27037,27038,27039
TCP OUT: 27015,27020,27021,27022,27023,27024,27025,27026,27027,27028,27029,27030,27031,27032,27033,27034,27035,27036,27037,27038,27039
UDP IN: 1200,27000,27001,27002,27003,27004,27005,27006,27007,27008,27009,27010,27011,27012,27013,27014,27015
UDP OUT: 1200,27000,27001,27002,27003,27004,27005,27006,27007,27008,27009,27010,27011,27012,27013,27014,27015
Yes, I manually enabled each port instead of doing a port range...
Like I said, not sure if its fixed or if the valve master server somehow memorized my server IP. But I now no longer have steam_id_pending myself.