Raees Khan
2020-Apr-06 20:09 UTC
[Samba] How to force Winbind to use port 445 to talk to Windows Active Directory
We have Samba4 installed on CentOS 7.3 and it is integrated with Windows AD for user authentication. Everything is working fine, but we see a lot of Firewall denies on port 139. Upon investigation, I found that Winbindd on my Linux machine is trying to connect to AD on port 139. I ran winbind -i -d 3 and noticed that Winbind tries connecting to Windows AD on port 445 as well port 139. I would like to prevent Winbind from using port 139 to connect to DC. I have added 'disable netbios = Yes' in the Global section of my smb.conf but it did not help. Any help will be greatly appreaciated. Thanks,
miguel medalha
2020-Apr-06 22:55 UTC
[Samba] How to force Winbind to use port 445 to talk to Windows Active Directory
In the [global] section of smb.conf try: smb ports = 445 The default is: smb ports = smb ports = 445 139
Raees Khan
2020-Apr-07 21:24 UTC
[Samba] How to force Winbind to use port 445 to talk to Windows Active Directory
I will but changing that would block samba from listening for connections on port 139. However, in my case I don't see any incoming traffic on port 139 rather the winbind daemon on my samba server tries to connect to the Active Directory Domain Controller on port 139. On Monday, April 6, 2020, 03:55:56 PM PDT, miguel medalha via samba <samba at lists.samba.org> wrote: In the [global] section of smb.conf try: smb ports = 445 The default is: smb ports = smb ports = 445 139 -- To unsubscribe from this list go to the following URL and read the instructions:? https://lists.samba.org/mailman/options/samba
Seemingly Similar Threads
- How to force Winbind to use port 445 to talk to Windows Active Directory
- How to force Winbind to use port 445 to talk to Windows Active Directory
- winbind : suspend nightmare
- wbinfo -u Don't show users from trusted(ing) domain on domain member server
- Unable to join domain when DC firewall is active