CACE Technologies WinPcap

Views: 5.9k  |  Created: 01/31/2007

Average Rating: 0
WinPcap has 12 inventory records, 1 Questions, 0 Blogs and 0 links. Please help add to this by sharing more!

Deployment Tips (4)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 0 / 5 (Not Rated) based on 0 ratings
Most Commonly Reported Deployment Method
Not Determined
or cancel
119
Note

Cace WinPcap 4.0.2 is required for network packet sniffers such as WireShark. The vendor of this application has specifically disabled the ability to do a silent or unattended installation of this software. The setup is a Nullsoft Install with the /S switch disabled. You will need to repackage it as an MSI in order to achieve unattended installation. The problem is making sure that the services are populated in the services tables and not the registry table. If not the package will still work but a reboot will be required before use.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
4
Note
I tried to repackage the WinPcap driver to no avail. However, the NMap application has customised the WinPcap install to install silently. Download the package from here : http://nmap.org/download.html

Extract the WinPcap driver from the install and your in business!!!
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • Thank you worked like a charm. Keep up the good work! :)
Please log in to comment
4
Note
This looks old but since I have an answer I thought I would post it just in case it help someone else that comes across WinPcap.

Basically all WinPcap does is copy DLL's to their proper locations, then creates and starts a service that runs the npf.sys driver.

Here is what you need to do for a silent installation:

1. Extract the files from the WinPcap installer - using 7zip - using the autorename feature
2. There will be several duplicates that have a _1 or _2 etc on the end of their name
3. You will have to copy the proper versions of each file to their respecitive locations
4. Each file is for a different version of windows - jsut check the properties - details tab to see which version it is.
5. For 32bit Windows (I was using Windows 7) copy the following to C:\Windows\System32
Packet.dll
wpcap.dll
pthreadVC.dll

Then copy the driver to C:\Windows\System32\Drivers
npf.sys

Next create a service for the driver using the following command:
sc create npf binPath= system32\drivers\npf.sys type= kernel start= auto error= normal tag= no DisplayName= "NetGroup Packet Filter Driver"

For 64bit windows it is almost the same except the 32bit versions of the DLL's go into C:\Windows\sysWOW64
and the 64bit versions go into C:\Windows\System32

File names are the same so on 64bit you end up with a 64bit version in C:\Windows\System32
Packet.dll
wpcap.dll

32bit versions end up in C:\windows\System32
Packet.dll
pthreadVC.dll
wpcap.dll

Driver npf.sys ends up in the same place either way.

hope this helps someone
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
0
Note
An addition to the note above:
when distributing this from SCCM on a 64bit system (Windows 7 for me) you will have to copy the files from a 32bit process such as CMD.exe and utilize the %windir%\sysnative to get the proper files into the real system32 directory

If you use the normal cmd or xcopy the files will be redirected to C:\windows\Syswow64 and Wireshare doesn't like that! it wants packet.dll to be in the system32 native directory - who knew?

At any rate here was my work around:
use a CMD file as the initial program in the SCCM package
C:\windows\syswow64\cmd.exe /c "%~dp0<SilentInstall.cmd>

obviously that silentInstall.cmd file can be called whatever you want to name it

then inside the silentinstall.cmd file put your "copy" commands and use the sysnative directory for system32
example:
copy "%~dp0npf.sys" %windir%\Sysnative\drivers

then copy the sysWOW64 files into their directory using the normal syntax.

Hope that helps for sccm
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
This content is currently hidden from public view.
Reason: Removed by member request
For more information, visit our FAQ's.

Inventory Records (12)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

WinPcap

Version

4.1.0.2001

Uninstall String

C:\Program Files\WinPcap\uninstall.exe C:\Program Files (x86)\WinPcap\uninstall.exe E:\Program Files\WinPcap\uninstall.exe "C:\Program Files\WinPcap\uninstall.exe" C:\Programme\WinPcap\uninstall.exe D:\Program Files\WinPcap\uninstall.exe "C:\Programme\Win

Questions & Answers (1)

Questions & Answers related to CACE Technologies WinPcap

9
ANSWERED

Blogs (0)

Blog posts related to CACE Technologies WinPcap

Reviews (0)

Reviews related to CACE Technologies WinPcap