(unkown error) 118

[tigerman05]

Hello

I am having a problem with the steam community page (also affected are store and news tabs) on steam.... i get the 118 error. I have identified that its not a problem either with the firewall, antivirus or gmaeoverlayui. It has been 2 weeks since i decided to 'wait it out'. The problem has not fixed itself nor have i've been able to fix it myself. No website has been helpful at all at this problem. Hope i get a reply soon .

_tigerman05_

[kraze1994]

Restart Steam,

If that does not help delete the clientregistry.blob file out of your Steam client files and restart Steam.

[tigerman05]

Originally Posted by kraze1994

Restart Steam,

If that does not help delete the clientregistry.blob file out of your Steam client files and restart Steam.

does not work

[MikeBlaszczak]

Deleting clientregistry.blob is always bad advice, and particularly so in this case.

Knowing if you can see http://www.steamcommunity.com/ from another browser on the same system would be a good diagnostic step, as would doing a ping and tracert to the www.steamcommunity.com site.

[tigerman05]

Originally Posted by MikeBlaszczak

Deleting clientregistry.blob is always bad advice, and particularly so in this case.

Knowing if you can see http://www.steamcommunity.com/ from another browser on the same system would be a good diagnostic step, as would doing a ping and tracert to the www.steamcommunity.com site.

I tried the steam community on firefox, IE and chrome... Needless to say all 3 failed to load the page. 'The connection has timed out' it says

[MikeBlaszczak]

Actually, saying that isn't needless. It's an incredibly important diangostic point; if the pages worked in the other browser, we'd know there's not a problem with your machine or your route to the Steam websites. I'm sorry you thought it was pointless.

[tigerman05]

Originally Posted by MikeBlaszczak

Actually, saying that isn't needless. It's an incredibly important diangostic point; if the pages worked in the other browser, we'd know there's not a problem with your machine or your route to the Steam websites. I'm sorry you thought it was pointless.

Sorry, my mistake. I am not from America and i do not speak perfect english thats why sometimes i mess things up :P

So you're saying it could be my machine or router right? I think the culpret might be my router.. I shall check if there were any changes made to it.

[kraze1994]

Originally Posted by MikeBlaszczak

Deleting clientregistry.blob is always bad advice, and particularly so in this case.

Why would that be bad advice? I see that get recommended many times by users and I have done it several times and it has solved a lot of my problems.

[MikeBlaszczak]

Originally Posted by kraze1994

Why would that be bad advice? I see that get recommended many times by users and I have done it several times and it has solved a lot of my problems.

It causes lots of defaults to be reset; sometimes erroneously. It also destroys any chance of finding the cause of the problem. In this case, it's completely inappropriate advice because nothing stored in clientregistry.blob influences the way web pages are rendered in the client browser -- it's just a waste of time for an already frustrated customer.

It's pretty rare that deleting the file fixes anything. Lots of "problems" are really just transient network issues between the client and the various Steam servers, or problems on the servers themselves. When the user deletes the file then returns, the issue has cleared up and it's just coincidental that deleting the file appears to have had an effect.

In the cases that resetting the defaults stored in the file would fix anything, a better idea is to rename the file. That way, the client will create a new file, accomplishing the new settings. If the change doesn't fix, the old file can be replaced to regain the user's settings. If the change does cause a fix, we can use the old file to see what might have been the problem.

Indeed, this bad advice is deeply entrenched in the culture of the forums. It'll take some time and considerable effort to change it.

[kraze1994]

Originally Posted by MikeBlaszczak

It causes lots of defaults to be reset; sometimes erroneously. It also destroys any chance of finding the cause of the problem. In this case, it's completely inappropriate advice because nothing stored in clientregistry.blob influences the way web pages are rendered in the client browser -- it's just a waste of time for an already frustrated customer.

It's pretty rare that deleting the file fixes anything. Lots of "problems" are really just transient network issues between the client and the various Steam servers, or problems on the servers themselves. When the user deletes the file then returns, the issue has cleared up and it's just coincidental that deleting the file appears to have had an effect.

In the cases that resetting the defaults stored in the file would fix anything, a better idea is to rename the file. That way, the client will create a new file, accomplishing the new settings. If the change doesn't fix, the old file can be replaced to regain the user's settings. If the change does cause a fix, we can use the old file to see what might have been the problem.

Indeed, this bad advice is deeply entrenched in the culture of the forums. It'll take some time and considerable effort to change it.

