Can only send files one way

[jll123567]

HI, I can't seem to send files to one computer but can send to the other.
I can select the file and receiver but then LAN-Share just says "waiting" forever.

I have

• Restarted the program on both computers. No effect.
• Tried changing the transfer port. No effect.
• Made firewall exceptions on both computers. No effect

For reference, both machines are Windows 10 64bit

.

[jll123567]

Here's what I see.

[jwarrenbc]

I'm having the same problem sending from Linux to Windows 10. The Windows 10 instance is binding to the wrong IP address: 169.254.179.189, when its actual IP address on the LAN is 192.168.1.5. I believe that my DHCP server is working correctly, so I don't know where it's getting the 169 address from?

[timbrockley]

I also have issues - can send from Windows 10 (64 bit) to Linux but not the other way.

Binds to wrong IP address on windows.

[rwperrott]

I've seen LAN-Share on Windows 10 (64 bit) not see an active LAN-Share on a Mint Debian VM. The Debian side appear to be bound to an IP6 socket, but not IP4 socket, which may be the problem.

[IRebri]

Is there any solution to this problem?

I'm having the same problem sending from Ubuntu to Windows 10.

I'm having the same problem sending from Linux to Windows 10. The Windows 10 instance is binding to the wrong IP address: 169.254.179.189, when its actual IP address on the LAN is 192.168.1.5. I believe that my DHCP server is working correctly, so I don't know where it's getting the 169 address from?

In my case Win10 has 192.168.0.190 however the Win10 instance is binding to 169.254.100.206

[rwperrott]

Is there any solution to this problem?

I'm having the same problem sending from Ubuntu to Windows 10.

I'm having the same problem sending from Linux to Windows 10. The Windows 10 instance is binding to the wrong IP address: 169.254.179.189, when its actual IP address on the LAN is 192.168.1.5. I believe that my DHCP server is working correctly, so I don't know where it's getting the 169 address from?

In my case Win10 has 192.168.0.190 however the Win10 instance is binding to 169.254.100.206

The solution is for the abdularis account holder, or a fork account holder, to add optional configuration of the IP address of the listening socket, not just its port number. Some systems have and use multiple NICs, including virtual ones, so it is stupid to always assume the listening port IP address and may be a security risk too. A text format IP address could be use to specify one or more IP4 and/or IP6 server sockets.

This naïve fail has gone on so long now that I had to setup and use a minimal FTP server to share some context from my Mint Debian VM, and I may decide to ignore this project if this drags on much longer.

[atiyabzafar]

I installed LAN share to transfer some files form my ubuntu setup to my windows laptop. But I can don only the reverse of it. Why is this issue so old and haven't been rectified. The listening IP for windows I believe is not correct. But i may be wrong.

[syJSdev]

+1
Any updates?