USER ID ticket

Greenmarine · 11-20-2011, 02:43 AM

I get a (error verifying steam user id ticket). I'm no stranger to this from the TFC days. I tried restarting steam that didn't help, So I deleted the steam.dll , steamUI.dll and the clientregistry.blob. That didn't help either. All other games valve and non valve games work fine in multi-player. It's only FF and so far I've tried just about every server and they all give me the same ID ticket error.
Ive searched the forums here to see if anyone else had the same problem in the past and all I found was a link to a steam help page that tells me to do what I already did. I have changed nothing nor have I added any new hardware or software. Running windows7 64, MSI 790fx-gdr790 mobo, 4 gigs ddr3-1333 ram, AMD 970X4 phenomII, two AMD HD4870's crossfired.

any help would be greatly appreciated

**squeek.** · 11-20-2011, 02:48 AM

Might want to submit a Steam support ticket or ask on the Steam forums as nothing has changed on FF's end. A few others have this problem and nothing seems to fix it.

Atreuce · 11-20-2011, 05:13 AM

I got a ticket in... but they are taking forever to reply. Trailer and I are having the same issue. Deleted all the files, restarted, checked file integrity, etc etc etc...

sucks

FDA_Approved · 11-20-2011, 05:52 AM

The only current solution I've seen people come up with is make a new steam account. And it works I saw someone else do it earlier and then get in game.

Good temp solution untill it can be figured out.

KubeDawg · 11-20-2011, 06:57 AM

Steam was hacked recently, so this may have something to do with that. I'd advise updating your passwords and info.

Greenmarine · 11-20-2011, 02:30 PM

Quote:

Originally Posted by KubeDawg

Steam was hacked recently, so this may have something to do with that. I'd advise updating your passwords and info.

Allready done

I have a ticket in with steam as well but it seams they could care less about third party mods. My thought is that if some people have this problem and some don't then it might stem to my ISP, maybe the routing is different in a way that causes a problem, I find this strange as the trace route to the server had only 5 hops and all of them were under 50ms. just thinking out loud.

Anyhow thank you for the input
Greenie

Greenmarine · 11-20-2011, 06:19 PM

OK steam got back to me with this message...It didn't help me but I'll post it in case it helps someone else.

Invalid Steam UserID Ticket

Question

I'm getting an Invalid Steam UserID Ticket, how do I fix this?

Answer

You are trying to connect to your own server.
If you have a server and a client behind the same router:

You will not be able to connect your client to your server from behind the router using the external IP address. You will not be able to connect to the Server by clicking on it in the full server browser window.

In fact, you will probably not be able to even see your Server in the ServerBrowser Window.

You must use the internal IP address.

What you do is go to:
Steam > Servers > Favorites then add your internal Server IP and port

For example: 192.168.1.100:27015 if this is what your Server says when you type in "Status" in the Server console.

Then always connect to your server from the favorites menu.

Two or more clients behind the same router
You might get this or an "expired" SteamID ticket if you are behind a router with other players and you are all trying to connect to the same server. Here is a detailed FAQ with information on how to fix this:

How can I have multiple clients playing games behind a router at the same time?

Log out and exit
If this is a problem for you on all servers then you can try fixing this problem by logging out of Steam and then logging back in again.

Check your Clock Settings
If this doesn't work then you need to check the date, time and year on your computer to make sure they are set properly. This should not be an issue with Steam itself, but it is a good idea to ensure it is set properly.

Two Computers, one Account Problem
Something else that can cause this is if there is another computer that is using the same Steam account.

When you log into a second computer with the same account that is running on the first, the Steam Ticket will invalidate on the first machine and transfer to the new Session.

This means that the first machine will then eventually prompt for a login to establish a new SteamUserID Ticket, and if the person on that machine logs in, then the ticket will then transfer back to him.

You need a unique Steam Account for each computer that is going to be online at the same time.

Stand-alone Server Uses a Steam Account
Stand-Alone Steam Dedicated Servers use a Steam Account, and if you are using the same Steam Account for your Stand-Alone Dedicated Server that you are using for your Client then this problem can occur as well.

Client Listen Servers and Client Dedicated Servers use the SteamID Ticket for the Client that they are run from so they don't have this problem.

Incompatible Networks
Complex Computer networks might be configured in such a way that the Steam client gets NAT translated twice before it can get to the Server. NAT translation is the process where many computers can share one IP address.

