similar to: clients loose connection/cant save to samba server (samba-3.0.0-2)

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]

hi, some days ago i posted the message below. i found out that the problem was that samba lost the connection to our nt 4.0 domain controller. after i did "net join -w domainname -U Administrator" the probem was solved. when i installed samba i did the net join to join our domain with success. yesterday we got the same problem again. the users couldnt write or create files on the server

hi, i installed samba-3.0.0beta2-1 on a rh9 (kernel-2.4.20-18.9). everthing was working fine but since today when i want to copy files onto the samba server i got from a win nt 4.0 client the error msg that he got a network problem. when i check the samba logfile i found this: /var/log/samba/log.machinename: [2003/07/15 11:47:32, 2] smbd/open.c:open_file(240) administrator opened file

Linux 2.2.14, samba 2.0.7 Summary: samba kept __MSBROWSE__ registered but thought it was not the master browser. Details: 1) samba started and became master browser (6/13/2000 0.00) 2) then there was a problem on the network (I played with ipchains...) 3) samba received an announce from a win9x pc claiming it was MB (6/13/2000 circa 8.00AM) Due to the problems of point2, the election that

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

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

I'm hoping someone can give me a hand in figuring out this problem, I have seen several other similar problems in searching, but nothing that exactly matches what I am seeing here. I have recently migrated a client from a Samba server running 2.2.7 (Redhat 9) to 3.0.2 (Fedora 1). The samba installation is running as a PDC for 5 Win XP workstations and was working perfectly prior to the

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

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

Hello, I have attached a patch wich adds support for 4kb pages to xen 2.0 proper. (No changes were required from xen 2.0-beta. Apprently mixing xenolinux from one release and xen kernel from another release is a no-no. Other than that there were no problems. Thanks to Rupert Schlick for helping to nail it down. The "noacpi" parameter does not seem to be mandatory. Finally

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

SIMPLIFY SHARING YOUR RUBYGEMS ON RUBYFORGE! ~> gem install rubyforge SYNOPSIS rubyforge [options]* mode [mode_args]* DESCRIPTION simplistic script which automates a limited set of rubyforge operations MODES setup() initializes your .rubyforge directory. you need to run this first before doing anything else. example : rubyforge setup login()

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

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

I have a new MDK 9.1 server running iptables, pop, smtp, ftp, www, ssh, and trying tio get samba up on it. The box has two nic's in it. inside net is 192.168.1.0/24 the outside is a /28 net I have uip forwarding running and also shorewall. I also have an older Samba box running on the internal net. The problem is this. All the winblows boxes can see the old samba server but not the new server.

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