PDA

View Full Version : The hells up with steam?



Pyong Kawaguchi
May 29th, 2009, 09:09 PM
I swear, about every 5-30 seconds, steam will disconnect, then reconnect a few seconds later, making TF2 unplayable, and to make things worse, for the few times I have been able to play for a bit, my loadout is not availiable
What the hell is going on?

Sel
May 29th, 2009, 09:11 PM
you should fix it










































because its your problem

Timo
May 29th, 2009, 09:12 PM
Is working fine for me :x

Pyong Kawaguchi
May 29th, 2009, 09:18 PM
This is seriously pissing me off, and Im sick of restarting steam

Atty
May 29th, 2009, 09:29 PM
Do what probably hundreds of goons in pubs have told you to do: Uninstall.

Hint: Don't reinstall.

hth

Pyong Kawaguchi
May 29th, 2009, 09:39 PM
:'(

p0lar_bear
May 29th, 2009, 09:43 PM
Is your router set to put your computer in the DMZ?

Turn that off, it fucks with Steam.

InnerGoat
May 29th, 2009, 10:27 PM
Actually steam was updating some shit hope this helps

=sw=warlord
May 30th, 2009, 09:11 AM
Is your router set to put your computer in the DMZ?

Turn that off, it fucks with Steam.
I've never had a issue with DMZ...

Pyong Kawaguchi
May 30th, 2009, 11:57 AM
Yeah, the problem just started after TF2 updated....

paladin
May 30th, 2009, 02:19 PM
Ive been on it all morning no problem.

Pyong Kawaguchi
May 30th, 2009, 03:23 PM
I've restarted my computer, my router, my internet, steam everything
still this problem.

p0lar_bear
May 30th, 2009, 04:21 PM
I've never had a issue with DMZ...Neither did I until a day before the Sniper/Spy update.

https://support.steampowered.com/kb_article.php?ref=6776-MYXU-0480


Steam does not support gameplay on machines operating in a network DMZ. You must remove your machine from the DMZ in order to play through Steam.

Pyong Kawaguchi
May 30th, 2009, 05:16 PM
Idk what it was, but its working now, I think my router changed my local ip and fucked up port fowarding.
I didnt have dmz before btw

CodeBrain
May 30th, 2009, 09:35 PM
For other people still having this problem, try deleting ClientRegistry.blob

That worked for me.