The Snap is the only box guaranteed to be on 24x7x365, so http does not work for me. I'd be happy to assist Eset in debuggging whatever problems...
Thanks too Marcos, I tried again, but now I changed the account settings I use. Maybe the default setting could be 'Current user' instead of...
Thats the problem. It IS the correct userid and password ... It works some of the time. I suspect the times it does not are those times when Nod32...
The SNAP is the only box that is guaranteed to be on 24x7x365, so I would prefer to serve the files from there. Bob
Can anyone tell me what could cause the sort of failures listed below? I have my mirror setup on a locally attached SNAP server and have update...
Re: NOD32 2.50.7 Beta - Comments & Opinions I have the admin version. If I install the beta on top of it, will I retain the admin functionality?...
Since updating to build 1124 of Corporate Workstation the daily scheduled incremental backups on several of my client PC's has been failing with...
That was it. Thanks.
So I haven't seen any more update failures on the box that I put the beta on, but I have noticed that since I installed it, my PC never goes to...
I will try it, thank you.
It is already scheduled that way. I think the problem is that it is setup to run hourly. That means that if it has been at least an hour since it...
I keep all my computers setup so that they sleep after 30 minutes of inactivity (they're all on UPS's so it is a convenient way to have them all...
I am from Hyde Park, NY USA, which is about 75 miles north of NYC in the Mid-Hudson valley. Hyde Park is home to two major tourist sites, the...
I have symptoms similar to this with build 930 of Corporate Desktop/Agent. There are two problems. (1) From a local computer I use the...
Where does nod32 keep its list of servers to try? I notice the help says to try www.esetsoftware.com and/or www.nod32.com, but neither of those...
Yep, same here ...
Efficiency, I believe. I will try it the other way and report back. Thanks for the suggestion. Cheers, Bob Cronin
First off, a brief comment about the lsass.exe problem I had so much trouble with last month. It seems to have been solved by the latest beta....
So, here's what AT&T had to say ... ----- In reality I think this is NOD32 problem. The faults you indicate don’t involve us. We just happen...
I have sent an inquiry to the development/support team for the AT&T VPN client infoming them of my findings and asking if they have any ideas what...
Although it *is* interesting that it does not happen if imon is deactivated, so perhaps there is some interaction amongst all these components...
Of course, this means that someone has got to go try to convince Microsoft to fix the sasser-worm windows update to not get upset by some other...
Ok, some more news. I narrowed it down a bit more. Since the AT&T VPN client has a proprietary implementation of IPSEC, one of the things it does...
Ok, I managed to capture the info from the VPN client bringup log from around the time of the error in imon.dll. Here it is, interspersed with...
I regularly get this problem whenever I try to establish a VPN session to my company's network using the AT&T 5.09.2 VPN client. Someone mentioned...
Separate names with a comma.