Wireshark для windows server 2008

The amount of resources Wireshark needs depends on your environment and on the
size of the capture file you are analyzing. The values below should be fine for
small to medium-sized capture files no more than a few hundred MB. Larger
capture files will require more memory and disk space.

Busy networks mean large captures

A busy network can produce huge capture files. Capturing on
even a 100 megabit network can produce hundreds of megabytes of
capture data in a short time. A computer with a fast processor, and lots of
memory and disk space is always a good idea.

If Wireshark runs out of memory it will crash. See
https://wiki.wireshark.org/KnownBugs/OutOfMemory for details and workarounds.

Although Wireshark uses a separate process to capture packets, the packet
analysis is single-threaded and won’t benefit much from multi-core systems.

1.2.1. Microsoft Windows

Wireshark should support any version of Windows that is still within its
extended support
lifetime. At the time of writing this includes Windows 11, 10,
Server 2022,
Server 2019,
and Server 2016.
It also requires the following:

  • The Universal C Runtime. This is included with Windows 10 and Windows
    Server 2019 and is installed automatically on earlier versions if
    Microsoft Windows Update is enabled. Otherwise you must install
    KB2999226 or
    KB3118401.
  • Any modern 64-bit Intel or Arm processor.
  • 500 MB available RAM. Larger capture files require more RAM.
  • 500 MB available disk space. Capture files require additional disk space.
  • Any modern display. 1280 × 1024 or higher resolution is
    recommended. Wireshark will make use of HiDPI or Retina resolutions if
    available. Power users will find multiple monitors useful.
  • A supported network card for capturing

    • Ethernet. Any card supported by Windows should work. See the wiki pages on
      Ethernet capture and
      offloading for issues that
      may affect your environment.
    • 802.11. See the Wireshark
      wiki page. Capturing raw 802.11 information may be difficult without
      special equipment.
    • Other media. See https://wiki.wireshark.org/CaptureSetup/NetworkMedia.

Older versions of Windows which are outside Microsoft’s extended lifecycle
support window are no longer supported. It is often difficult or impossible to
support these systems due to circumstances beyond our control, such as third
party libraries on which we depend or due to necessary features that are only
present in newer versions of Windows such as hardened security or memory
management.

  • Wireshark 4.2 was the last release branch to officially support Windows 10.
  • Wireshark 4.0 was the last release branch to officially support Windows 8.1 and Windows Server 2012.
  • Wireshark 3.6 was the last release branch to officially support 32-bit Windows.
  • Wireshark 3.2 was the last release branch to officially support Windows 7 and Windows Server 2008 R2.
  • Wireshark 2.2 was the last release branch to support Windows Vista and Windows Server 2008 sans R2
  • Wireshark 1.12 was the last release branch to support Windows Server 2003.
  • Wireshark 1.10 was the last release branch to officially support Windows XP.

See the Wireshark release lifecycle page for more details.

1.2.2. macOS

Wireshark supports macOS 11 and later.
Similar to Windows, supported macOS versions depend on third party libraries and on Apple’s requirements.

  • Wireshark 4.2 was the last release branch to support macOS 10.14.
  • Wireshark 3.6 was the last release branch to support macOS 10.13.
  • Wireshark 3.4 was the last release branch to support macOS 10.12.
  • Wireshark 2.6 was the last release branch to support Mac OS X 10.6 and 10.7 and OS X 10.8 to 10.11.
  • Wireshark 2.0 was the last release branch to support OS X on 32-bit Intel.
  • Wireshark 1.8 was the last release branch to support Mac OS X on PowerPC.

See the Wireshark release lifecycle page for more details.

The system requirements should be comparable to the specifications listed above for Windows.

1.2.3. UNIX, Linux, and BSD

Wireshark runs on most UNIX and UNIX-like platforms including Linux and most BSD variants.
The system requirements should be comparable to the specifications listed above for Windows.

Binary packages are available for most Unices and Linux distributions
including the following platforms:

  • Alpine Linux
  • Arch Linux
  • Canonical Ubuntu
  • Debian GNU/Linux
  • FreeBSD
  • Gentoo Linux
  • HP-UX
  • NetBSD
  • OpenPKG
  • Oracle Solaris
  • Red Hat Enterprise Linux / CentOS / Fedora

If a binary package is not available for your platform you can download
the source and try to build it. Please report your experiences to
wireshark-dev[AT]wireshark.org.

Introduction

