dannagle / PacketSender

Network utility for sending / receiving TCP, UDP, SSL, HTTP

Home Page:https://packetsender.com

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Cannot Connect TCPIP

gkcabc opened this issue · comments

What OS?

  • Windows
  • Mac
  • Linux (Which distro?)
  • iOS (phone or ipad?)
  • Android (phone or tablet?)

Description of issue

Can connect using localhost or 127.0.0.1.
Cannot connect using LAN IP address (or hostname) (192.168.0.109) of PC.
Cannot connect to other devices on same LAN
Can connect using LAN IP with telnet. with everything.
Tried binding to 192.168.0.109, but no connect

Do the pre-bundled packets work?

I used the windows installer version. UDP works fine.

How about the TCP bundled packets?

image

Bind to the IP you want in the Settings. Make sure Packet Sender says that IP exists in the title bar.
image

When you hit OK, it should show the bound IP in the bottom right.

image

I don't see a screenshot. Did you paste one into the github thread?

Sorry, I attached it to the mail, here it is.
bind

At a glance, these settings look OK. In fact, you shouldn't need to IP-bind. Try setting back to "IPv4 Only" since Cygwin probably isn't doing an IP-bind and is working OK.

What has me concerned is the "From Port". Something bizarre is happening underneath. 8368847 does not look right. Could you have a firewall blocking private connections to Packet Sender (but is allowing Cygwin to pass)? Your firewall could be allowing Packet Sender public connections (to get to an internet telnet server) but not private.

Well, if I use a hostname (test), inserting into the hosts file "test 192.168.110.10", it works correctly (with no bind address).

Very strange.

Thanks

Gordon

That is very strange. I can't even think of a good theory. I'm going to leave this ticket open for a while in case I do think of something.

I don't think its anything to do with your code, I debugged it and there is no problem, calls QSslSocket.connectToHost correctly.

Looked at Windows Event logs, but nothing of interest.

Tried using the same configuration (192.168.100.10) on a Windows 7 machine with no problem.

Also tried using a Windows 7 VM on my Windows 10 machine with no problem

I conclude there is some problem with my Windows 10 machine

For me you can close.