Marco Moock <
mo...@posteo.de> schrieb:
>Die FB hat damit nichts zu tun.
>Port unreachable kommt normalerweise bei UDP-Verbindungen.
>Schaue bitte, auf welchen Port (und ob TCP/UDP) das geht und was genau
>als Antwort kommt.
Vom PC zum Fantec:
Frame 82: 66 bytes on wire (528 bits), 66 bytes captured (528 bits) on
interface \Device\NPF_{785B3E25-AAA4-42D9-8063-DBC21ABFDB84}, id 0
Ethernet II, Src: Giga-Byt_d6:c3:48 (90:2b:34:d6:c3:48), Dst:
00:ce:39:b9:90:18 (00:ce:39:b9:90:18)
Internet Protocol Version 4, Src: 192.168.178.23, Dst: 192.168.178.31
Transmission Control Protocol, Src Port: 55010, Dst Port: 111, Seq: 0,
Len: 0
Source Port: 55010
Destination Port: 111
[Stream index: 3]
[Conversation completeness: Incomplete (37)]
[TCP Segment Len: 0]
Sequence Number: 0 (relative sequence number)
Sequence Number (raw): 1156512994
[Next Sequence Number: 1 (relative sequence number)]
Acknowledgment Number: 0
Acknowledgment number (raw): 0
1000 .... = Header Length: 32 bytes (8)
Flags: 0x002 (SYN)
Window: 64240
[Calculated window size: 64240]
Checksum: 0xe5ae [unverified]
[Checksum Status: Unverified]
Urgent Pointer: 0
Options: (12 bytes), Maximum segment size, No-Operation (NOP),
Window scale, No-Operation (NOP), No-Operation (NOP), SACK permitted
[Timestamps]
[SEQ/ACK analysis]
Und vom Fantec zum PC:
Frame 80: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on
interface \Device\NPF_{785B3E25-AAA4-42D9-8063-DBC21ABFDB84}, id 0
Ethernet II, Src: 00:ce:39:b9:90:18 (00:ce:39:b9:90:18), Dst:
Giga-Byt_d6:c3:48 (90:2b:34:d6:c3:48)
Internet Protocol Version 4, Src: 192.168.178.31, Dst: 192.168.178.23
Transmission Control Protocol, Src Port: 111, Dst Port: 55010, Seq: 1,
Ack: 1, Len: 0
Source Port: 111
Destination Port: 55010
[Stream index: 3]
[Conversation completeness: Incomplete (37)]
[TCP Segment Len: 0]
Sequence Number: 1 (relative sequence number)
Sequence Number (raw): 0
[Next Sequence Number: 1 (relative sequence number)]
Acknowledgment Number: 1 (relative ack number)
Acknowledgment number (raw): 1156512995
0101 .... = Header Length: 20 bytes (5)
Flags: 0x014 (RST, ACK)
Window: 0
[Calculated window size: 0]
[Window size scaling factor: -1 (unknown)]
Checksum: 0xb124 [unverified]
[Checksum Status: Unverified]
Urgent Pointer: 0
[Timestamps]
[SEQ/ACK analysis]
Die Sache ist: Ich hatte diese Konfiguration schonmal genau so, mit
diesem Netzwerk, diesem BS (Win10), und da erschien der Fantec unter
'Netzwerk'. Oder ich konnte das Erscheinen erzwingen, indem ich in der
Suchleiste des Explorers \\FANTEC eingab.
Das funktioniert jetzt nicht.