Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Thank you for the help, Ardenol. That actually was the case.
With some trial & error I found out my PC software "BitDefender Total Security 2015" to be the one actually blocking the log-in process.
By deactivating the firewall I could get the game running. The problem is that my system firewall mostly serves as a tool to block communication of certain programms and I can't keep it deactivated just for playing your game. I simply don't want some programms to send out data without reason and then not even asking me.
Would you be so kind to tell me for which files I should set an exception for, so I could keep the firewall running while playing?
Thank you.
Thank you for your help. I will make it work!
1. Check if a firewall is blocking the log-in by deactivating it and trying to log-in without the firewall(s) being active.
2. If so:
a. Keep your firewall(s) deactivated for the time you play Dirty Bomb.
b. Activate your firewall(s) but set an exception for the game.
3. If not: Make sure you actually deactivated ALL your firewalls for testing purposes.
4. If still not: Ask for help again.
There's probably one active in your wireless router too.
Well, opening your eyes and looking at RECENT post might help ><
http://steamcommunity.com/app/333930/discussions/0/530646080866089406/
I was having the same problem with the same firewall and followed your steps, which fixed the problem, but since the Pheonix update I have to disable my firewall again. Any ideas?