Makes sense, I honestly did not know what the file did exactly but it seems to have placed a placebo affect on me and many others, so it makes sense that it would be default fallback when there are no better ideas.

Either way thanks for clearing that up.

[tigerman05]

I've confirmed that nothing has been changed to the router

[B33 ENN]

Originally Posted by tigerman05

I tried the steam community on firefox, IE and chrome... Needless to say all 3 failed to load the page. 'The connection has timed out' it says

Originally Posted by tigerman05

I've confirmed that nothing has been changed to the router

Can you follow through on Mike's other suggestions:

Originally Posted by MikeBlaszczak

Knowing if you can see http://www.steamcommunity.com/ from another browser on the same system would be a good diagnostic step, as would doing a ping and tracert to the www.steamcommunity.com site.

1 - Go to {START} >> [Run...]

2 - In the box that appears, type "cmd.exe", and press [OK]

3 - In the new window that appears, type:

ping www.steamcommunity.com

4 - Press [Enter] and wait for the command prompt to reappear.

5 - Next type:

tracert www.steamcommunity.com

6 - Press [Enter] and wait until you see "Trace complete".

7 - <Right-Click> in the window, and click [Select All]

8 - Press [ENTER] on your keyboard to copy the text to Clipboard.

8 - Paste the information here so we can see the results

[tigerman05]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\tigerman> ping www.steamcommunity.com

Pinging www.steamcommunity.com [63.228.223.103] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 63.228.223.103:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\tigerman>
C:\Users\tigerman>tracert www.steamcommunity.com

Tracing route to www.steamcommunity.com [63.228.223.103]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    11 ms     8 ms    20 ms  89-212-0-1.gw.t-2.net [89.212.0.1]
  3    61 ms     8 ms     7 ms  84-255-209-145.core.t-2.net [84.255.209.145]
  4     8 ms    10 ms     9 ms  212.162.28.13
  5    28 ms    30 ms    27 ms  ae-10-10.ebr2.Frankfurt1.Level3.net [4.69.151.18
6]
  6    27 ms    41 ms    26 ms  ae-82-82.csw3.Frankfurt1.Level3.net [4.69.140.26
]
  7    26 ms    27 ms    26 ms  ae-81-81.ebr1.Frankfurt1.Level3.net [4.69.140.9]

  8    36 ms    36 ms    36 ms  ae-45-45.ebr2.Paris1.Level3.net [4.69.143.134]
  9   114 ms   115 ms   114 ms  ae-42-42.ebr2.Washington1.Level3.net [4.69.137.5
4]
 10   116 ms   116 ms   114 ms  ae-62-62.csw1.Washington1.Level3.net [4.69.134.1
46]
 11   120 ms   123 ms   150 ms  ae-1-60.edge1.Washington4.Level3.net [4.69.149.1
5]
 12   114 ms   120 ms   120 ms  CenturyTel-level3-xe.washington4.Level3.net [4.6
8.63.82]
 13     *        *        *     Request timed out.
 14   218 ms   188 ms   198 ms  63-234-174-50.dia.static.qwest.net [63.234.174.5
0]
 15   191 ms   192 ms   191 ms  c1-tuk-tuk-b1.valve.net [208.64.202.18]
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Thats what i got.. i cant receive no pings from it.
Also i have tried to go to the site through another computer from the same router and it did not work.
I have also checked to see if my friend with the same internet provider can connect and he can :/

[Mangr0v3]

That's odd. Here are the last three hops of a traceroute from my machine:

  9   188 ms   187 ms   187 ms  63-234-174-50.dia.static.qwest.net [63.234.174.50]
 10   191 ms   188 ms   193 ms  c1-tuk-tuk-b1.valve.net [208.64.202.18]
 11   189 ms   188 ms   188 ms  steamcommunity.com [63.228.223.103]

My ninth hop corresponds to your 14th, so logically what should be 16 on your traceroute is the actual Steam Community website. I'd guess either there's a problem on their end, or something is actively blocking everything - even ping packets - from Steam Community.

[MikeBlaszczak]

Originally Posted by tigerman05

Thats what i got.. i cant receive no pings from it.
Also i have tried to go to the site through another computer from the same router and it did not work.
I have also checked to see if my friend with the same internet provider can connect and he can :/

What is your IP address? It's odd that you get to the edge and not to the server.