similar to: 3.0.7 server "NetBIOS over TCP disabled -- no workgroup available"

Getting the following on startup: [2004/11/02 09:57:15, 0] smbd/server.c:main(760) smbd version 3.0.7 started. Copyright Andrew Tridgell and the Samba Team 1992-2004 [2004/11/02 09:57:15, 0] lib/smbldap.c:smbldap_open_connection(623) Failed to issue the StartTLS instruction: Decoding error [2004/11/02 09:57:15, 1] lib/smbldap.c:another_ldap_try(936) Connection to LDAP server failed

The owner of a folder (userid gdunn01) is unable to make any changes to it (rename / delete) through Samba despite being listed as having read/write perms. I'm using winbind for username mapping. I feel like I'm missing something simple. ma21cab5# wbinfo -t checking the trust secret via RPC calls succeeded ma21cab5# ls -ld asdfas/ drwxr-xr-x 2 gdunn01 Domain Users 512 Jun 22 08:50

Hi all Bear with me on this one... We have a problem connecting to a specific port via Oracle TNSPING There are two PC's in our office that are on the same network as the server (i.e. my desktop PC can not get to the server) The server has multiple network interfaces, the primary is a gigabit fibre card on IP xx.16. The secondary is a megabit card on IP xx.80 The tnsping command fails

I compiled the 3.0.21a samba software with the following configure options: configure --prefix=/opt/samba --exec-prefix=/opt/samba --with-krb=/usr/krb5 --with-smbwrapper --with-syslog --with-mandir=/usr/man --with-winbind Everything compiled fine; however, I am unable to see the server on the microsoft network. My smb.conf file looks like the this: [global] workgroup = CAREMARKRX

Hi team, one small query, Is netbios-ns,netbios-dgm and netbios-ssn ports 137,138,139 need to be open to communicate with windows from linux. what was the use of these services??

On Thursday 06 Aug 2015 1:24:29 PM VigneshDhanraj G wrote: > Hi team, > > one small query, > > Is netbios-ns,netbios-dgm and netbios-ssn ports 137,138,139 need to be open > to communicate with windows from linux. > Not really. It depends on what service you want to access. > what was the use of these services?? http://ubiqx.org/cifs/NetBIOS.html

On 11/07/15 04:06, Lee Brown wrote: > Hi Everyone, my first foray into Samba and AD both. > > Not sure if this is an OS or configuration problem. I've found similar > issues, but nothing either recent enough (is related to samba 3) or close > enough. > > FreeBSD-10.1-RELENG, Samba 4.2.2. > > I have the domain provisioned as rfc2307 > I have joined a Win7-virtual

On 11/07/15 10:16, Rowland Penny wrote: > On 11/07/15 04:06, Lee Brown wrote: >> Hi Everyone, my first foray into Samba and AD both. >> >> Not sure if this is an OS or configuration problem. I've found similar >> issues, but nothing either recent enough (is related to samba 3) or >> close >> enough. >> >> FreeBSD-10.1-RELENG, Samba 4.2.2.

Hello, I've been trying to get a solution (or at least an explanation) from the FreeBSD guys at freebsd-questions lists, but I guess no one knew the answer. I am trying to run Samba 3 (latest) in a FreeBSD 7.0 jail (http://en.wikipedia.org/wiki/FreeBSD_Jail). It seems I cannot convince Samba to answer NetBIOS broadcast requests and therefore Windows machines cannot browse it directly by name

Hi Everyone, my first foray into Samba and AD both. Not sure if this is an OS or configuration problem. I've found similar issues, but nothing either recent enough (is related to samba 3) or close enough. FreeBSD-10.1-RELENG, Samba 4.2.2. I have the domain provisioned as rfc2307 I have joined a Win7-virtual machine to the domain I have created a new user with ADUC I have assigned 10000 to

through dns proxy man smb.conf Default: dns proxy = yes >-----Oorspronkelijk bericht----- >Van: samba [mailto:samba-bounces at lists.samba.org] Namens >VigneshDhanraj G >Verzonden: donderdag 6 augustus 2015 11:21 >Aan: Anubhav Rakshit >CC: samba at lists.samba.org; samba-technical at lists.samba.org >Onderwerp: Re: [Samba] Netbios > >thanks a lot guys, > >one

On Tue, 2017-02-07 at 13:06 -0500, James B. Byrne via samba wrote: > Recently we have been having a lot of trouble with time > synchronisation between our samba DC and the domain clients.  We are > not sure what started this issue since the Samba domain went live on > October 11, 2016 and the issues only began to surface this past > January but at some point the time on the clients

On Tue, February 7, 2017 13:06, James B. Byrne wrote: > In any case, we have resolved most of these issues. In dealing with > this I ran across > https://wiki.samba.org/index.php/Time_Synchronisation which contains > this instruction: > > Set up the ntpd.conf File on a DC > . . . > ntpsigndsocket /usr/local/samba/var/lib/ntp_signd/ > > Now, on the FreeBSD host I

Recently we have been having a lot of trouble with time synchronisation between our samba DC and the domain clients. We are not sure what started this issue since the Samba domain went live on October 11, 2016 and the issues only began to surface this past January but at some point the time on the clients and the DC diverged enough that we began to get strange network errors. Once we figured out

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm running stock FreeBSD with services running: samba (connections allowed only from local network), lpd (same), bind (all interfaces), apache (all), zope (local) This machine is home gateway/http/printserver. Recently some strange things happened as my printer all of sudden started to print stuff when nobody prints... luckily (or

>>> > Considering any editing/buffering benefits are only marginal (AFAIK) there are not benefits with the current approach.On the other hand the list of potential problems includes: > 1) We cannot use the ubiquitous EFI PXEbc protocol forcing us to rely on the (not always present) EFI Binding Services. > Best,Patrick Speaking utterly ignorantly here... could this switch help

Greetings! I am still struggling with the issue that after vampiring from NT4 domain to Samba 3.0.7 with ldap backend, Windows XP cannot find the domain controller. In particular, WXP is an XP Prof which signed in AB_INITIO_DOM domain. After the migration I put the Samba Server (Priscilla) and WXP in an isolated network, and started up Priscilla as PDC for the network. But WXP

Hello all, After upgrading to 3.0.23c on my FreeBSD 6.1 box Samba stopped working on any connections. When connecting to smbd, tcp session is established (SYN, SYN+ACK, ACK) then a client send a NEGOTIATION packet, and after some timeout (about 10-15 seconds) this tcp session is closed (by the client) because no response to NEG. packet was received. Then after 75 seconds (counting from the

Hello, I am new to samba and i would to well secure it. In smb.conf, I entered the following lines : hosts allow = 192.168.0.2 127.0.0.1 hosts deny = 0.0.0.0/0 bind interfaces only = yes interfaces = eth0 lo I thought that it would only listens on the local machine and my internal Lan (which is on eth0 192.168.0.1) but nmbd seems to always listen on UDP/137 and UDP/138 (netbios-ns and

Hello, I would like to ask you if its possible to run Samba on an other port than 137-139? I tried once to edit the "/etc/services" File. The lines: ... netbios-ns 137/tcp netbios-ns 137/udp netbios-dgm 138/tcp netbios-dgm 138/udp netbios-ssn 139/tcp netbios-ssn 139/udp ... I changed it to: ... netbios-ns 6998/tcp netbios-ns 6998/udp netbios-dgm 6999/tcp netbios-dgm 6999/udp