steam update

[HL2Fan]

Originally Posted by Z3D

*Sigh* AciD....

There's no easy way to put this and I lack the patience anymore to try.

Your assistance is equal to that of a drooling tard! Quoting the FAQ with assumption that it hasn't been consulted in detail100 times already is hardly helpful and ultimately adds to the frustration of the whole problem.

"Customer" My car won't start
"AciD" Try the keys

I'm personally sick of your post count buffing which utterly hinders us getting any real assistance.

STFU & PO..

What are your full computer specs? including router/modem, what security software do you use? operating system including service pack and what is your connection speed?

If you do have a router try going to its home page and disabling the firewall on the router then restart it (this is if you have a router) hardware firewalls tend to be extremely restrictive

[AciD]

Originally Posted by Z3D

[...]

It's not Valve's fault that you jumped on "Same error message it must be same issue" train. As you probably noticed that issue got fixed *some* time ago and your problem is still present. Why you didn't contacted Steam Support? Earlier you did not stated that you took any steps to troubleshoot your issue so I gave you a link to FAQ so you may try to troubleshoot yourself.

So this problem is solved and non-existent? that's wonderful news! /sarcasm

"Same error message it must be same issue train"
my problem is relevant to both the "time frame" and "symptoms" stated in this thread.. I fail to see this as simply coincidental.

The only thing that has changed is steam.. not my system, Steam worked perfectly fine prior the update.

Originally Posted by Z3D

... The only thing that has changed is steam.. not my system, Steam worked perfectly fine prior the update.

Exactly. Having also been someone who suffered through an unexplainable period during which I couldn't get Steam to update properly, I think you've hit the nail on the head.

I believe that every Steam update ends up causing problems for a very small minority of Steam users. Somewhere within the interplay of a new Steam update and our individually unique computer's system a problem occurs for a very few people. And the problem is so obscure (and individual) that it can't be easily identified or fixed.

However, there is some good news. The problem eventually goes away due to another future Steam update. There's really nothing that can be done, except to have some patience, and keep the faith knowing that a future update will find your system working perfectly again.

The problem occurs and is solved without apparent rhyme nor reason, however it is somewhere within the intersection of your unique computer system and the Steam update that it both happens and is fixed.

So, just wait... and make sure you update your Steam again after the next update. In all likelihood, as mysteriously as the problem happened, it will be solved... all due in some inexplicable reason to the character of the Steam update and your unique system.

It may be a few weeks, or a month, but I really believe that a future update will solve your probem, not deliberately, but as a matter of course.

[Akudama89]

Originally Posted by ComradeNachaev

Exactly. Having also been someone who suffered through an unexplainable period during which I couldn't get Steam to update properly, I think you've hit the nail on the head.

I believe that every Steam update ends up causing problems for a very small minority of Steam users. Somewhere within the interplay of a new Steam update and our individually unique computer's system a problem occurs for a very few people. And the problem is so obscure (and individual) that it can't be easily identified or fixed.

However, there is some good news. The problem eventually goes away due to another future Steam update. There's really nothing that can be done, except to have some patience, and keep the faith knowing that a future update will find your system working perfectly again.

The problem occurs and is solved without apparent rhyme nor reason, however it is somewhere within the intersection of your unique computer system and the Steam update that it both happens and is fixed.

So, just wait... and make sure you update your Steam again after the next update. In all likelihood, as mysteriously as the problem happened, it will be solved... all due in some inexplicable reason to the character of the Steam update and your unique system.

It may be a few weeks, or a month, but I really believe that a future update will solve your probem, not deliberately, but as a matter of course.

i hope you realize the post you commented on was 5 months ago, also, if people do have a problem like this, do you know if uninstalling steam, and trying to install it again, fixes it?

Originally Posted by Akudama89

i hope you realize the post you commented on was 5 months ago, also, if people do have a problem like this, do you know if uninstalling steam, and trying to install it again, fixes it?

