Sniffer Pro 4.5 reboots machine

[jcomellas]

I have recently installed Sniffer Pro 4.5 in my Win2K Pro (with SP1) system. The installation seems to work fine but my PC reboots one time after another. The only solution I've found is to boot on 'protected mode' and remove the program.
Do you have any idea about how to solve this problem?

TIA!

 

[Guest_imported]

Has anyone experienced NAI Sniffer pro 4.5 crashes on NT server 4.0 SP6

When NT server boots into the login mode the sniffer will attempt to load after the ntoskernl loads thus causing the server to crash.

You will get a Blue Screen pointing to Sniffer.sys as the last item that caused the crash. Unfortunately this crash happens so quickly that you do not have time to kill the process and eventually the memory dumps.

Does anyone know how to stop the Sniffer.sys module from loading before the ntoskrnl can safely load so that you can remove the sniffer program?

 

[wybnormal]

You could try boot from last known good config.. one of the menu items on the boot screen.. it *should* pull up the last good registry. This doesn work if you have managed to get to boot after the crash. If you have your ERD disk, you can recovery that way. You can use the *repair* option of NT Setup which rewrites the core files AND/OR the registery.. you would need to reapply the service pack.

You could boot off a dos floppy.. use a NTFS driver and edit the registry manually ( danger!!danger!!)

MikeS
"Diplomacy; the art of saying 'nice doggie' till you can find a rock" Wynn Catlin

 

[Guest_imported]

Sniffer 4.5 is supported under Win98, NT4sp6, and Win2k (both sp1 and sp2 have been tested). While it should run properly under NT Server as well, this is not officially supported;

You could have one of the following problems:
1) multiple processors; Sniffer does not run properly on a computer with multiple processors, and such a configuration would not enhance the performance of the Sniffer anyway

2) You might have another protocol analyzer/packet capture shim/service installed, like the Microsoft Network Monitor service; this would be bad!

3) You might have a VPN client or some other low-level network shim installed on your system.

When all else fails, use our approved Xircom NIC (for laptops) or Adaptec NIC for workstations, with ONLY the Sniffer service bound to the card. This will eliminate almost any problem.

Booting into 'safe mode' or VGA mode, will typically allow one to uninstall Sniffer without problems. Otherwise, you could boot from another NT system (or floppy disk with NTFS access) and rename/delete the sniffer.sys from the winnt/system32 directory so it can't load.

Hope this helps!

Jeff Fanelli
Sniffer SE - Detroit