similar to: Broken pipes

Using Samba 2.2.7a on FreeBSD 4.7-STABLE. #uname -a FreeBSD fileserver1.smartrafficenter.net 4.7-STABLE FreeBSD 4.7-STABLE #0: Mon Dec 16 19:41:03 EST 2002 +toor@fileserver1.smartrafficenter.net:/usr/obj/usr/src/sys/FILESERVER1 i386 All day long, constantly, I get the following messages in syslog: Jan 14 13:37:55 fileserver1 smbd[57969]: [2003/01/14 13:37:55, 0]

My syslog is constantly bombarded with these messages: Mar 27 07:15:35 fileserver1 smbd[70359]: [2003/03/27 07:15:35, 0] lib/util_sock.c:get_socket_addr(1012) Mar 27 07:15:35 fileserver1 smbd[70359]: getpeername failed. Error was Socket is not connected Mar 27 07:15:35 fileserver1 smbd[70359]: [2003/03/27 07:15:35, 0] lib/util_sock.c:write_socket_data(499) Mar 27 07:15:35 fileserver1

I'm trying to upgrade from Samba 3.0.14a to 3.0.23b. Using the exact same config file that I did in the older version, and using the exact same share directory and file permissions as I did with the old version, a share that I used to be able to access now returns: tree connect failed: NT_STATUS_ACCESS_DENIED When I try to connect to my home directory that's shared on the fly, I

I have been using Samba w/out any problems what so ever for the longest time, but today, I cannot connect to the linux box (shows up in network neighborhood as 'LINUXSERVER'), but when I try to connect from a win2K machine (which normally connects w/NO problems). Here is the output from /var/log/messages (appears the problem is in smbd) May 23 11:34:14 fileserver nmbd[1423]: [2002/05/23

I have an odd automount problem. The first time I look in an automounted filesystem (when the mount is requested), it is empty; the second time it is not. Moreover, I only see this behavior on Centos 4.x systems, but not on Centos 5.0 systems going to the same fileserver. Here's an example, with some details simplified to clarify. In this example, fileserver1 is exporting fs1.

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

hi everyone i am hoping for a bit of direction here, i've tried everything i can find that even closely relates to this. i have a samba server that has shares that can be accessed from windows by simply typing \\192.168.1.1 in windows file explorer, its name has just been changed to fileserver1 and is in dns as fileserver1. it is also in the dns as fserver1. before the name change everything

Hi, I can't get "net view \\<servername>" to work from my Windows test client. It fails with "The network path was not found". I followed some of the online debugging guides and have found that a couple of the test nmblookups on the server are failing. The server is named 'fileserver1' and its IP address is 155.2.196.251 for the purpose of this email.

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,

When I setup Samba4 I already had a master and slave bind9 server so I copied the relevant dns information to my master server however I don't know how to make my existing server authoritative for the zone. It will send notifies to the slave and allow ddns updates but the slave shows this error: "slave-server named[1187]: client 1.1.1.1#22792: received notify for zone

Full_Name: Chris Bodily Version: 1.5.1 OS: W2K Submission from: (NULL) (63.106.106.2) I took the following code directly from the 'split.screen' help page in R and modified one line to highlight the problem I encountered. Basically, it appears that when plotting in split screens and attempting to return to a particular screen to add or update points, the axes from the original plot are

Hi, This is slightly offtopic, but I have been trying to resolve that problem for two days now without much success. It looks like this may be something that works with CENTOS5, but not with CENTOS6! I have two machines, fileserver1 and server5. fileserver1 runs on CENTOS6 (virtualized, if this is important), server5 runs on Centos5. Both are running with the most recent updates. Server5 is a

Hi, I probably found a minor security hole (as it may be IMHO) in my (latest) stable release of SAMBA (2.2.9a-1) Using Win98SE I am logging to Samba server. I am using root preexec and root postexec on Home share's to maintain a list of "correctly logged" users. When a Windows workstation craches, Samba finds this after some 5 long minutes. Until that time, although a new user logs

Hello, everyone, I'm seeing some inconsistent behavior across SMB clients when configuring shares using the "msdfs proxy" parameter, and was hoping to get some advice from the community on this. My issue is that various SMB clients seem to behave differently when this parameter is pointed as a path that includes a sub-folder under the root share. So, given the following share

On Tue, 7 Nov 2017 07:13:19 -0500 Bernard Fay <bernard.fay at gmail.com> wrote: > Yes, our Samba servers are configured as standalone. Windows clients > and Xenservers for storage repositories are connecting to these > shares. > > What does that change for the Unix users as they have to be in the > passdb.tdb file anyway??? > > OK, you asked ;-) Lets say that

On Thu, Jan 05, 2023 at 01:28:55PM -0500, Nick Couchman via samba wrote: >Hello, everyone, >I'm seeing some inconsistent behavior across SMB clients when >configuring shares using the "msdfs proxy" parameter, and was hoping >to get some advice from the community on this. My issue is that >various SMB clients seem to behave differently when this parameter is >pointed

Hey all, I've got an issue with my Samba server. I can't seem to get file shares to map using Server Name, but I can get them to map using IP Address. Here is my smb.conf: [global] workgroup = ADMIN server string = Snap Server timestamp logs = yes dos filetimes = yes dos filemode = yes inherit acls = yes name cache timeout = 0 winbind uid = 101-6000000 winbind gid =

Hi, I already posted this to smb-clients, but I believe that is a very low volume list. We have a very complicated dfs root. Now I'm not positive that this is how we should have done things, but it works very well with Windows clients, so it hasn't been thought about here. This does not work with smbclient or smbmount. I'm using freshly built smbclient from Samba 3.0.21a.

Hi, I'm just installing Samba for the first time and have a problem with name resolution on my test client. Samba 3.0.8 is installed on a RHES system named 'fileserver1 (.our.xxx.edu)'. The clients are Windows 2000 and XP systems. This is a subnet that is part of a larger campus network. There is no Domain, just a workgroup called 'our_adm'. I have a very simple smb.conf file

This is probably a hot topic, and if this has been beaten to the ground, forgive me. I'm not a regular part of the Samba community. Although I have been using Samba for years, I now have to use it in a corporate environment utilizing some of it's more modern features. Let me just say, that it's been several hours of testing/troubleshooting to get where I am now. (And I don't