Help

[davidpulwer]

Hi,
I can't connect to steam anymore , I also can't connect to other online games , but Steam is my main problem . I can surf in the internet . Thanks in advance .

[Vampire]

Same Problem cant log in to steam !!!

[Tev]

Can you try this?:

1. Can you right mouse click your Steam shortcut
   
2. Properties
   

3. Target -field

   
   
   Change this

   "C:\Program Files (x86)\Steam\Steam.exe"

   to

   "C:\Program Files (x86)\Steam\Steam.exe" -tcp

4. OK
   
5. Try to launch Steam through the shortcut.

[Vampire]

Originally posted by Teutep:

Can you try this?:

1. Can you right mouse click your Steam shortcut
   
2. Properties
   

3. Target -field

   
   
   Change this

   "C:\Program Files (x86)\Steam\Steam.exe"

   to

   "C:\Program Files (x86)\Steam\Steam.exe" -tcp

4. OK
   
5. Try to launch Steam through the shortcut.

it worked thank you very much .. but can you tell us or explain why it happened it was working fine before ... it was without -tcp

[Tev]

Originally posted by Vampire:

Originally posted by Teutep:

Can you try this?:

1. Can you right mouse click your Steam shortcut
   
2. Properties
   

3. Target -field

   
   
   Change this

   "C:\Program Files (x86)\Steam\Steam.exe"

   to

   "C:\Program Files (x86)\Steam\Steam.exe" -tcp

4. OK
   
5. Try to launch Steam through the shortcut.

it worked thank you very much .. but can you tell us or explain why it happened it was working fine before ... it was without -tcp

The -tcp launch parameter basically overrides certain UDP ports Steam utilizes.

I don't unfortunately know what causes the ports to be blocked, but it seems to be a rather common issue at the moment. If it was on Steam's end it would be happening to everyone; and if it was a geologically based issue it would be easier to narrow down to a geographical area, which it isn't.

The issue does affect server connections (those that use Source Dedicated Servers), because whatever issue there may be seems to also block the UDP ports range 27000-27030. The -tcp launch parameter likely overrides only the UDP 4380.

There's likely something on your computer that does it, because other users have gotten rid of it with a reformat for one. Just that it has to be something many other people have in common; which I personally don't have.

[Vampire]

Originally posted by Teutep:

Originally posted by Vampire:

it worked thank you very much .. but can you tell us or explain why it happened it was working fine before ... it was without -tcp

The -tcp launch parameter basically overrides certain UDP ports Steam utilizes.

I don't unfortunately know what causes the ports to be blocked, but it seems to be a rather common issue at the moment. If it was on Steam's end it would be happening to everyone; and if it was a geologically based issue it would be easier to narrow down to a geographical area, which it isn't.

The issue does affect server connections (those that use Source Dedicated Servers), because whatever issue there may be seems to also block the UDP ports range 27000-27030. The -tcp launch parameter likely overrides only the UDP 4380.

There's likely something on your computer that does it, because other users have gotten rid of it with a reformat for one. Just that it has to be something many other people have in common; which I personally don't have.

got it thanks