ZA and Symantec's products add hooks to low-level operating system functions that cause everything from web browsing to game playing to slow down. Members of my family have used both and form experience ZA seemed to work but at a huge cost to network performance, and Symantec just plain broke EVERYTHING.
With Symantec's Norton Personal Firewall, one day everything would work fine, the next day nothing would work at all and no rules changed. Manual rules were simply ignored whenver the product pleased and it ended up needing to be uninstalled to do something as simple as surfing the web! If someone using them is getting this error I would seriously consider uninstalling them and see if that fixes the problem. I don't have enough experience uninstalling Zone Alarm to comment on if it indeed leaves it fruits on the tree. -sb On 6/19/05, Ook <[EMAIL PROTECTED]> wrote: > ZoneAlarm is notorious for blocking stuff it should not - even when it isn't > running. Anytime I trouble shoot a connectivity problem, one of the first > things I do is make sure they are not running ZoneAlarm or any form of > Symantec security, as both of them are known to block things that should not > be blocked. Then I check to see if ZA or Symantec has been installed but > either was not running, or had been removed (ZA is notorious for leaving > parts of itself behind, still running, after it's been "uninstalled"). > > I once had a server that would run just fine. I tried to set up a second > server on the same box, and it kept giving some weird connectivity error. No > matter what I did, it would not work. I swapped ports with the good server, > and found that the good server would work on different ports, and the bad > one would not work, even on the same port the good server worked on. I > *finally* realized that ZoneAlarm had been installed on that computer, and > even though it was not running, the good server was in some rule somewhere > and therefore worked. The bad server was not in the rules (executable was in > a different directory) and therefore was blocked. The was the last time I > ever used ZoneAlarm. > > > > > Some people have been reporting this on the Steam Forums, but thus far > > I have no reasolution posted on any of those threads, mostly > > suggestions of making sure ports are open. Are any of them using > > firewall software or routers? One of the threads in the forum was by > > a guy using ZoneAlarm but he maintained it wasn't blocking any > > necessary ports. > > > > -sb > > > > On 6/19/05, GiZm0r <[EMAIL PROTECTED]> wrote: > > > HI > > > > > > Some Players on my server get kicked from vac2 on mein CS:S server > > > with this message (No Steam Logon) > > > And after this, he gets the message: > > > "connection to the steam VAC servers could not be made. For > > > truobleshooting network isssues, please click the link below" > > > when he try to connect > > > > > > Anyone knows anything about it? > > > > > > Thx > > > > > > > > > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
