STEAM GROUP
Steam Client Beta SteamBeta
STEAM GROUP
Steam Client Beta SteamBeta
29,606
IN-GAME
98,743
ONLINE
Founded
January 8, 2013
All Discussions > Bug Reports > Topic Details
Melody Jul 26, 2019 @ 11:17pm
Since moving to my new house I need to login several times before it works
ISSUE
Since moving to my new house, I need to login several several times before it actually logs in.

OS
Microsoft Windows 10 1903 (build 18362.239)

STEPS
Open Steam
Type username and password and click Login

RESULTS
When clicking the Login button, all input boxes grey out and Steam hangs, forcing the user to close Steam, open Steam again and try to login again. It eventually works after trying twice or more times.

EXPECTED
Steam should login normally.

MORE INFO
The connection is definitely not the problem. The same issue happens on all systems while using the same connection, but the connection itself looks perfectly fine.
Speedtest: https://www.speedtest.net/result/8450762929.png
MTU Test: https://i.imgur.com/NUzgevm.png
netsh: https://i.imgur.com/YDG3V8n.png
UPnP and UPnP port mapping are enabled on the Gateway and working perfectly fine.
Any other application/service works perfectly fine, Steam is the only application giving issues.
< >
Showing 1-6 of 6 comments
Melody Aug 1, 2019 @ 11:52pm 
Sorry for bumping but I'm still having the problem and I really can't fix this. I tried with Windows 7 and I get the same exact issue. I contacted my ISP twice and, from what they've seen, they're 100% sure it's an issue with Steam not exchanging packets with clients properly.
Melody Aug 5, 2019 @ 1:05am 
Bumping for the last time then I will just give up on reporting this. Had to login 4 times this morning in order to make it work (lol). I streamed for almost 3 hours on twitch yesterday and had 0% lost frames. All other services still working fine except Steam's login procedure.
hexaae Aug 5, 2019 @ 2:52am 
Ciao, hai provato anche a impostare un DNS diverso?

CISCO UMBRELLA DNS (OPENDNS):
208.67.222.222
208.67.220.220

COMODO DNS:
8.26.56.26
8.20.247.20

YANDEX:
77.88.8.8
77.88.8.1

(safe)
77.88.8.88
77.88.8.2

NORTON:
199.85.126.10
199.85.127.10

ADGUARD (NO ADS):
176.103.130.130
176.103.130.131

(safe)
176.103.130.132
176.103.130.134

CLEANBROWSING:
185.228.168.168
185.228.168.169

CLOUDFLARE:
1.1.1.1
1.0.0.1

QUAD9:
9.9.9.9
149.112.112.112

DNS.WATCH:
84.200.69.80
84.200.70.40

ALTERNATE DNS (NO ADS):
23.253.163.53
198.101.242.72

KEWEON (NO ADS):
176.9.62.58
176.9.62.62

VERSIGN
64.6.64.6
64.6.65.6
Melody Aug 5, 2019 @ 3:01am 
Originally posted by hexaae:
Ciao, hai provato anche a impostare un DNS diverso?

CISCO UMBRELLA DNS (OPENDNS):
208.67.222.222
208.67.220.220

COMODO DNS:
8.26.56.26
8.20.247.20

YANDEX:
77.88.8.8
77.88.8.1

(safe)
77.88.8.88
77.88.8.2

NORTON:
199.85.126.10
199.85.127.10

ADGUARD (NO ADS):
176.103.130.130
176.103.130.131

(safe)
176.103.130.132
176.103.130.134

CLEANBROWSING:
185.228.168.168
185.228.168.169

CLOUDFLARE:
1.1.1.1
1.0.0.1

QUAD9:
9.9.9.9
149.112.112.112

DNS.WATCH:
84.200.69.80
84.200.70.40

ALTERNATE DNS (NO ADS):
23.253.163.53
198.101.242.72

KEWEON (NO ADS):
176.9.62.58
176.9.62.62

VERSIGN
64.6.64.6
64.6.65.6
Sì, 11 provider diversi.
Melody Aug 7, 2019 @ 12:21am 
I don't know how, but I finally managed to fix it. I don't know which of the following tweaks fixed it, but I will list all of them.
  • Changed interface metric to 100 in interface's IPv4 settings.
  • Changed gateway metric to 100 in interface's IPv4 settings (add gateway -> type gateway -> change metric to 100).
  • Set Jumbo Packet to 9KB MTU in interface's driver advanced settings.
  • Enabled NetBIOS in IPv4 WINS settings.
  • Unticked IPv6 in interface settings.
  • In HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters:
    DisabledComponents -> ff
  • In HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters and in each subkey in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces:
    TCPNoDelay -> 1 TcpDelAckTicks -> 0 TcpAckFrequency -> 1
  • In cmd as Administrator:
    netsh int tcp set global rss=enabled netsh int tcp set global autotuninglevel=normal netsh int tcp set global ecncapability=enabled netsh int tcp set global timestamps=enabled netsh int tcp set global initialrto=300 netsh int tcp set global rsc=enabled netsh int tcp set global nonsackrttresiliency=enabled netsh int tcp set global fastopen=enabled netsh int tcp set global fastopenfallback=enabled netsh int tcp set global hystart=enabled netsh int tcp set global pacingprofile=always netsh int tcp set supplemental internet minrto=300 netsh int tcp set supplemental internet congestionprovider=newreno netsh int tcp set supplemental internet enablecwndrestart=enabled netsh int tcp set supplemental internet rack=enabled netsh int tcp set supplemental internet taillossprobe=enabled netsh winsock set autotuning on
  • Download and run DNS Benchmark by Gibson Research Corporation.
    • Click Nameservers -> Build Custom List and let it run.
    • Click Run Benchmark and let it run.
  • Add the first 16 DNS servers in interface's IPv4 DNS settings.
  • Open inetcpl.cpl:
    • Go to "Settings" below, set disk space to 1024 MB, click "When opening a web page", click OK.
    • Go to security tab, click "Trusted sites" and set security to minimum. Click on "Sites", untick "Require https verification" and add the following:
    • Go to Connections tab, click LAN Settings and untick "Automatically detect settings".
  • In HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings, in HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings and HKEY_USERS\{ALL SUBKEYS}\Software\Microsoft\Windows\CurrentVersion\Internet Settings:
    SyncMode5 -> 3 AutoDetect -> 0
  • In cmd as Administrator:
    ipconfig /flushdns ipconfig /registerdns
  • In gpedit.msc:
    • Click Windows Settings, right click Policy based QoS and click Advanced, set DSCP override to allow.
    • Right click Policy based QoS and click add new. Type the full path of Steam executable without quotes and set DSCP to 46, set protocol to UDP only.
  • Wait a few minutes and reboot the system.
Last edited by Melody; Aug 7, 2019 @ 12:23am
Melody Sep 3, 2019 @ 1:09am 
It was fixed until today, which took literally 10 attempts before it actually logged in. Contacted my ISP again this morning and they repeated it's Steam not exchanging packets correctly.
< >
Showing 1-6 of 6 comments
Per page: 1530 50

All Discussions > Bug Reports > Topic Details
Date Posted: Jul 26, 2019 @ 11:17pm
Posts: 6