similar to: Forcing Samba & Winbind to use port 139

Hello there all. I setup a Samba 3.0 PDC using smbpasswd for authentication on a Mandrake 9.1 system. (I will be looking at LDAP later.) I have also setup another linux box to use winbind and get user and group listings from the Samba PDC. My problem is that no groups from the PDC get listed on the winbind box. I assume it has something to do with how groups are created and managed on a MS

Hi all, I have an odd situation on my hands: * Two CentOS 5.2 boxes both joined to an AD domain. * Same samba version (3.0.28-1.el5_2.1) smb.conf, only the netbios names differ * Can enumerate users and groups using winbind -{u,g} on both. * nss doesn't enumerate users & groups on one (same lib versions, same conf file). //bentis@testukmcsstor1//:~$ rpm -qa | grep nss-

On Sat, 18 Feb 2017 13:50:52 +0100 Emmanuel Florac via samba <samba at lists.samba.org> wrote: > Le Sat, 18 Feb 2017 13:20:52 +0100 > Emmanuel Florac via samba <samba at lists.samba.org> écrivait: > > > I've added > > idmap config * : backend = tdb > idmap config * : range = 10000-30000 > > to smb.conf, and now 'wbinfo -i

Having trouble with Samba. The config file passes the test (testparm) The Server seems to be upa and running fine (smbclient -L localhost) But can't seem to connect to it from other computers (running 2000 or 98) They were able to connect once though. What should be listed on port 139 in services. We have : netbios-ssn Does this sound right? Appreciate any help/suggestions!! Regards, Andrew

The unbelivable Civilizations of the World<http://mega-structures.blogspot.com/2007/03/unbelivable-civilizations-of-world.html> The unbelivable Civilizations of the World <http://mega-structures.blogspot.com/> <http://mega-structures.blogspot.com/> ''Chaco Canyon Indian ruins, NM, circa 1060, The Center of ...<http://mega-structures.blogspot.com/>

I installed Samba 2.0.0 on a P100 running SlackWare Linux 96 (Kernel 2.0.0). After running configure, make, make install, and testparm, I thought I was all ready to start up the smbd daemon. So I typed in smbd -D -d 50 Got back a failure listing in the error log. [1999/02/01 16:27:06, 0] lib/util_sock.c:open_socket_in(663 Brian Lee Bowers | Division of Government Research Computer Aide I

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

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

I can't figure out what is causing the error message of [1999/10/13 11:39:42, 0] lib/util_sock.c:open_socket_in(671) bind failed on port 139 socket_addr=0.0.0.0 (Address already in use) in my logs and thus preventing smbd from serving up connections. How can I track down what is causing this? Samba has been working great and now I must have done something but I don't know what. The

I did a clean install of Redhat 7.3 on a system. The install included samba, samba-client, samba-common. I moved the saved versions of smb.conf, smbusers and swbpasswd to /etc/samba. Then I started up smb by issuing "/etc/init.d/smb start" I have set smb to start upon reboot of the system. I have rebooted the system several times. smbd and nmbd start up, but clients cannot

Hey all. Has anyone been able to successfully install CentOS 4 in Virtual PC on the Mac? I have tried numerous times in both gui and text install mode w/ and w/o package customization and minimum and everything install. The install dies just when packages are beginning to be installed or very shortly thereafter. I don't get a full screen of errors to share as they pass by the screen too

Hello, I am running Red Hat 7.3 Samba 2.26 and winbind. I have been able to join the domain and test all of the following with these commands. All works great. winbind -u winbind -g getent passwd getent group But when I set up a share to test with one domain user account it just presents me with a password dialog box and does not accept anything. It should not prompt me but if it does

I've got a Debian/Jessie Samba 4.2.14 running as an AD member. ADC is a Windows2008R2 server. Join worked without problem. # net ads testjoin Join is OK wbinfo -u and wbinfo -g work perfectly and provides a list of users and groups from the AD as expected. wbinfo -i <user> works too: # wbinfo -i TESTAD\\testuser

Emmanuel Florac via samba wrote: > Unknown parameter encountered: "winbind enumerate users" > Ignoring unknown parameter "winbind enumerate users" > Unknown parameter encountered: "winbind enumerate groups" > Ignoring unknown parameter "winbind enumerate groups" It may be irrelevant, but I have: winbind enum groups = Yes winbind enum users

Hi, There are some generated Sparc assembly code like this: main: ! @main ! BB#0: save %sp, -112, %sp sethi 0, %l0 or %g0, 5, %l1 st %l0, [%fp+-4] st %l1, [%fp+-8] st %l1, [%fp+-12] sethi %hi(.L.str), %l1 ld [%fp+-8], %o1 add %l1, %lo(.L.str), %l1 or %g0, %l1, %o0 call printf nop ld [%fp+-12], %o2 ld [%fp+-8], %l2 sethi %hi(.L.strQ521), %l3 add

Hi Rowland, Thanks AGAIN for your answer. I followed what you advise me to do... If you tell me something and I didn't change it, I forget it. I give you more infos this time: Please look at my full smb.conf https://pastebin.com/WR2CY9SW Now, please check my testparm result https://pastebin.com/2jMDtWs2 Can you explain that sir ? Thanks in advance. Peace! ;) Sébastien ;) -----Message

I have an annoying problem I'm hoping to get some guidance on. I am able to use winbind with our local domain, however it does not work with a remote trusted domain (it works fine for a local trusted domain). >From the looks of things, winbind requires port 445 or 139 to be open to the remote domain controllers, which it is not. Apparently these ports are not required for the MS Windows

The unbelivable Civilizations of the World <http://mega-structures.blogspot.com/> <http://mega-structures.blogspot.com/> ''Chaco Canyon Indian ruins, NM, circa 1060, The Center of ...<http://mega-structures.blogspot.com/> <http://mega-structures.blogspot.com/> <http://mega-structures.blogspot.com/> <http://mega-structures.blogspot.com/> Chaco

All Samba binaries have a --option parameter, so you could just add to your winbindd startup script/unit '--option=smb ports=445'. This would only change winbindd, and not smbd or other client tools. Andrew Bartlett On Tue, 2020-04-07 at 21:24 +0000, Raees Khan via samba wrote: > > > I will but changing that would block samba from listening for > connections on port 139.

supported, beside Idle, On call and Ringing ? Can we expect this list to match DEVICE_STATE's one (UNKNOWN | NOT_INUSE | INUSE | BUSY | INVALID | UNAVAILABLE | RINGING | RINGINUSE | ONHOLD) > Might be worth seeing if other phones do the same. > > S > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by