Steam works very well with NAT, but will not work with double NAT, Steam must be able to verify the identity of the client and validate the SteamUserID Ticket and double NAT will prevent this from happening. There are no plans to modify Steam for this situation.

Router Issues
Another cause of this problem is if you are trying to connect to your own server and both the server and client are behind the same router.

In this case, you must connect to the server using the internal IP address and not the external IP address. An easy way to do this is to add the Server internal IP address and port to your client "Favorite Servers" and connect that way.

Dual WAN Networks and Routers
There are a few routers available that will accept two Internet connections and then manage the bandwidth so the client computers get better performance than just one connection. Unfortunately, since each WAN connection has a unique IP address, and client packets have a 50/50 chance of traveling through either path, this will also cause Invalid SteamUserID Tickets to happen.

If you are trying to connect to a local server where your LAN has two paths to the internet (two parallel NATs) and you are hosting a Server on one side, you can try to connect via the "external" IP instead of using the LAN IP. It might be best however to dedicate one WAN connection to just the Server and then have the other WAN dedicated for Clients. Clients would use the external (normal) Server IP then.

The bottom line is that one of these two things must be true:

a. The IP that the Game Server sees you connecting from is the same IP that the Steam network sees you connecting from, or

b. It must appear to Steam that your Client and the Game Server are using the same IP (you are both behind the same NAT).

If you are unable to meet these requirements then your network will be incompatible with Steam.

Other Possibilities:
If this happens when you try to connect to a server, it might be because the Server or the Steam network is having problems. You need to try a different server or check on the Steam Status page and see what the current status is:

http://www.steampowered.com/status/status.html

Normally, if this is a problem on your client (game) it will prompt you to renew your Ticket.

Iggy · 11-20-2011, 10:39 PM

Well, at least they got back to you.....

11-20-2011, 02:43 AM	#1
Greenmarine Beta Tester Join Date: Sep 2007 Posts Rated Helpful 0 Times	USER ID ticket I get a (error verifying steam user id ticket). I'm no stranger to this from the TFC days. I tried restarting steam that didn't help, So I deleted the steam.dll , steamUI.dll and the clientregistry.blob. That didn't help either. All other games valve and non valve games work fine in multi-player. It's only FF and so far I've tried just about every server and they all give me the same ID ticket error. Ive searched the forums here to see if anyone else had the same problem in the past and all I found was a link to a steam help page that tells me to do what I already did. I have changed nothing nor have I added any new hardware or software. Running windows7 64, MSI 790fx-gdr790 mobo, 4 gigs ddr3-1333 ram, AMD 970X4 phenomII, two AMD HD4870's crossfired. any help would be greatly appreciated __________________ netflix Junkie

11-20-2011, 02:48 AM	#2
squeek. Stuff Do-er Lua Team Wiki Team Fortress Forever Staff Join Date: Mar 2007 Location: Northern California Class/Position: Rallygun Shooter Gametype: Conc tag (you just wait) Affiliations: Mustache Brigade Posts Rated Helpful 352 Times	Might want to submit a Steam support ticket or ask on the Steam forums as nothing has changed on FF's end. A few others have this problem and nothing seems to fix it. __________________ #FF.Pickup ¤ Fortress-Forever pickups My Non-official Maps Released FF_DM_Squeek - FF_2Mesa3_Classic - FF_Siege_Classic Beta FF_Myth - FF_Redlight_Greenlight Sick of the people on the internet, always moanin'. They just moan. - Karl Pilkington

11-20-2011, 06:57 AM	#5
KubeDawg Nade Whore Server Owner Beta Tester Join Date: Sep 2007 Location: Oklahoma Class/Position: Scout/Soldier Gametype: CTF/TDM Affiliations: blunt. Moto Posts Rated Helpful 128 Times	Steam was hacked recently, so this may have something to do with that. I'd advise updating your passwords and info. __________________ Moto's Funhouse \| Dallas, TX - 74.91.114.247:27015 ff_plunder - Complete

