Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 2 subscribers
  • Views 11886 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Unable to log into Steam

MikeRM275
Hello,

    Having an issue with Steam.  keep getting a warning from the App that: Steam is having trouble connecting to the Steam servers.

I have watched the logs when hitting login and have only pulled the following in the logs:

Firewall:
:22:27 Default DROP TCP   
192.168.0.22 : 2518 
 → 
208.64.200.201 : 27020 
   
[SYN] len=48 ttl=127 tos=0x00 srcmac=18:03:73:ca[:D]d:f3 dstmac=00:15:5d:00:1a:04 
 
Web Filtering:
2015:05:13-16:16:13 MRM2Sophos httpproxy[5213]: id="0001" severity="info" sys="SecureWeb" sub="http" name="http access" action="pass" method="GET" srcip="192.168.0.22" dstip="208.64.202.85" user="" ad_domain="" statuscode="200" cached="0" profile="REF_DefaultHTTPProfile (Default Web Filter Profile)" filteraction="REF_DefaultHTTPCFFAction (Default content filter action)" size="2998" request="0xe2245000" url="api.steampowered.com/.../

Now correct me if I am wrong it looks like the Web Filter is allowing it through, but the Firewall is dropping the service?

Now I feel that I have everything configured correctly:  I have the following firewall rules and Web Filtering Rules.
Firewall:
UDP 27000:27015
UDP 27015:27030
TCP 27014:27050
UDP 4380
All of these are in a Group Called Steam with Internal Network to Any

Web Filtering:
Steam 
Skipping: Antivirus / Extension blocking / MIME type blocking / URL Filter / SSL scanning / Certificate Trust Check / Certificate Date Check 
Matching these URLs: ^https?://(?:\d{1,3}\.){3}\d{1,3}/depot/571/
^https?://([A-Za-z0-9.-]*\.)?steampowered\.com/
^https?://([A-Za-z0-9.-]*\.)?steamcommunity\.com/
^https?://store\.akamai\.steamstatic\.com/
^https?://([A-Za-z0-9.-]*\.)?steamstatic\.com/
^http?://([A-Za-z0-9.-]*\.)?steampowered\.com/ 
 

Anyone see anything wrong with this?  Otherwise I have no idea why this will not work.


This thread was automatically locked due to age.
Parents
  • 0
    Mike, the Firewall Live Log is not very useful for seeing WHY something was blocked.  Please post the corresponding line from the full Firewall log file.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0
    Mike, the Firewall Live Log is not very useful for seeing WHY something was blocked.  Please post the corresponding line from the full Firewall log file.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
  • 0 in reply to BAlfson
    We tried ALL the configurations options based on Valve's recommended FW rules for Steam, and finally ended up with this iteration to get a working config. We have low latency pings and the performance is very good.  It seemed the overlapping UDP ports may have been causing our initial failed attempts. 

    Ironically, I just found this thread as we were trying to disable our FW rule and hoping to get the Layer 7 - Application Control to mange (replace) the rule. 

    Our config in a group of services, as follows:

    Int - TCP 27014-27050 - Any (IPv4)
    Int - UDP 27000-27036 - Any (IPv4)
    Int - UDP 4380 - Any (IPv4)
    Int - UDP 3478 - Any (IPv4)

    We have those grouped as a single rule WITHOUT Application Control enabled.

    We just tried the Application Control (all Steam rules) w/o our FW rules and it didn't work. 

    Good luck.

    Jack.
Unfiltered HTML