Steam 설치
로그인
|
언어
简体中文(중국어 간체)
繁體中文(중국어 번체)
日本語(일본어)
ไทย(태국어)
Български(불가리아어)
Čeština(체코어)
Dansk(덴마크어)
Deutsch(독일어)
English(영어)
Español - España(스페인어 - 스페인)
Español - Latinoamérica(스페인어 - 중남미)
Ελληνικά(그리스어)
Français(프랑스어)
Italiano(이탈리아어)
Bahasa Indonesia(인도네시아어)
Magyar(헝가리어)
Nederlands(네덜란드어)
Norsk(노르웨이어)
Polski(폴란드어)
Português(포르투갈어 - 포르투갈)
Português - Brasil(포르투갈어 - 브라질)
Română(루마니아어)
Русский(러시아어)
Suomi(핀란드어)
Svenska(스웨덴어)
Türkçe(튀르키예어)
Tiếng Việt(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
You must have configured your current network to be "public". Public/private doesn't have anything to do with whether it connects to the internet.
Do you know how to solve this on a Mc Afee Firewall?
On different router all fine, so looks like it's router configuration problem, but for now I don't know what exactly causes problem.
Thanks for the update. Try enabling UPnP in the router if it's currently disabled. The ports UDP 7884 and TCP 7889 are being used specifically, in case you need to open them somehow.
If you can manage to get it to work with your original router, please let us know if it's something completely different, we're working on improving the instructions. Best we can detect/fix from the application directly is likely only the Windows firewall configuration, everything else we'll try to describe better on the website.
Well then you know at least it's not your router or either PC, it's the phone. Some phones allow turning off network or wifi access per app, some have built-in VPNs, any of that would prevent the devices from seeing each other. Or even an anti-virus app that is intercepting all traffic could just be swallowing it. Most of these things don't even produce errors that we could use to help determine the issue, that's what makes this so difficult.
If the firewall is the issue then either you accidentally denied access when Windows prompted you or Windows didn't prompt you to allow the program to access the network. It might have been a while ago already, but the firewall rule sticked.
If you have any ui32.exe rules, just set them to be allowed or remove them, so Windows prompts you again.
We will make this easier by showing a warning and attempting to fix it programmatically, but the issue can still be something else entirely. The firewall is the only part we can access from the program.
You're right I fixed it. I was editing the rules for "Wallpaper Engine" instead of "ui32.exe" within my firewall settings. Noticed ui32.exe and allowing it through fixed my issue, thanks.