Disconnect: Error verifying STEAM UserID Ticket.

[scz]

I've searched up and down this forum and went through the faq's here and on the manual to no avail. I have HL2, HL2: LC & HL2: DM, as well as the Source SDK Base. So, I've dl'ed and installed the correct files. I'm able to create a server and play by my lonesome, but connecting to a server = fail. Here's what i get after it connects:

Disconnected
Disconnect: Error verifying STEAM UserID Ticket.

I can play my other steam games just fine, and am able to connect to hl2:dm servers. I got so excited when i found out about this mod and would really like to get into it. I'm an old TFC clan player from back before steam came to ruin our lives. *shakes fist*

Any help or suggestions are much appreciated.

[GeoKill----->]

I been getting the same thing, its a source error, not ff really. It happens in some servers, but not all of em.
http://www.google.com/search?q=Disco...L_enUS262US262

[Shadow00Caster]

Exit STEEM.
Delete clientregistry.blob in STEEM folder.
Restart STEEM.

poof.

[PoisonDuckie]

This still hasn't fixed my problem. I have tried numerous times with no luck. Only FF as far as I can tell.

[Dexter]

try this. clientregistry.blob deletion again. restart steam and verify source sdk base 2006 (in tools). then run FF. sacrifice goat

[Trailer]

I still am getting this error. =(

[Greenmarine]

This has not helped me but it might help you.

Close steam then go into your steam main directory and delete the following.

Clientregistry.blob, steam.dll, steamui.dll, steamclient.dll and if you are on a 64 bit OS then delete the steamclient64.dll. Restart steam, steam will update. This has helped some but it hasn't helped me good luck

[Greenmarine]

Originally Posted by Dexter

try this. clientregistry.blob deletion again. restart steam and verify source sdk base 2006 (in tools). then run FF. sacrifice goat

how do I verify sdk base 2006. Do you mean just make sure it's there or is there a way to verify, cause I'm not seing a verify tool in the drop down menu.

*UPDATE*
Nevermind...I had a brain fart,.....under properties

Nope that didn't help either..something is going on with steam with certain clients

[CINodras]

So far, even the goat hasn't worked for me. :/

In addition to deleting ClientRegistry.blob, Steam.dll, SteamUI.dll, steamclient.dll, and steamclient64.dll, restarting Steam, and verifying Source SDK Base 2006, I've also reinstalled the Fortress Forever client.

Edit: I wanted to add that I can connect to a VAC secured Garry's Mod server, so I can confirm that it does seem to be Fortress Forever related. I'm going to find another mod that uses the 2006 SDK, and see see if I can connect.

Edit2: I found this on the Half-Life 2 CTF forums. It looks like their mod is using the 2006 SDK as well. They suggest that you delete everything in your steam folder except Steam.exe, and the steamapps and friends directories. They mention that it will cause steam guard to trigger if you have it enabled. I'm going to give it a try, and see what happens. I'll let you know.

Edit3: It worked for me.

[Greenmarine]

*Another update*

I believe this issue is related to steam or client I don't believe it has anything to do with the server. Unless everyone that is having the problem has win7 64 bit and it is singular to that OS. I haven't done any needed updates since maybe 3 weeks ago and the problem has only been for a few days. I did do a Video driver VIA steam approx. 3 days ago I wonder if steam did something then. Did anyone else update drivers via steam before the issue started ?

I have Steam on another hard drive that is running WindowsXP under the same steam account. for shits and giggles I booted into winxp and tried to log onto the o-t server and some other servers. Everything worked fine no userid ticket error, no error at all of any kind. It has to be the way steam is verifying the client..something got messed up some how....oh well I'll keep working at narrowing down the problem.

[Greenmarine]

Originally Posted by CINodras

So far, even the goat hasn't worked for me. :/

In addition to deleting ClientRegistry.blob, Steam.dll, SteamUI.dll, steamclient.dll, and steamclient64.dll, restarting Steam, and verifying Source SDK Base 2006, I've also reinstalled the Fortress Forever client.

Edit: I wanted to add that I can connect to a VAC secured Garry's Mod server, so I can confirm that it does seem to be Fortress Forever related. I'm going to find another mod that uses the 2006 SDK, and see see if I can connect.

Edit2: I found this on the Half-Life 2 CTF forums. It looks like their mod is using the 2006 SDK as well. They suggest that you delete everything in your steam folder except Steam.exe, and the steamapps and friends directories. They mention that it will cause steam guard to trigger if you have it enabled. I'm going to give it a try, and see what happens. I'll let you know.

Just turn off steam gaurd to confirm...if you can log onto the the server with steam gaurd off then you know you can do the suggested before you go threw all that trouble. just thought

[vitz]

I've had the same problem for several days now... have tried:

• Deleting ClientRegistry.blob, steamui.dll, steamclient.dll, etc. and restarting.
• Reinstalled FF 2.43
• Tried disabling Steam Guard
• Tried changing my Steam server to a different region.

I may be remembering wrong, but this seemed to crop up only after I changed my Steam password (as advised due to the recent penetration).

I'm running Windows 7 SP1 64 bit.

[vitz]

Originally Posted by CINodras

Edit2: I found this on the Half-Life 2 CTF forums. It looks like their mod is using the 2006 SDK as well. They suggest that you delete everything in your steam folder except Steam.exe, and the steamapps and friends directories. They mention that it will cause steam guard to trigger if you have it enabled. I'm going to give it a try, and see what happens. I'll let you know.

This worked for me as well. Thanks for the info, I was starting to go through FF withdrawal.