similar to: Issue with Mandrake 9.1 and Samba

I just finished setting up a Linux RedHat 6.1 system with Samba 2.0.5a. I cannot browse the system from a Windows Nt Domain, but I can browse it just fine from another Linux samba system... The line: [2000/01/27 14:41:47, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(118) become_logon_server_success: Samba is now a logon server for workgroup BERKELEY on subnet 127.0.0.1 looks

Hi... I have exactly the same problem with lsarpcd giving the error "ERROR: setgroups call failed!". Anyone know of a fix?? MWP > Hello > > I was just installing the new TNG 1.0.5 and after i installed and cleaned the > logs i started the dameons and was unable to access the shares on win98. The > computer showed up in Network Neighborhood but i would get a \\comp03

I setup the samba server to be a wins server on my network when ever I browse the network it takes for ever to come up and sometimes it takes awhile to even to bring up the share or I don't see them. I am using lmhost on win xp system and the linux system for dns. When ever I do restart on the samba server it gives me this error. (shutting down nmb services ./smb: line 201: kill (6442) - no

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]

rh61, 2.2.14. The problem is in 2.0.6 also. 1st samba is wins server. 2nd samba uses the 1st samba as wins server. All is ok, but if I use interfaces = eth0 127.0.0.1 bind interfaces only = yes (is there anything wrong in the above lines?) in the 2nd samba, then I get the following in the log.nmb of the 2nd samba: [2000/03/29 15:45:30, 1] nmbd/nmbd.c:main(743) Netbios nameserver version

hi, i setup a samba-3.0.0-2 server under redhat 9. i added this server to a win nt 4.0 domain controller. the nt domaincontroller only runs the following services: wins, dhcp & pdc. nothing more. /etc/samba/smb.conf: [global] workgroup = SCHLICK-ROTO server string = Server - File hosts allow = 172.24. 127. printcap name = /etc/printcap load printers = yes log file =

The only thing related to 'addresses' in my /etc/samba/smb.conf file is a "hosts allow": hosts allow = 192.168.3.0/24 127.1 I'm going to ignore the 'local hosts case, as if I solve the other, the localhost case may get solved by inference. I thought the 'hosts allow' would allow any host on the local 192.168.3.0/24 subnet. The hosts have no problems

When using the global options: ================================ interfaces = eth0, lo bind interfaces only = Yes hosts allow = 192.168.1. 127. ================================ and a secondary loopback address: ================================ ~ # ip addr show dev lo 3: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet

Hi All, On my first internal NIC, Samba is working perfectly. On my new, second internal NIC, I am getting the following in my messages log: libsmb/nmblib.c:send_udp(793) Packet send failed to 192.168.254.255(138) ERRNO=Operation not permitted nmbd/nmbd_packets.c:send_netbios_packet(163) send_netbios_packet: send_packet() to IP 192.168.254.255 port 137 failed I though .255 was a reserved

I admit theres a LOT about the windows networking I dont understand - and even though this may NOT be a SAMBA issue per se, I thought I'd post it here. Have a 400gb samba server thats been working well (am upgrading to current patches today, btw). I've got 3 Win2k workstations, on two subnets, that have drives mapped, and connect every morning on startup just fine. All the machines

Looking for a solution to this problem. I have Googled all over the place but haven't found a definitive answer. I have a Samba Server that ONCE was on a network where there was SECOND Samba Server with IP Address 192.168.20.3. Today, the FIRST server is on a network with an address range 10.0.0.0/255.255.255.0 and it has no way of finding that SECOND Server 192.168.20.3. However,

Hi, Semi-not new to samba, used a previous version a long time ago. I'm using samba on SuSE 9.0, samba version 'Version 2.2.8a-SuSE' 2 network cards on this machine, eth0&1. I've enabled the samba server on this machine and it is functional. However, i only want samba to serve the file system on one of the network cards and not the other. Is this just a simple

SEND: Teoman TURHAN Hi teams. I installed samba 2.0.9 on Alpha server TRU64 unix 4.0F. But I cannot configure --with-dfs because this Tru64 unix was installing chosed filesystem type UFS filesystem. but I used ./configure command and make and make install. I installed ADVFS file system 2 days ago samba 2.2.2 on TRU64 unix. but I don't live a problem. all services were running. UFS BUG

Hello, I installed recently a samba server 3.0.0-15 on Fedora as PDC, it works - generally speaking - but i have a few problems with it (I should begin with "i'm samba virgin - my first time :) ). So, first thing, i was expecting to have something like windoze network neighbourhood in konqueror (smb://), meaning all computers from my network browseable no matter what system they

It seems that my smbd process got fuxed somehow. It appears to have take up all the file handles, and there were over 130 smbd processes running on the system. I'm not entirely sure what happened. My first thought is that something bad happened between the server and the Windows client that's running Kaza (with a couple hundred mid-download files) and it just spiraled out of control,

I've built samba for an embedded mips platform. Since this is an embedded platform, it's possible that some critical file that samba needs is missing but stracing the daemons doesn't reveal anything strange. It's running 2.4.34 kernel. Samba is failing to find any interfaces. [2000/01/02 10:55:01, 3] nmbd/nmbd.c:main(759) Opening sockets 137 [2000/01/02 10:55:01, 10]

I have recently upgraded my Redhat 7.3 server to Fedora FC1 with all related updates. I also upgraded my samba version from 3.0.0 to 3.0.2a. It now seems that my nmbd daemon will not start & subsequently I cannot log in from any Windows client as the netbios server name PDC is not found I think. Before this problem started, I noticed that in order for my DNS ping requests from Windows clients

hello, using SuSE 7.3 with all Patches and SAMBA 2.2.7a-SuSE after a couple of days too many files are opend (bejond 16000) and samba hast to be totally stopped and restartet. the log tells us the following: [2003/03/13 09:21:44, 0] smbd/posix_acls.c:create_canon_ace_lists(919) create_canon_ace_lists: unable to map SID S-1-5-21-823518204-1202660629-842925246-2721 to uid or gid. [2003/03/13

I have a Solaris box and Windows 2K box connecte through a hub, along with a DSL modem. I cannot get the two boxes to work via Samba, here is the relevant details. The status report from SWAT # Samba config file created using SWAT # from localhost (127.0.0.1) # Date: 2001/03/02 12:54:01 # Global parameters [global] netbios name = MARISOL server string =

Hi all! As a die hard slackware user and as a part of my learning pam process I installed debian bookworm (12.4.0) in a vm and setup a domain member server per the instructions in the wiki trying to figure out how debian does it so I can correct some issues I have with how it's done in slackware. Everything seems to be working fine except for the winbind offline logons, what I tried was to