Alright....

I have a Windows 10 laptop and a Linux Mint desktop.

On the dektop is a web site and an FTP server that I am accessing via 192.168.0.183 sort of thing.

I seem to be able to xfer files via Filezilla on my laptop a few times or even a couple of dozen times.

But eventually Filezilla will fail and can no longer connect to the FTP server at 192.168.0.183

When that happens I can no longer access the web site at 192.168.0.183

But strangely I can always access the web site via 110.147.129.231:8080
Or at least so far Filezilla locking up the server on my Linux desktop as not also locked up access to my web site via 110.147.129.231:8080. It always locks up access to my web site via 192.168.0.183 though.

Also I am not able to see my Linux desktop in Windows network on my laptop, despite installing Samb on my Linux desktop. Am I missing something about other things I need to do on my window laptop to make it work?

Welcome to LinuxQuestions.

Originally network discovery was built into SMB version 1 but that has been removed in both linux and Windows. Windows has Web Service Discovery to find other Windows shares but it isn't built into samba. However, linux has its own WSD implementation called wsdd which should be available from Mint's software center. You can still connect manually to the Mint samba share by entering into the Windows file browser \\Mint hostname or IP address\share_name. Be sure to create a samba password for the user.

Are you using sftp or ftp as the connection protocol. Just a wild guess but if FileZilla is not disconnecting correctly you might be creating to many concurrent connections which exceeds the limit of the server.

I set filezilla to only have one active connection at a time and it seeme to be working.
And the trick with samba in windows was \\192.168.0.183/sambashare