Jump to content

SmirnJoV

Members
  • Content Count

    3
  • Joined

  • Last visited

About SmirnJoV

  • Rank
    Candidate
  1. We've had the same problem with our winxp sp2 workstations. On one of your crashing workstations view the boot.ini file (located in the c:\ root). Open it using notepad, it should look something like this: [boot loader] timeout=0 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=Optin /fastdetect Try and change /noexecute=Optin to /noexecute=AlwaysOff and see if that helps, if the problem isn't solved you can always start the client in the last known good configuration, but if it is the same problem that we had (memory dump when rebooting) it is possible that this fixes the situation...
  2. Thanks for all the reactions, but none of the offered solutions seem to help. After two months of trying, changing settings, patches en fixes I give up. At the moment we just do an on demand scan of the hard drives on the remote xp sp2 clients, that works without errors, but it isn't what I expect from Kaspersky as a business solution. The clienst begin to whine about not being scanned for a long time, just because I can't perform a remote scan of "my computer" on them... The problem seems to be in the mailbox files, and I've read quite a lot about those in this forum, so I guess the problem is known, but where's the solution? I don't understand how a commercial product like Kaspersky can be released as a server / client solution when it obviously has bugs when it comes to mailboxes. A lot of servers are win2003 and on those machines mostly exchange 2003 is used. If there comes a solution to this problem (and not patch to 202, doesn't help either), please let me know. Thanks all
  3. Hi all, Recently we bought Kaspersky at our company (7 employees). We purchased a server licence and 10 client licences. At first we used it on our company network that consisted of windows 98 SE client computers and a windows 2000 server. That gave no real problems except it seemed to slow down the computers (They were older computers too then). Now since a week we have new client pc's, intel PIV HT with windows XP SP2 installed on them (100% clean install, no recovery or so). We also have a new Windows 2003 Server. On the server we have the admin kit running. The remote installation of the network client and the packages was no problem at all. The policies are all enforced, again no problem at all. But when I add a new task, for an on demand scan, all the client computers give this error: "Unhanded exception 0xC0000005 occured at address 0x35F73BBA on thread 0x00000AC0 in proces 708". The only thing you can do is accept the error (or cancel but that makes no difference) and the computer hangs for about 2 minutes. After that you can work slowly with almost no network connectivity. So you have to reboot in order to be able to work again... Now I'm really wondering what the problem is, cause in my opinion, and the opinions I've read, heard from others, I don't do anything wrong, I simply ask the clients to scan. I also have a laptop (AMD Athlon XP mobile - with windows XP SP2) (so it differs from the other client computers) that I've put in my company's domain and done a remote install on (the network client and the package) but also when I make a task for an on demand scan, it gives the same problem. Is there anyone who can help me solve this problem cause I've tried a lot of things but can't seem to solve it... All help is appreciated ! Thanks
×
×
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.