12-17-2008 06:26 PM
12-17-2008 06:42 PM
Sorry, I meant to get back to you yesterday on this and forgot. Tim's post just reminded me. We've identified a problem that could cause this problem on Vista machines. If you are running Vista and would like to try out the fix before its final release, please let me know.
How about XP? I reported this problem on October 21st and so far... no fix!
12-18-2008 06:17 AM
All of the machines in our office are Windows XP.
The issue only occurs if the 'file-serving" XP machine has NAV 2009 installed. I 'fixed' the network by removing NAV 2009 and reinstalling NAV 2008.
I figured out the problem by uninstalling 2009 and am not willing to break my network again in order to troubleshoot the 2009 issue.
As others have reported this same issue, you should be able to duplicate such problems easily in your test labs.
12-18-2008 12:58 PM - edited 12-18-2008 01:22 PM
I'm experiencing the same issue that everyone else is experiencing. Upgraded from NAV 2007 to NAV 2009 in the last 2 days, but ever since then none of my workstations is able to connect to the computer we use as a file/application server. All of the 9 computers (8 clients, 1 "server") have the following specs:
NAV 2009 184.108.40.206 on all computers (upgraded from NAV 2007)
AutoProtect enabled (what is the point of NAV if you have to disable this?)
All Intrusion Prevention Settings are enabled (but computers never show up on blocked list, so I don't think this is the problem)
All computers are "found" and visible on NAV's Home Network (LAN)
Windows XP Pro SP2 on all computers (all latest patches installed)
Windows Firewall enabled
Certain folders are shared on the network
No trouble with NAV 2007
Do you think adding each computer again to "NAV's Home Network (Trust Control)" will solve this problem? (I'm skeptical since all the computers are found in NAV's Home Network (LAN) to begin with.)
Does NAV 2009 have a "white list" where we can add IP/MAC addresses of computers we DON'T want NAV 2009 to block? (I remember seeing a setting somewhere asking if you wanted to allow Network LAN computers to be excluded from blocking, but I forgot where I saw that...)
Every 1-2 hours we need to reset the "server" because it starts to block traffic from all the computers in our network. Obviously this is NOT an acceptable "solution", so Symantec better solve this problem soon... because I'm getting really annoyed with this problem and tired of restarting the "server" so many times a day!
12-29-2008 03:56 AM - last edited on 12-30-2008 05:50 AM by Tony_Weiss
I'm having the same exact issues. Four computers, two Dell Dimension desktops, two Dell D-series Latitude laptops, all running Windows XP Pro, SP3. All worked fine using Norton Antivirus 2008, until "upgrading" the "server" (i.e., the one with the shared drive containing all our business files) to Norton Antivirus 2009.
The server could access all the others, but none could access the server; even though they could all "see" it on the network, access was denied. I figured maybe an incompatibility between 2008 and 2009, so put 2009 on the rest, but a few hours later, got universally shut out, none of the computers could access any of the others. I tried running the network wizard again, created a new netsetup.exe which I ran on all the other machines.
Everything works fine immediately after rebooting the computers, but anywhere from a half hour to a couple days later, access is again denied.
This was reported to tech support on 12/25/08, case number [removed].
The tech rep had me remove and reinstall 2009 on two of the machines, turn off SONAR, add IP addresses for the other computers to the trusted list on the server and all seemed OK for the moment. He tried repeatedly to get me to acknowledge that the problem was fixed, and I repeatedly told him that it always workd fine right after rebooting, so how do I know? I asked him to keep the case open for a few days.
I was hopefully optimistic, but on 12/27/08, once again, none of the computers could access any of the others.
I'm going to contact tech support again, and if there's no fix for 2009, go back to 2008. Problem is, what do I do in a couple months when my subscription to 2008 runs out? Go back to rebooting several times a day, or wait for 2010?
12-29-2008 06:07 AM
You can renew your licenses online but keep using NAV 2008. That's still only a temporary solution though.
Since Symantec is obviously ignoring this issue, the ultimate solution will be to use a competing product. Start looking now.
(Will that get a response? Probably not)
12-29-2008 11:04 AM
Yes, as noted, the subscription can be renewed under NAV 2008, but it seems kinda dumb to renew 2008 for a year if there's at least one newer version, soon to be two. I spent five hours in Norton's chat room this morning chatting with four different tech reps and two case supervisors/case managers. First case manager insisted the problem must be with my network or Windows settings, can't be with Norton. So, says I, here's what we'll do: we'll remove all NAV 2009 from all my computers, and reinstall NAV 2008. When nothing bad happens after a week, we'll pick a computer, any computer on my network, install NAV 2009, and I guarantee within two days it will drop off the network.
It was then, but only then, that he admitted there is a problem with NAV 2009, and they're working on a patch. He then offered to extend my subscription for 30 days, which gets me past my busiest period of the year, and meanwhile, maybe they'll have NAV 2009 fixed.
So, I uninstalled 2009, re-installed 2008 throughout the network, and inter-computer access is normal on every machine. However, the 30-day extension didn't show up. I tried to re-enter chat, worked my way up to the second case manager, but then kept getting disconnected; tried to send an e-mail, but the e-mail contact page kept redirecting me to chat. Finally called on the telephone and actually spoke to a real live person who got the subscription extension recognized in just a few minutes.
Bottom line is, Norton has a problem, they know it, and supposedly they're working on it, but it seems mighty odd that one would have to go through so much harassment to get to this point. Why didn't the first person I contacted know this? And why wouldn't the case manager admit it sooner?
Anyhow, thanks to all who posted here, this gave me the confidence to pursue a solution, once I knew I wan't the only one having this issue. Happy New Year, everybody!
12-29-2008 03:24 PM - edited 12-29-2008 03:29 PM
Thanks for your patience and for the detail of your reports.
Did you see this message up the thread a little that confirms there is a problem and they are working on it?
I'm glad you got a bonus!
See you around.
12-29-2008 05:26 PM
Yes, noted the earlier note regarding Vista. Seems odd that they would acknowledge Vista problems while seeming to know nothing about XP. They offer solutions that don't fit, I think, just so we'll fiddle with something so we won't have time to bother them any more. "Here, try this, now go away and leave me alone." If that's their attitude, why do they even bother having tech support?
Yeah, great bonus, works out to maybe thirty cents an hour for all the time I spent.