This blog will teach you how Wireshark functions. We’ll walk you through where to find and install the Wireshark application on your PC or Server. You will learn how to start a packet capture and what data you may expect to receive from it. The Wireshark lecture will also show you how to utilize the data manipulation features in the interface fully. You’ll also learn how to get data analysis tools better than Wireshark’s built-in features.

What can you do with Wireshark?

As one of the most dependable network protocol analyzers on the market in recent years, Wireshark has gained a solid reputation. This open-source program has been used as a comprehensive network analysis tool by users worldwide. Users can use Wireshark to analyze network security vulnerabilities, debug protocols, and learn about network activities.

How to Use Wireshark

Wireshark is a network protocol analysis tool, as was already described. Wireshark’s primary function is to deconstruct data packets sent across various networks. The user can look for particular data packets and filter them, then examine their passage across their network. These packets can be examined either in real-time or offline.

The user can use this data to produce statistics and graphs. Originally known as Ethereal, Wireshark has become one of the most important network analysis tools. Users who want to view data from various networks and protocols should use this tool.

Both novice and professional users can utilize Wireshark. Once you understand how to capture packets, the user interface is easy to use. Advanced users can decrypt packets using the platform’s decryption capabilities as well.

Wireshark main Features

The main characteristics of Wireshark are listed below:

  • Take live packet data capture
  • Packets from text files imported
  • View the protocol and packet data information
  • Save packet data obtained
  • Display packets
  • Filter packets
  • Search packets make packets colorful
  • Generate Statistics

Most users use Wireshark to check their software and find network issues. Wireshark is an open-source project maintained by a special staff that upholds high service standards. We explain how to utilize Wireshark in this guide. The official user manual for Wireshark has more details.

How to Download and Install Wireshark

Downloading and installing Wireshark is the initial step before using it. The firm’s website offers Wireshark for free download. You should download the most recent version from the “stable release” section for your platform to get the smoothest operating.

https://www.wireshark.org/download.html

Install Wireshark on Windows Server

Once the application has been downloaded, you can begin the setup procedure. You might be prompted to install WinPcap during installation. WinPcap is essential since you cannot record live network data without it. Only stored capture files can be opened without WinPcap. Check the Install WinPcap box to install.

install wireshark on windows

Choose the installer (64-bit or 32-bit) appropriate for your Windows architecture before clicking the link to download the file.
1. To launch the downloaded file, click on it. In the User Account Control window, select Yes.
2. On the installer’s welcome screen, select Next.
3. Click the Noted button on the License Agreement screen.
4. The Choose Components screen’s default settings should be left alone. Then press the Next button.
5. Click Next after leaving the Additional Tasks screen’s options alone.
6. click Next after choosing your installation location.
7. Leave the Consent box checked and click the Next button on the Packet Capture screen.
8. Check the Install USBPcap box on the USB Capture screen, then click the Install button.
9. Allow the installation to go forward. You will see a consent screen for Npcap during the procedure. Click “I Agree.”
10. Check the boxes next to Support raw 802.11 traffic (and monitor mode) for wireless adapters, Restrict Npcap driver access to Administrators Only, and Install Npcap in WinPcap API-compatible Mode on the NPcap Installation Options screen. Select Install.
11. once the Npcap setup is complete. To close that dialog box, click Next, followed by Finish. The installation of Wireshark will proceed.
12. Click Next after the Complete Installation screen before selecting Finish on the following screen.

How to Capture Data Packets using Wireshark

Data packet capture is one of Wireshark’s main network analysis tool features. To perform in-depth network analysis, you must understand how to configure Wireshark to capture packets. It’s crucial to remember that if you’re unfamiliar with Wireshark, it can be challenging to capture packets. There are two things you must perform before you can begin to capture packets:

  • Ensure you have administrative rights before beginning a live capture on your device.
  • Select the appropriate network interface to use for packet data capture.

After completing these two steps, you are now prepared to begin the capture procedure. When you use Wireshark to capture packets, they are shown to the user in a format that is easy to read. You may also segment packets using filters and color coding to examine more detailed information.
The following launch screen will appear when you initially launch Wireshark:

launching wireshark

It would help if you start by examining the offered capture interfaces. Select Capture > Options to get started. After that, as seen below, the “Capture Interfaces” dialogue box will appear.
To begin, select the box next to the interface you wish to record, then click the Start button. You can choose different interfaces if you wish to collect data from several sources at once.
The toolbar’s shark fin button can also be used as a shortcut to start packet recording. This button will launch Wireshark and initiate the live capture procedure.

Click the red stop button next to the shark fin to end the capture.

Promiscuous Mode

