Hello. I have a situation where I need to communicate with an NT server that is behind a firewall, the admins of which will not allow port 445 traffic to pass through. With the setup I have, smbmount and smbclient literally take minutes to issue back a response from said server unless I issue '-p 139', in which case I get a response almost instantly. My larger issue is getting winbind to use 139 instead of 445. I can not enumerate the groups and users from that server. I even had the samba/winbind system become a member of that domain but the only groups that will enumerate are those of the two other trusted domains. Is there a way to make winbind use only 139? I have looked at debugging and what not and everything is hanging w/ communications to 445. I have added samba ports = 139 to my smb.conf but that has not done anything, although I did not expect it to, as I believe it is for communications from others to itself? Thanks all. ~T --- No one makes statues honoring critics.
Quoting T'Krin <tkrin@tkrin.net>:> Hello. I have a situation where I need to communicate with an NT server that > is > behind a firewall, the admins of which will not allow port 445 traffic to > pass > through. With the setup I have, smbmount and smbclient literally take > minutes > to issue back a response from said server unless I issue '-p 139', in which > case > I get a response almost instantly. My larger issue is getting winbind to > use > 139 instead of 445. I can not enumerate the groups and users from that > server. > I even had the samba/winbind system become a member of that domain but the > only > groups that will enumerate are those of the two other trusted domains. > > Is there a way to make winbind use only 139? I have looked at debugging and > what not and everything is hanging w/ communications to 445. I have added > > samba ports = 139 > > to my smb.conf but that has not done anything, although I did not expect it > to, > as I believe it is for communications from others to itself? > > Thanks all. > > ~TSorry. Forgot to give details of my system. It is Mandrake 9.1 and Samba 3.0 compiled from SRPMS. My smb.conf and testparm output are below. Is it even possible to force winbind to only attempt connections w/ other systems via port 139 rather than 445? ### WINS and WORKGROUP lines were changed ### ### Start smb.conf ###[global] workgroup = workgroup netbios name = server server string = Samba Server %v smb ports = 139 log file = /var/log/samba/log.%m max log size = 50 log level = 3 security = domain password server = * encrypt passwords = yes smb passwd file = /etc/samba/smbpasswd winbind uid = 10000-20000 winbind gid = 10000-20000 # winbind separator = + winbind use default domain = yes socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 wins server = 123.123.123.123 [public] path = /home/samba read only = no create mask = 0777 directory mask = 0777 browseable = yes writable = yes ### End smb.conf ### ### Start testparm output ### Load smb config files from /etc/samba/smb.conf Processing section "[public]" Loaded services file OK. Server role: ROLE_DOMAIN_MEMBER Press enter to see a dump of your service definitions # Global parameters [global] workgroup = workgroup server string = Samba Server %v security = DOMAIN log level = 3 log file = /var/log/samba/log.%m max log size = 50 smb ports = 139 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 wins server = 123.123.123.123 idmap uid = 10000-20000 idmap gid = 10000-20000 winbind use default domain = Yes [public] path = /home/samba read only = No create mask = 0777 directory mask = 0777 ### End testparm output ###
Possibly Parallel Threads
- Samba 3.0 PDC and Group Listing on Samba Winbind Box
- Winbind+nss working on one centOS 5.2 box but not another
- wbinfo -i returns the same id for all users, authentication doesn't seem to go through winbind at all
- what's on port 139
- The unbelivable Civilizations of the World