Port nicht erzeugt

[Kas Ob.]

Zitat von TurboMagic:

Angefügt habe ich zwei Screenshots. Diese zeigen alle bind Aufrufe, weil die nach
meinem Wissenstand die relevanten sind. Richtig?

bind is relevant of course, but i don't see successful or failed listen !
https://learn.microsoft.com/en-us/wi...insock2-listen

Zitat von TurboMagic:

Nur was bedeutet das für mich?

There is something bugging me in the second screenshot shot, you can see the bind call internally calling ntohs and return 82, while you mentioned port 1025 (which is showing in the first screenshot), is that a simple test, or there is something is missing here.

As i don't have your library of DataSnap to compare with working one, you should repeat the same API usage report between the failed one and successful, and see if there is something.
From what i see all the functions in both screenshots were OK, yet both do show that the opening port process was repeated, hinting there was a failure somewhere, yet there is no failed API per see !!

If i am to guess, your bug is completely have nothing to do with socket handling, it could be firewall or may be an event in a DataSnap class, in all cases you should have received an event or some error for that socket like an event triggered, (the one with success bind which is all of them, they all did bind yet repeated it on the same port), i don't see closesocket being called, try to catch the moment when your application decided to reopen the port, use logging for the relevant events.

[TurboMagic]

Hallo,

bevor ich anfange in meinem Anwendungsquellcode weiter nach dem Fehler zu suchen hier
noch ein Log Auszug mit dem Listen Aufruf. Sieht für mich erstmal ok aus. Rückgabewert
ist 0.

Oder sieht da jemand was verdächtiges?

[Kas Ob.]

Zitat von TurboMagic:

Hallo,

bevor ich anfange in meinem Anwendungsquellcode weiter nach dem Fehler zu suchen hier
noch ein Log Auszug mit dem Listen Aufruf. Sieht für mich erstmal ok aus. Rückgabewert
ist 0.

Oder sieht da jemand was verdächtiges?

Listen is success here in the screenshot, hence in TCPView listening status for the port should be visible just like netstat.exe, if there are not visible as open ports and listening then something is broken in the network interface, like there is broken virtual adapter for faulty VPN software.
Once the port have a listening status, firewalls will not close or hide it, they will just intercept the traffic and block them, traffic here does include the SYN for establishing the connection, in other words there should be listening ports.

Check the existed network adapters.

[TurboMagic]

Hallo,

ich komme jetzt endlich wieder zu weiteren Tests.
Ich habe in meinen DataSnap/Webbroker Code weitere Logmeldungen eingebaut und
mal beide Teile die einen Socket erzeugen können sollen getestet:

a) das Rest API um welches es eigentlich geht. Es erzeugt auch auf meinem PC
den eingestellten Port nicht, auch nicht wenn man einstellt, dass der ohne HTTPS
erzeugt werden soll.

b) eine einfache Statuswebseite, in keinem Fall auf Port 80.

Der Port 80 aus b) wird in meinem Fall erzeugt, der Port aus a) nie, sagt jedenfalls
netstat -p TCP auf einer Admin Konsole.
Nur komme ich auf Port 80 nicht mit dem Webbrowser drauf, egal ob ich HTTPS an oder aus habe.

Die Anwendung ist mit 10.3.3 erstellt und der Teil hatte schon mal funktioniert.
Als OpenSSL DLLs sind die libeay32.dll und ssleay32.dll im ANwendungsverzeichnis.
Beide in V1.0.2j. Ja, das sind nicht mehr die neuesten, sollten aber doch TLS 1.2 unterstützen.

Mir gehen gerade die Ideen aus.

Hier mal der zum Starten benutzte Code:

Delphi-Quellcode:

  if FMyServiceEnabled and (not FRESTServer.Active) then
  begin
    FRESTServer.Bindings.Clear;
    FRESTServer.DefaultPort := FMyServicePort;
    FRESTServer.Active      := True;

    log.Send(LevelBlue, cCategory, 'REST Server gestartet. Port: ' + FMyServicePort.ToString);
  end;

  if FStatusWebsite and (not FWebServer.Active) then
  begin
    FWebServer.Bindings.Clear;
    FWebServer.DefaultPort  := FStatusPort;
    FWebServer.Active       := True;

    log.Send(LevelBlue, cCategory, 'Web Server gestartet. Port: ' + FStatusPort.ToString);
  end;