You must switch to “promiscuous mode” if you want to generate an overhead view of your network packet transfers. In promiscuous mode, Wireshark examines each packet it encounters as it passes across the interface. When this mode is turned off, your network is less transparent, and you only get a restricted snapshot of it (this makes it more difficult to conduct any analysis).

Click on the Capture Options dialogue box, then select Promiscuous Mode to start the promiscuous mode. This should display all of the active traffic on your network, in theory. The below image depicts the promiscuous mode box:

wireshark promiscuous mode

But this frequently isn’t the case. You must visit the Wireshark website to find information about your particular hardware because many network interfaces resist promiscuous mode.

It’s helpful to launch Device Manager on Windows and verify that your settings are set to disallow promiscuous mode.
The promiscuous mode will be rejected if your settings are set to “reject,” reducing the number of packets Wireshark may collect. Check your Device Manager to make sure that your interface isn’t preventing any data from passing through, even if promiscuous mode is active in Wireshark. By looking through your network architecture, you can make sure Wireshark gets all the data packets it needs.

How to Analyze Captured Packets in Wireshark

It would help to examine your collected packets after collecting your network data. Three panes—the packet list pane, the packet bytes pane, and the packet details pane—can be seen in the screenshot below.

Any field in each packet can be clicked to get more details. The byte view section displays a breakdown of a packet’s internal bytes when you click on it.

Packet List

At the top of the screenshot is the packet list window. Each component has a number and information about the time, source, destination, protocol, and backing.

Packet Details

The middle contains packet information, which displays the chosen packet’s protocols. Each segment can be made larger by clicking the arrow next to the row you want to expand. You may easily add other filters by selecting the item with the right click.

Packet Bytes

The page’s footer displays the packet bytes pane. The internal data of the packet you picked is displayed in this window. When you select a portion of the data in this section and highlight it, the packet details pane also highlights the information that goes with it. By default, the hexadecimal format is used to display all data. Right-click the pane and choose this choice from the context menu to convert it to bit format.

How to Analyze Network Performance Using Wireshark

Close any running applications on your network before using Wireshark to examine your network and examine all live traffic. This will significantly lessen traffic, allowing you to see your network’s activity. However, even if you disable every application, you’ll still send and receive several packets.

The best way to analyze your network data is to filter these packets using Wireshark. Thousands of packets are moving through your network per second when your connection is active. To gain a clear picture of what’s happening, you must weed out the information you don’t need.

Capture Filters and Display Filters

Two filters can be applied on Wireshark: Capture Filters and Display Filters.

Two filters can be applied on Wireshark: Capture Filters and Display Filters. By essentially filtering out other packets during live packet capturing, capture filters are used to minimize the size of incoming packet capture. Therefore, before you start the live capture procedure, capture filters are configured.

By essentially filtering out other packets during live packet capturing, capture filters are used to minimize the size of incoming packet capture. Therefore, before you start the live capture procedure, capture filters are configured.

Once a capture has begun, Capture Filters cannot be changed. On the other hand, data that has already been recorded can be filtered using display filters. While viewing previously captured packets, Acquire Filters control what data you see, and Display Filters control what data you capture from real-time network monitoring.

Using the filter box beneath the toolbar is one of the simplest ways to begin filtering your data. You will be given a list of all HTTP packets recorded, for instance, if you type HTTP into the filter box. When you begin typing, an autocomplete field will appear.
Once you begin capturing live network traffic, your changes will take effect if you decide to create a capture filter. Simply click the arrow to the right of the entry area to activate a display filter. Alternatively, you can select a filter from the list of defaults by selecting Analyze > Display Filters.

After selecting a filter, you can see the TCP discussion hidden behind a packet. Click Follow > TCP stream in the right-click menu of the packet to accomplish this. This will display the client and server’s TCP communication.

Using Color Coding in Wireshark

The Wireshark color-coding feature not only filters which packets are displayed or captured but also makes it simpler for the user to distinguish between various packet kinds based on their color. For instance, light purple and light blue indicate TCP and UDP traffic, respectively. The usage of black to denote packets containing mistakes must be noted.

In Wireshark’s default settings, you have a selection of about 20 colors. These can be modified, turned off, or removed. To disable colorization, go to the View menu and select the Colorize Packet List field option. Click View >Coloring Rules to view additional details about Wireshark’s color-coding system.

Viewing Network Statistics in Wireshark

The statistics drop-down option is immensely helpful for viewing more details about your network. The statistics menu, located at the top of the screen, provides several metrics, including size and time data and plotted charts and graphs. You can also apply display filters to these statistics to focus on key information.

