similar to: Error in logs regarding samba

Here's the sitch: I have a RH 6 machine and an NT 4.0 SP3 machine that I want to use Samba to make the Linux box space available to the NT client. There is no DNS, and there is no Internet connection. Each of the two machines has a "dummy IP", specifically 192.168.255.253 (NT) and 192.168.255.254 (Linux). Trying to browse on the NT box results in either a "Cannot obtain list of

Hello. I'm running RH 7.1, with Samba 2.2.2. VERY often I get a SIGHUP to smbd and it'll dump the workgroups. I also get a "Discarding datagram from IP 216.202.200.103. Source name ROUTER<00> is one of our names" all the time also. This line FILLS my logs. I don't understand this one, because I have the interfaces line specified in smb.conf to use only the local

Hello All, I have recently switched back over from using the MySQL backend to the standard smbpasswd file in an effort to make our implementation of Samba better.\ I am still having a great problem with getting messages from the nmbd daemon saying that ------------------------ [2005/09/10 14:53:43, 0] nmbd/nmbd_packets.c:process_browse_packet(1050) process_browse_packet: Discarding

All, first off thanks for any advice on this issue. Last night, my fileserver crashed on me. When i came in this morning, here is what the syslog was filled up with: May 20 21:54:26 fileserver1 nmbd[15324]: [2004/05/20 21:54:26, 0] nmbd/nmbd_packets.c:process_browse_packet(1063) May 20 21:54:26 fileserver1 nmbd[15324]: process_browse_packet: Discarding datagram from IP 192.168.1.6. Source name

I am having trouble with one of my samba PDC's. It does not recognize itself as the domain master browser even though it is set to be so. I can not add machines to this domain and I suspect this is why. Has anybody seen this or know what causes it? Notice this: DOMAIN_ALBANY(3) current master browser = ALBANY_PDC DOMAIN_NYC(2) current master browser = NYC_PDC

I've been messing around with running samba 3.4.14 inside a freebsd jail over the last couple of days, and am running into an odd problem where wbinfo -u and wbinfo -g succeed, but getent passwd fails (insofar that it shows only local users, but none of the domain users). Here's my smb.conf: [global] interfaces =192.168.0.16/32 bind interfaces only =yes security

Specifics samba-3.0.0beta1-1.i386.rpm on RedHat 9 and smbpasswd authentication, the machine is the PDC and security is set for user. The machine account was setup on the fly and it appears in passwd, shadow, and smbpasswd files as it should. However it seemed to take a very long time to join the domain, about 1-1/2 minutes. I can browse the Samba PDC machine and access the shares, etc. After

No takers thus far. These are the Samba 4.2 changes to which I previously referred (https://www.samba.org/samba/history/samba-4.2.0.html) : For the client side we have the following new options: "require strong key" (yes by default), "reject md5 servers" (no by default). E.g. for Samba 3.0.37 you need "require strong key = no" and for NT4 DCs

You may have included this in another email however I will ask anyway, did you set DNS to your server in the Linux and Windows clients? Can you check if a Windows Server can join? Can you use DNS management to check the DNS on you samba server? On Mar 28, 2016 2:15 PM, "Dale Schroeder" <dale at briannassaladdressing.com> wrote: > No takers thus far. These are the Samba 4.2

Hi Dear Samba Gurus, We're planing to migrate the old samba server to a new samba server. But the person who maintain old samba server have left, so we need to figure out the configuration steps from the old config file. Now the things that confused me now is the setting with "security=domain", the old samba server config global sections are: log level = 3 netbios

Help! I have two computers, both running HP-UX 11.0, both running 3.0 alpha23 (the second computer's samba trees were copied from the first, so they are identical). Mapping a drive from an XP SP1 computer has NO problems on the first HP server. On the second one, it displays the message "Configuration information could not be read from the domain controller, either because the machine

Hi all, I am a samba rookie with a problem. I have replaced an old server with a new server, and copied over the original samba config which was for samba file but the new server has samba 3.0.5 while the old version was 2.0.7. I had problems connecting to samba, so I tried using the supplied default config file and then migrated the original settings to the new file. problems still persisted.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I try to set up a Linux/Samba box to authenticate users (on Windows 2000 and XP boxes) against a Windows NT4 Primary domain controller but failed with what I tried so far. - - both machines are on the same local network (192.168.17.X) - - the windows box runs NT4. I havn't set up this and I don't know much about it either but I have

hi Louis, same result: NT_STATUS_LOGON_FAILURE heinz Am Dienstag, 14. April 2015 11:20 CEST, L.P.H. van Belle <belle at bazuin.nl> schrieb: > can you try : > > smbclient //SERVER.DOMAIN.TLD/netlogon -k > > bet that works.. > > Louis > > > >-----Oorspronkelijk bericht----- > >Van: heinz.hoelzl at gvcc.net > >[mailto:samba-bounces

can you try : smbclient //SERVER.DOMAIN.TLD/netlogon -k bet that works.. Louis >-----Oorspronkelijk bericht----- >Van: heinz.hoelzl at gvcc.net >[mailto:samba-bounces at lists.samba.org] Namens Heinz H?lzl >Verzonden: dinsdag 14 april 2015 10:55 >Aan: samba at lists.samba.org >CC: pug at felsing.net; schnaggy at schnaggy.de >Onderwerp: Re: [Samba] samba 4.2 RDP

I have an NT domain on Debian Stretch. It's been upgraded numerous times, but has been running for almost a decade. Since upgrading from 4.1.17 to 4.3.3 (huge Debian jump), then to 4.3.6, clients cannot connect to shares. Prior to upgrading, I found the changes mentioned for 4.2 regarding NT domains and applied them. Even so, I still cannot connect to network shares nor print to

hi, now i did some tests with the "auth methods" option. "auth methods = sam, sam_ignoredomain, unix, winbind, wbc, trustdomain, ntdomain, guest" -> RDP works -> smbclient -k does not work "auth methods = sam, sam_ignoredomain, unix, winbind, wbc, trustdomain, ntdomain, guest, samba4" -> RDP hangs an the welcome-scrren -> smbclient -k works fine

Question: I want to setup a Samba server as a domain member, allowing Windows PC to map unix server directories, but having the authentication performed by our Windows Domain Controller(s). I'm basically following this example from the Samba docs: http://us1.samba.org/samba/docs/man/Samba3-HOWTO/domain-member.html#id2538809 It appears to me that I must "net join" the domain from

> hi all, > > my working samba-4.1.7 member of a samba3 domain (samba-3.5.3) failed > while updating to samba-4.2.0. Users were no longer able to access > shares because the trust account was broken. > > According to release notes (Winbindd/Netlogon improvements): > > For the client side we have the following new options: > "require strong key" (yes by

Hi I've got a home-made, small file server running on Samba 2.4.1.11 from Debian Wheezy backports repo. I've noticed following lines in log.nmbd file: [2014/11/17 22:54:00, 0] nmbd/nmbd.c:66(terminate) Got SIGTERM: going down... [2014/11/17 22:54:00, 0] libsmb/nmblib.c:856(send_udp) Packet send failed to 127.0.0.1(137) ERRNO=Operation not permitted [2014/11/17 22:54:00, 0]