So far, I used the LAN plugin (v3.09) to connect to my Windows 10 machine and upload data there, and it worked fine. Yesterday I switched routers (Telekom Speedport W724V Type B to AVM FritzBox 7590), and the first test also worked; however, today I couldn't connect any longer. The error message in the UI is truncated, the full message is in the log file: (IPv6 prefixes have been anonymized)
LAN:SMB2 CONNECT:failed to connect to blacky.fritz.box/2003:e7:272x:xxxx:1841:41e0:99eb:61dd (port 445) from /2003:e7:272x:xxxx:251b:3052:349c:4c6e (port 41289) after 5000ms: isConnected failed: EHOSTUNREACH (No route to host)
Some parts of the message make sense, others don't: The "from" address is in fact my mobile's IPv6 address, and the IPv6 address it tries to connect to actually doesn't exist, so the "Host Unreachable" error is understandable. What I don't get though is
- Where does it get that invalid address from?
- Why does it try to use IPv6 anyway? The share I connect to is configured as "192.168.1.26/TheShareName", i.e. an explicit IPv4 address, not even a hostname.
- Why does it reverse-lookup the IP? blacky.fritz.box is, in fact, the correct hostname for the machine, but I never asked the client to use it.
- Why does all of this happen only after the switch to a different router? (And why didn't it happen for the first try with said router?) Is it just coincidence?
Any ideas? ;) It still works with SMBv1, but I'd rather use SMBv2 like before ...