12-01-2008 08:28 AM
Right -- but the problem is that answers to your problem get fragmented and duplicated so it's better I believe to do one or the other but not both!
Anyway hang on in both places and see what develops -- I see that several Symanaec Staffers -- names in red -- were active in this one and now the holiday weekend is over hopefully some of them will be able to pick up the ball again.
12-01-2008 11:02 AM
I was posting on this thread also to let the original poster know that others are having the same issue.
Thank you. I might not have found your thread if you hadn't...
12-16-2008 08:53 AM - edited 12-16-2008 08:55 AM
I am having the exact same problem. Installed NIS 2009 (free upgrade from NIS2008) in an office with 8 desktops and 1 file sharing "server". All systems running Win XP SP3 fully patched and updated. This install took place Saturday Dec 13th, on Monday the 15th when the office was open, started having problems accessing shared files from the file server. Looked at the System event log and have many Warning events ID 2022 from the Srv (Server) Source.
Event ID: 2022
Description: Server was unable to find a free connection 6 times in the last 60 seconds.
I tried the suggestions from Microsoft at this link: http://support.microsoft.com/kb/317249, cannot make the registry changes for MaxFreeConnections and MinFreeConnections as they seem to only apply to actual Windows Server 2000 or 2003. I have made the performance changes to make CPU and memory prioritize background processes and I disabled Idle Scanning in NIS 2009.
Will find out today if any of this makes any difference, but based on what is being said here it looks like another site visit tonight to downgrade the server back to NIS 2008.
12-18-2008 11:38 AM
I downgraded the file server (a Win XP Pro box) and the issues with accessing its shared files and printers has disappeared. Now another Win XP Pro box in the same workgroup is having the exact same problems with other computers accessing its shared files. Looks like I am going to have to revert to 2008 on all the machines at this site.
Symantec????? Looks like your testing procedures need to be revisited.
12-18-2008 12:56 PM - edited 12-18-2008 01:23 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 126.96.36.199 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-18-2008 01:19 PM
You are more than welcome to try anything that comes to mind. Maybe you will find the answer to this problem. I worked on the problem for over a week – even completely disabling NAV2009 – but no matter what I tried, the server would lock up every hour or so.
The only solution that worked for me (and I think the rest of the users on this site) was to downgrade the server from NAV2009 back to NAV2008.
Just an FYI … my “server” is an XP Pro box now running NAV2008. My “clients” run XP Pro, Vista, and a Mac. Most of my clients are running NAV2008, but I do have two running NAV2009. I have not had an issue crop up since I downgraded the server. So, whatever the problem is, it must be with NAV2009 on the server.
12-18-2008 01:26 PM - edited 12-18-2008 01:28 PM
Well this is not reassuring... hopefully Symantec will release an update to NAV 2009 that will fix this problem (or at least tell us how to "white list" computers that we don't want blocked... or another acceptable workaround to this problem). Has anyone heard back from Symantec on a potential fix or acceptable workaround?
(Restarting the computer every hour or turning off Auto-Protect or uninstalling NAV 2009 are NOT acceptable workarounds from Symantec... YOU HEAR THIS SYMANTEC?!?!?!)