Network Packet Visualization Using IO Graphs

Open IO graphs are required if you wish to build a visual representation of your data packets. Pick IO graphs from the statistics menu by clicking on them.
You can configure IO graphs using your settings depending on the data you wish to present. By default, only graph 1 is active; to enable graphs 2 through 5, you must click on them. Similarly, to apply a display filter to a graph, click the filter icon next to the desired graph. You can modify the structure of your graph using the style column. Line, bar, Dot, or Impulse are your options.

You may also play about with the X and Y axis measurements on your graph. The tick interval parts on the X-axis let you choose the interval length, from minutes to seconds. To change the time displayed on the X-axis, you can also select the view as a time of day checkbox.

You can select the following options for the unit of measurement under the Y-axis section: Packets/Tick, Bytes/Tick, Bits/Tick, or Advanced. The scale lets you select the measurement scale for the graph’s Y-axis.

The graph is then saved in the file format you choose after selecting the “Save” button.

How to Use Wireshark’s Sample Captures

Using “sample captures” is an excellent alternative if you want to practice using Wireshark, but your network is inaccessible for any reason. Sample captures provide you access to packet data from another network.

Conclusion

This finishes our explanation of Wireshark’s usage. This platform is a very flexible network analysis tool, regardless of whether you are a beginner or an experienced Wireshark user. It is strongly advised that you conduct more research on the Wireshark website if you want to make the most of this program.

This is even more crucial if you want to employ more sophisticated features and build your own protocol dissectors. The official Wireshark user manual is the most thorough source of information on the subject.

СКАЧАТЬ

Описание

Отзывы

Выберите вариант загрузки:

  • скачать с сервера SoftPortal (для Windows 64-bit, установочный exe-файл)
  • скачать с сервера SoftPortal (для Windows 64-bit ARM, установочный exe-файл)
  • скачать с сервера SoftPortal (portable-версия для Windows 64-bit, exe-файл)
  • скачать с официального сайта (для Windows 64-bit, установочный exe-файл)
  • скачать с официального сайта (для Windows 64-bit ARM, установочный exe-файл)
  • скачать с официального сайта (portable-версия для Windows 64-bit, exe-файл)

Wireshark — утилита для детального анализа сетевых пакетов локальных сетей в реальном времени, с возможностью отображения значения каждого поля протокола любого уровня. Работает с разными форматами входных данных, поддерживает различные сетевые протоколы (полное описание…)

Рекомендуем популярное

Advanced IP Scanner 2.5.4594.1

Advanced IP Scanner — Это быстрый, надежный и простой в использовании сканер локальных сетей (LAN) для…

Wireshark 4.4.0

Wireshark — утилита для детального анализа сетевых пакетов локальных сетей в реальном времени,…

LANScope 2.9.1

LANScope — бесплатная утилита, с помощью которой можно легко и быстро определить доступность…

Nmap 7.95

Nmap — Самый популярный сканер портов. Использовался в фильме «Матрица: Перезагрузка» при реальном взломе компьютера…

Serial Port Monitor 1.7

Программа-сниффер, которая позволяет отслеживать трафик COM-порта вашего ПК. Также…

MAC spoofer 2.1.0.9

Небольшая бесплатная утилита, которая предназначена для изменения MAC адреса сетевой…

Wireshark

1.2. System Requirements

What you’ll need to get Wireshark up and running …

  • The values below are the minimum requirements and only
    «rules of thumb» for use on a moderately used network

  • Working with a busy network can easily produce huge
    memory and disk space usage! For example: Capturing on a fully saturated
    100MBit/s Ethernet will produce ~ 750MBytes/min! Having a fast processor,
    lots of memory and disk space is a good idea in that case.

  • If Wireshark is running out of memory it crashes,
    see: http://wiki.wireshark.org/KnownBugs/OutOfMemory
    for details and workarounds

  • Wireshark won’t benefit much from Multiprocessor/Hyperthread
    systems as time consuming tasks like filtering packets are single threaded.
    No rule is without exception: during an «Update list of packets in real
    time» capture, capturing traffic runs in one process and dissecting and
    displaying packets runs in another process — which should benefit from two
    processors.