FRestServer und FWebServer sind jeweils: TIdHTTPWebBrokerBridge

[TurboMagic]

Ok, nochmal einen Test mit der Statuswebseite ohne aktiviertes HTTPS gemacht: die fragt jetzt zumindest
mal nach Benutzername und Passwort. Das ist mehr als vorher.

Nur der andere Endpunkt mit dem anderen Port taucht nie auf.

Ergänzung: im nächsten Test taucht auch der Port 80 wieder nicht mehr auf.
Das ist ein Lottospiel. Aber warum?

[TurboMagic]

Hallo,

weitere Infos:
war eben auf dem PC beim Anwender und konnte auch ipconfig /all ausführen.

Das zeigt:

1x WiFi (unverbunden)
1x LAN (unverbunden, Microsoft Wi-Fi Direct Virtual Adapter)
1x LAN (unverbunden, Microsoft Wi-Fi Direct Virtual Adapter #2)
1x LAN (Realtek, verbunden, IPv6 und IPv4, IPv4IP: 192.168.2.24 mit 255.255.255.0 Subnetzmaske, DHCP an)
1x VMware Virtual Ethernet Adapter for VMnet1 (IPv4 IP: 192.168.64.1)
1x VMware Virtual Ethernet Adapter for VMnet8 (IPv4 IP: 192.168.179.1)

Oder auch anders gefragt: wo bekomme ich detailliertere Infos zur DataSnap Fehlersuche?

[Kas Ob.]

Well, i was not going to comment on this but ...

You have Api Monitor and you recorded a report, but you missed few details so i will try again to explain few things, and expand on your last post:

1) Bind : it does what say, it does bind a socket to a port, (local port) and prepare the socket for listening, bind is not essential for Listen to success, and calling listen without it will work except it will be on an arbitrary port, so bind allow you to specify the port to listen for, hence it plays a role in detecting if the port is busy, and by busy i don't mean it is in listening state but, it means port is already bound to a socket and can't be used for this socket, hence listen should not be called or will pick an arbitrary port.
2) Listen is the actual ... well listening, as a term it is means opening the port for incoming connections in case of TCP.
3) if Listen is success as you showed in API monitor log then and to my knowledge NetStat and TCP View should show the port in listening state, there is no Firewall that will prevent this as it will break any application, FireWalls will allow the listening port but will not allow any packet or event on it in blocking mode, so again if Listen is success then TCP View should report a listening port.
4) What can be a reason for Listen to succeed but there is no opened (listening state) socket, i can think of two cases
A) The socket had been closed !!!, aka in that report there should be CloseSocket, you didn't mention if that happen, so please try to check what operation did happen on these socket handles after Listen.
B) From you last post, you listed few Network interfaces and this raise a completely different questions, for that i will go back for bind and expand on it, Bind will not select the IP it will only assign port for an already created Socket, that created socket already had an IP !!, this is very important form here, that IP address will decide where the listening state will happen, i mean on which network interface, when that IP belongs to an IP provided by an interface then Listen will be applied and valid for incoming connections for that IP only on that network interface, many network interface are virtual ones, means they are not even real and emulated by a driver, to listen to all network interfaces you should assign the zero IP address for that socket "0.0.0.0", other wise listen will be limited, so..

Suggestion:
How about you check (A) for CloseSocket if being called, also check what are you listening to, i don't mean the port but the IP, the local one that will define and scope the IP range, some virtual interfaces are protected and here i don't mean protected by firewall, because they can be hidden form the firewall to begin with, in that case they can be protected/hidden TCPView ... this case i can imagine might happen when such interface is configured to allow communication between virtual guests excluding the host, like some security feature or something similar.

ps: what i discussed above apply for IPv4, there is small differences in handling for IPv6, in IPv6 there is no subnet masks provided by interfaces, the masks functionality are already with in the IP and its provider over the wire (or the virtual one) and how the network interface configured, this for privacy and simplification standardized for IPv6.