As a matter of fact, there was a more recent post to this thread on August 20 by Ragin Caucasion which brought me here. Subsequently Ragin Caucasion's post has been removed. I assume not only his post, but his account likely, given his bogus name. Anyhow, upon reading over the last few posts, I decided to reply to Z3D's comment based on my personal experience with this problem.

As for your question regarding uninstall/re-install, nope it doesn't seem that people have success doing that. I really think it just requires waiting for a future Steam update which will fix the problem as mysteriously as the previous Steam update caused the problem.

[KillahInstinct]

Originally Posted by ComradeNachaev

As a matter of fact, there was a more recent post to this thread on August 20 by Ragin Caucasion which brought me here. Subsequently Ragin Caucasion's post has been removed. I assume not only his post, but his account likely, given his bogus name. Anyhow, upon reading over the last few posts, I decided to reply to Z3D's comment based on my personal experience with this problem.

Actually the thread was split up and his post was moved here (as it wasn't related to this topic), his account was not removed.

[stends]

I haven't had the chance to read the entire thread but the symptoms remind me of TCP mss adjustments done wrong or are not done at all. Essential ICMP packets are being dropped at some point between sender/receiver. TCP checksum is calculated and replaced but never verified. Many end-user routers have been known to fall into some or all categories in a seemingly random pattern.

TCP mss (maximum segment size) is a value in TCP packets with the SYN flag set that indicates the maximum TCP packet size on the TCP connections used for communication. Routers on the path between computers may lower this value if the path MTU is lower. Without this mechanism we would see a several second lag whenever we first sent an over sized TCP frame to any computer with a lower MTU than the sender.
The mechanism breaks down completely (And you'll experience the symptoms in the thread) when the following happens;

1) MTU is lowered at some link between sender and receiver AND tcp mss is not lowered appropriately AND ICMP fragmentation-needed packets are never received at the transmitting end.

2) MTU is lowered at some link between sender and receiver AND tcp mss is lowered but at some point another router increases it back up AND ICMP fragmentation-needed packets are never received at the transmitting end.

--

ICMP packets are sent by routers to indicate that when a frame, with Dont-Fragment set, is to be forwarded across a link that can't handle the frame's size it must generate an ICMP fragmentation-needed packet to sender of the over sized frame. If this is not sent or is dropped then sender will retry the same oversized frame until the TCP connection is considered dead.

Sometimes modems or network cards of any medium have had issues where certain combinations of bit patterns have resulted in wrong bit pattern transmitted or received, this can sometimes happen and is a flaw.

Additionally if corruption occurs on a frame, while in transit, and any of the routers in between never verifies the tcp checksum or ip checksum (but of course recalculates it and replaces the checksum in the frame) then you will experience broken TCP connections.

Encrypted connections are often more prone to failure. Not because they are encrypted but since an error is more likely to throw the upper layers out of sync and therefore either breaking the connection at roughly the same place.

Multiple paths between the two connection endpoints may attribute to the coming and going of this types of errors, for some.
In my experience low-end D-Link firewalls/routers tend to be the worst offender in all categories but i have not tried all brands.

http://media.steampowered.com/Steam/SteamFull.zip
went to that website and got a 404 not found error!
is there another website?

[Killerwatt]

Originally Posted by viper952

http://media.steampowered.com/Steam/SteamFull.zip
went to that website and got a 404 not found error!
is there another website?

As you see, that full installation zip was posted more than 2 years ago. So even if it worked, you would get a heavily outdated Steam installation, which would start updating with the newest release as soon as it's launched. So don't bother yourself with that.

Originally Posted by Killerwatt

As you see, that full installation zip was posted more than 2 years ago. So even if it worked, you would get a heavily outdated Steam installation, which would start updating with the newest release as soon as it's launched. So don't bother yourself with that.

damn
well
thanks for the info

[rlsuth]

Everything updated very quickly but only after I completely uninstalled Zone Alarm. After the update, I reinstalled and now have no problems. I'd love to know what Steam is trying to do that the firewall is blocking?