| All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
| Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
SFU 3.5 and VirScan bsod
|
Logged in as: Guest |
| Users viewing this topic: none |
|
Login  |
|
|
 SFU 3.5 and VirScan bsod - Jan. 11, '06, 6:26:15 AM
|
|
|
admkris
Posts: 2
Joined: Jan. 11, '06,
Status: offline
|
I was happily using SFU and VirScan 7.1 from McAfee.
We decided to upgrade VirScan to release 8.0, and now the system crashes BSOD.
We have reinstalled SFU 3.5, VirScan 8.0 and W2K SP4 machines, but system still crashes.
Crashes seems to indicate a Pb in kernel or in TCP stack.
Has anyone already come across this situation ?
Thanks Christian
|
|
|
|
|
RE: SFU 3.5 and VirScan bsod - Jan. 11, '06, 11:29:20 AM
|
|
|
Rodney
Posts: 3696
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
This will be a McAfee bug.
There have been, before, virus scanners causing problems (various companies).
The AV "software" usually consists of one or more device drivers that wedge
themselves between the kernel and the actual drivers. If they don't handle
everything as they should or return an incorrect value, then you're toast.
I've sent a "head-up" to PSS. But it'll still be a McAfee problem to fix.
|
|
|
|
|
RE: SFU 3.5 and VirScan bsod - Jan. 11, '06, 12:00:28 PM
|
|
|
admkris
Posts: 2
Joined: Jan. 11, '06,
Status: offline
|
What do you mean by: "I've sent a "head-up" to PSS. But it'll still be a McAfee problem to fix." ?
BTW how do you handle the situation where the problem is in between two sides ?
As McAfee replies my soft is working ans so do Microsoft ?
Christian
|
|
|
|
|
RE: SFU 3.5 and VirScan bsod - Jan. 11, '06, 12:48:51 PM
|
|
|
Rodney
Posts: 3696
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
> What do you mean by: "I've sent a "head-up" to PSS. But it'll still be a McAfee problem to fix." ?
Just means I sent a message to the the PSS (MS Support) section that specifically handles SFU/Interix
about this problem appearing. Just so they are aware of it.
> BTW how do you handle the situation where the problem is in between two sides ?
I'd approach McAfee and tell them that their software has regressed.
Things worked before with an earlier version. Nothing else has changed on the system for
hardware or software. Upgrading the McAfee AV software causes other applications to
hit the McAfee regression causing the BSOD. A level 1 (low) support tech may or may not
understand and you may have to try to escalate it to a higher level support tech
who does know about SFU so they can test/confirm it themselves.
If that doesn't work then the path to follow is open a ticket through Microsoft and
then Microsoft will tell McAfee the same dang thing. McAfee should then listen.
Doing it this way, since it's not an MS problem per se, will likely result in a support charge.
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
|
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|
Printable Version
