PacketSender icon indicating copy to clipboard operation
PacketSender copied to clipboard

Published 20 hours ago • verified publisher icon dannagle

[BUG] Bind Error: The server can't bind 0Connection to proxy refused

Open SSar2024 opened this issue 1 year ago • 4 comments
trafficstars

What OS and Version?

Latest Windows 10 22H2 x64 with all updates. Network interfaces: 192.168.x.x - local network ip4 only 10.x.x.x - OpenVPN currently offline PacketSender 8.8.2

Description of issue

Recently, when launching the utility, a binding error has been consistently occurring both with and without administrator rights. After clicking OK, another error is displayed: "Packet Sender attempted (and failed) to bind to port 0. Are you running multiple instances? Trying to build to custom IP?" After pressing OK again and after a long wait, the application starts, but it is impossible to send either TCP or UDP packets to the server IP, they are on its DNS name.

  1. I do NOT run multiple instances.
  2. I don’t use any proxies, and I don’t even see any settings for them in the application.
  3. I tried to disable TCP and UDP servers in the application settings, and also tried to specify a port greater than 1024 in the application settings - no effect.
  4. I tried to specify in the settings an explicit IP4 address in my local network - also no effect.
  5. It seems that the application simply ignores the settings that I specify and still tries to bind to port zero. Or it takes the settings from somewhere else despite the fact that I tried to completely remove the application from my PC and cleared all files and records about it before reinstalling.
  6. Every time I try to send a packet (tcp or udp) to the server, the application freezes for 3-4 seconds, and then nothing happens and no entry is even added to the log.
  7. And finally, when closing the application, a standard Windows error appears stating that an error has occurred in the application and it will be closed.
  8. I tried to download the windows x64 installer and the portable version, but for some reason the installer wanted to be installed in the Program Files (x86) folder, but in the end there was no difference, the errors were the same.
  9. I only use the standard antivirus and firewall Microsoft Defender.

PS I used your great app for debugging my servers for many years, but now it is no longer possible.

SSar2024 avatar Oct 25 '24 06:10 SSar2024

Previous releases are available at https://github.com/dannagle/PacketSender/releases if this one is causing problems.

May I see a screenshot of the settings you are using?

dannagle avatar Oct 25 '24 11:10 dannagle

No problem, here's a screenshot, but as I wrote earlier, I did a clean reinstallation more than once. image There are suspicions that in addition to problems within the application, something may have changed in the operating system after the latest official (not beta) updates from Microsoft. Can you simulate the situation on Windows 10 22H2 x64 ?

ghost avatar Oct 25 '24 13:10 ghost

  • I found a possible cause for it trying to install into x86 directory. That is fixed in the development branch.
  • DTLS is a brand new feature in this release. Maybe the workflow of that is causing you problems.

A patch release is already planned next week for a different problem related to loading certificates with DTLS. Would you mind helping to test a portable release candidate when that fix is finished? Maybe I am missing a step in my own testing.

If you are willing to test a portable of the next version: [email protected]

dannagle avatar Oct 25 '24 13:10 dannagle

If you are willing to test a portable of the next version: [email protected]

Yes, of course, I will help test. Not only is it a very necessary and useful tool, but I am always for helping a fellow developer.

  • email sent.

ghost avatar Oct 25 '24 19:10 ghost