1.2.2. Microsoft Windows

  • Windows XP Home, XP Pro, XP Tablet PC, XP Media
    Center, Server 2003, Vista, 2008, 7, or 2008 R2

  • Any modern 32-bit x86 or 64-bit AMD64/x86-64 processor.

  • 128MB available RAM. Larger capture files require more RAM.

  • 75MB available disk space. Capture files require additional disk space.

  • 800*600 (1280*1024 or higher recommended) resolution with
    at least 65536 (16bit) colors (256 colors should work if Wireshark is
    installed with the «legacy GTK1» selection of the Wireshark 1.0.x releases)

  • A supported network card for capturing:

    • Ethernet: Any card supported by Windows should work. See the wiki
      pages on Ethernet
      capture and offloading
      for issues that may affect your environment.

    • 802.11: See the Wireshark
      wiki page. Capturing raw 802.11 information may be difficult without special equipment.

    • Other media: See http://wiki.wireshark.org/CaptureSetup/NetworkMedia

Remarks:

  • Many older Windows versions are no longer supported for three reasons:
    None of the developers use those systems which makes support
    difficult. The libraries Wireshark depends on (GTK, WinPcap, …) have
    dropped support for older releases. Microsoft has also dropped
    support for these systems.

  • Windows 95, 98 and ME are no longer supported. The «old technology»
    releases of Windows lack memory protection (specifically VirtualProtect)
    which we use to improve program safety and security. The last known
    version to work was Ethereal 0.10.14 (which includes WinPcap 3.1). You
    can get it from http://ethereal.com/download.html.
    According to this
    bug report, you may need to install Ethereal 0.10.0 on some
    systems.

    Microsoft retired support for Windows 98 and ME in 2006.

  • Windows NT 4.0 no longer works with Wireshark. The last known version
    to work was Wireshark 0.99.4 (which includes WinPcap 3.1). You still
    can get it from http://www.wireshark.org/download/win32/all-versions/wireshark-setup-0.99.4.exe.

    Microsoft retired support for Windows NT 4.0 in 2004.

  • Windows 2000 no longer works with Wireshark. The last known version
    to work was Wireshark 1.2.x (which includes WinPcap 4.1.2). You still
    can get it from http://www.wireshark.org/download/win32/all-versions/.

    Microsoft retired support for Windows 2000 in 2010.

  • Windows CE and the embedded versions of Windows are not currently supported.

  • Multiple monitor setups are supported but may behave a bit
    strangely.

1.2.3. Unix / Linux

Wireshark currently runs on most UNIX platforms.
The system requirements should be comparable to the Windows values
listed above.

Binary packages are available for at least the following platforms:

  • Apple Mac OS X

  • Debian GNU/Linux

  • FreeBSD

  • Gentoo Linux

  • HP-UX

  • Mandriva Linux

  • NetBSD

  • OpenPKG

  • Red Hat Enterprise/Fedora Linux

  • rPath Linux

  • Sun Solaris/i386

  • Sun Solaris/Sparc

  • Canonical Ubuntu

If a binary package is not available for your platform, you should
download the source and try to build it.
Please report your experiences
to wireshark-dev[AT]wireshark.org
.

  • Windows
  • Utilities
  • System Utilities
  • Wireshark (32bit)
  • Old Versions

Wireshark (32bit) 3.6.8

Sep 8, 202258.28 MB

Download

Wireshark (32bit) 3.6.7

Jul 29, 202258.28 MB

Download

Wireshark (32bit) 3.6.6

Jun 16, 202258.23 MB

Download

Wireshark (32bit) 3.6.5

May 5, 202258.47 MB

Download

Wireshark (32bit) 3.6.3

Mar 24, 202258.49 MB

Download

Wireshark (32bit) 3.6.2

Feb 13, 202258.48 MB

Download

Wireshark (32bit) 3.6.1

Dec 30, 202158.45 MB

Download

Wireshark (32bit) 3.6.0

Nov 24, 202158.34 MB

Download

Wireshark (32bit) 3.4.10

Nov 18, 202152.86 MB

Download

Wireshark (32bit) 3.4.9

Oct 7, 202152.84 MB

Download

Glary Utilites

Make Your Computer Faster

  • Totally Free
  • No Bundle,No Ads, No Virus

Download Now

Понравилась статья? Поделить с друзьями:
0 0 голоса
Рейтинг статьи
Подписаться
Уведомить о
guest

0 комментариев
Старые
Новые Популярные
Межтекстовые Отзывы
Посмотреть все комментарии
  • Активация режима разработчика windows 10
  • Как подключить телефон к компьютеру через usb для передачи интернета с телефона на компьютер windows
  • Как изменить путь ярлыка в windows 10
  • Как быстро открыть командную строку в windows 10
  • Vlc картинка в картинке windows