Wiresharl not able to communicate on a remote NpCap
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 592
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I have setup this morning NpCap on one win 2019 64 server which has an IP in the same network as my laptop. I fire wireshark and try to add an interface, I underatnd from a couple of blogs that I should enter the IP of the remote server and port 2002.
Is it the right port 2002 that NpCap uses?
I opened port 2002 on the firewall on the remote server also. when I run DiagReport.bat, it shows all details correctly except the port on which it is listening on. The strange thing is when I run
netstat -an
I don't see the port 2002 in the list
Thanks for your help
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported DiagReport.bat output and the results of netstat -an on the Windows Server 2019 host. Check the Npcap remote-capture entry points and configuration related to port 2002, then establish whether the service should listen there and what evidence confirms the issue is resolved.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100