11-20-2011, 06:19 PM	#7
Greenmarine Beta Tester Join Date: Sep 2007 Posts Rated Helpful 0 Times	OK steam got back to me with this message...It didn't help me but I'll post it in case it helps someone else. Invalid Steam UserID Ticket Question I'm getting an Invalid Steam UserID Ticket, how do I fix this? Answer You are trying to connect to your own server. If you have a server and a client behind the same router: You will not be able to connect your client to your server from behind the router using the external IP address. You will not be able to connect to the Server by clicking on it in the full server browser window. In fact, you will probably not be able to even see your Server in the ServerBrowser Window. You must use the internal IP address. What you do is go to: Steam > Servers > Favorites then add your internal Server IP and port For example: 192.168.1.100:27015 if this is what your Server says when you type in "Status" in the Server console. Then always connect to your server from the favorites menu. Two or more clients behind the same router You might get this or an "expired" SteamID ticket if you are behind a router with other players and you are all trying to connect to the same server. Here is a detailed FAQ with information on how to fix this: How can I have multiple clients playing games behind a router at the same time? Log out and exit If this is a problem for you on all servers then you can try fixing this problem by logging out of Steam and then logging back in again. Check your Clock Settings If this doesn't work then you need to check the date, time and year on your computer to make sure they are set properly. This should not be an issue with Steam itself, but it is a good idea to ensure it is set properly. Two Computers, one Account Problem Something else that can cause this is if there is another computer that is using the same Steam account. When you log into a second computer with the same account that is running on the first, the Steam Ticket will invalidate on the first machine and transfer to the new Session. This means that the first machine will then eventually prompt for a login to establish a new SteamUserID Ticket, and if the person on that machine logs in, then the ticket will then transfer back to him. You need a unique Steam Account for each computer that is going to be online at the same time. Stand-alone Server Uses a Steam Account Stand-Alone Steam Dedicated Servers use a Steam Account, and if you are using the same Steam Account for your Stand-Alone Dedicated Server that you are using for your Client then this problem can occur as well. Client Listen Servers and Client Dedicated Servers use the SteamID Ticket for the Client that they are run from so they don't have this problem. Incompatible Networks Complex Computer networks might be configured in such a way that the Steam client gets NAT translated twice before it can get to the Server. NAT translation is the process where many computers can share one IP address. Steam works very well with NAT, but will not work with double NAT, Steam must be able to verify the identity of the client and validate the SteamUserID Ticket and double NAT will prevent this from happening. There are no plans to modify Steam for this situation. Router Issues Another cause of this problem is if you are trying to connect to your own server and both the server and client are behind the same router. In this case, you must connect to the server using the internal IP address and not the external IP address. An easy way to do this is to add the Server internal IP address and port to your client "Favorite Servers" and connect that way. Dual WAN Networks and Routers There are a few routers available that will accept two Internet connections and then manage the bandwidth so the client computers get better performance than just one connection. Unfortunately, since each WAN connection has a unique IP address, and client packets have a 50/50 chance of traveling through either path, this will also cause Invalid SteamUserID Tickets to happen. If you are trying to connect to a local server where your LAN has two paths to the internet (two parallel NATs) and you are hosting a Server on one side, you can try to connect via the "external" IP instead of using the LAN IP. It might be best however to dedicate one WAN connection to just the Server and then have the other WAN dedicated for Clients. Clients would use the external (normal) Server IP then. The bottom line is that one of these two things must be true: a. The IP that the Game Server sees you connecting from is the same IP that the Steam network sees you connecting from, or b. It must appear to Steam that your Client and the Game Server are using the same IP (you are both behind the same NAT). If you are unable to meet these requirements then your network will be incompatible with Steam. Other Possibilities: If this happens when you try to connect to a server, it might be because the Server or the Steam network is having problems. You need to try a different server or check on the Steam Status page and see what the current status is: http://www.steampowered.com/status/status.html Normally, if this is a problem on your client (game) it will prompt you to renew your Ticket. __________________ netflix Junkie

11-20-2011, 05:13 AM	#3
Atreuce Tiny Asian Penis Man Beta Tester Join Date: Jun 2011 Location: South Carolina Class/Position: D - Engy/Demo Gametype: CTF/AvD Affiliations: rQ Posts Rated Helpful 12 Times	I got a ticket in... but they are taking forever to reply. Trailer and I are having the same issue. Deleted all the files, restarted, checked file integrity, etc etc etc... sucks

11-20-2011, 05:52 AM	#4
FDA_Approved Beta Tester Join Date: Nov 2011 Gametype: Capture the Flag Posts Rated Helpful 293 Times	The only current solution I've seen people come up with is make a new steam account. And it works I saw someone else do it earlier and then get in game. Good temp solution untill it can be figured out.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)