GW vs. Norton Internet Security

Anyone else have problems with Norton Internet Security locking GW after each update?

Once GW has updated and tries to connect to ANet, NIS pops up a "high risk" requester, and regardless of whether I say 'permit all connections' or 'permit no connections', GW locks up. As the GW process is locked in a state listening for a connection, it can't be killed with the task manager.

The only solution I've found, is to go into NIS settings, and manually enter the GW.exe client, then restart the computer through cycling the power (shutdown/restart doesn't work as the GW process can't be stopped). Considering how often GW is updated, this is bloody annoying. And risky.

Now, the problem probably resides with NIS, but do you other guys using NIS have this problem?

No. After each update Norton Internet Security will say I should not allow access. I just override it every time. That is how I see if there is an update. This is on my older computer. On my brand new computer with NIS it "sees" Guild Wars as an OK program and allows it.

Go figure.

I use NIS and I just permit it after every update and tell it to remember the action. I've been trying to find a way to make it work forever, but, the little pop-up warnings aren't that annoying.

I've encountered this exact same situation every GW update -- grant permission for GW.exe and move right along. No pop-up warnings until the next GW update.

However...once, after an update to NIS, I had to manually permit GW access.

It just means Norton is working correctly since the .exe has changed. Like they said: authorize it and move on.

Jeddak: the thing is that authorizing it doesn't work. NIS gets a rule which says 'allow all connections', but the GW.exe it stopped is still running, so I can't start a new one, and not kill the old one. Restarting the computer doesn't help, as the NIS rule applies to the old version, and the story repeats.
The only solution I've found is to go into NIS, kill the existing rule, make a new rule manually, then restart the computer through cycling power.

As it works for some/most/all except me, I suspect the problem may be a bug in the networks driver, so I've updated my nforce driver now - it was quite old. Hopefully the problem is now gone, I'll find out at the next update.

I don't mind. There's not an update everyday and all you're doing is hitting ok . For all the things Norton detects for me I don't mind hitting ok.

In ZoneAlarm/Kerio, you can authorize a program by "path name only"...i.e. updated versions retain rights. Poke around to see if Norton has a similar option, which is fairly common in firewalls.

I use ZoneAlarm... the personal version is free, and when GW updates, I just give the updated version permission to go thru ZA.

GW > Norton's firewall. I use hardware firewall,no problem for me