<div>
Hi,<br />
<br />
You can use Wireshark.<br />
<br />
<a href="http://www.wireshark.org" rel="ugc">www.wireshark.org</a><br />
<br />
Incase you are new to wireshark;<br />
<br />
wiki.wireshark.org
</div>


Hi,

You can use Wireshark.

www.wireshark.org [http://www.wireshark.org]

Incase you are new to wireshark;

wiki.wireshark.org

<div>
<div class="content wysiwyg-content">
Hello,<br />
<br />
I have a custom windows service running on a Windows Server 2008 x64. For some reason, 3 out of 10 users are dropping the connection to this server. Before looking into the service, I want to know if the port and connection can handle these amount of users. I want to be able to test the port to see if it can handle connections. How do I go by doing so?<br />
I tried using &quot;Process and Port Analyzer&quot; but it only shows me the traffic and not if a packet has been dropped.<br />
<br />
Are therer any tools aout there that will show me this? How many connections can a standard TCP Port (example: 9000) take?<br />
<br />
Thanks!
</div>
</div>


Hello,

I have a custom windows service running on a Windows Server 2008 x64. For some reason, 3 out of 10 users are dropping the connection to this server. Before looking into the service, I want to know if the port and connection can handle these amount of users. I want to be able to test the port to see if it can handle connections. How do I go by doing so?
I tried using "Process and Port Analyzer" but it only shows me the traffic and not if a packet has been dropped.

Are therer any tools aout there that will show me this? How many connections can a standard TCP Port (example: 9000) take?

Thanks!

How do I test a port for dropped packets?

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

Networking software modules are interfaced with a framework implemented on the machine's operating system that implements the networking functionality of the operating system. The best known frameworks are the TCP/IP model and the OSI model. Systems typically do not use a single protocol to handle a transmission. Instead they use a set of cooperating protocols, sometimes called a protocol family or protocol suite.[9] Some of the best known protocol suites include: IPX/SPX, X.25, AX.25, AppleTalk and TCP/IP. Other protocols indirectly related to networking include the hypertext transfer protocol (HTTP) and its related technologies, Dynamic Host Configuration Protocol (DHCP), Domain Name Server (DNS) and other Internet protocols.

Networking Protocols

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.