![]() ![]() This is probably insecure, because the originating port can be spoofed, but let's not be paranoid. The port 138 is probably not necessary, as I have only seen packets arriving from 137, but you never know. This will allow UDP packets to arrive into any local port as long as they are originating from port 137 or 138 of the remote computer. To solve this problem, execute the following command: sudo ufw allow in proto udp from any port 137,138 to any The rules that allow Samba to act as a server are not sufficient to also allow Samba to act as a client, because the remote machines respond from their own port 137, but the local port on which these responses arrive is not 137, it is some random port. They may respond with an error, in which case you have other problems, but if they don't respond at all, then their packets are usually being eaten up by a firewall. ![]() Machines do generally respond to requests. But when you try to mount a remote share, that's what you are doing: in this scenario your machine is a client, and the remote machine is a server.Īlso, the "no reply" error is a hint that some firewall is messing things up. It will not add any rules for Samba acting as a client. This process shouldn't be difficult and, in the end, you'll have a reliable printer server. Will only add rules for Samba acting as a server. I'm going to walk you through setting up a print server on Ubuntu Server 18.04, using CUPS and Avahi. The problem (at least in Ubuntu 18.04 where I tried it) is that the following command: sudo ufw allow Samba ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |