similar to: Initial install - networking problem

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.

Hello, I just recently migrated our samba fileservers to be members of our corporate AD domain, which seemed to work out so far. Now, I experience problems with group membership of groups that are defined on our old ldap server. To avoid recreating all these groups in the AD, i thought it'd be nice to use the old groups with the new user accounts via nsswitch. Samba 3.0.22 on debian/unstable

Running samba version 3.2 on AIX 6.1. Mapping share on windows 7 workstation. I can map the share using \\<ip<file:///\\%3cip> address>\testarea. If I attempt to map using using \\servername\testarea<file:///\\servername\testarea> I receive an error. smbclient -L //<servername>/testarea on the unix box is successful When I run a net view command I receive the

As Gaiseric requested, here is the testparm -v diff of a working and nonworking member server in the NT4 domain. I've tried to align the columns, but it's possible your mail client may mangle them. The only parameter change I have tried is changing 'ntlm auth' to Yes on the the nonworking system. It did not fix anything. Thanks for looking. Dale *# Samba 4.2.14 (working)*

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

Running samba on AIX 6.1. Mapping share on windows 7 workstation. My share will only map using the ip address, not by server name. smbclient -L //<servername>/testarea on the unix box is successful When I run a net view command I receive a system error. C:\Users\Desktop>net view \\<servername>\test<file:///\\%3cservername%3e\test> area System error 53 has occurred. Is the

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]

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 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

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

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

I am running Samba 3rc4 as a PDC. When trying to join my Windows 2000 workstation to the domain, I get the following error (on the win2k box): No mapping between account names and security IDs was done. I've searched Google, the archives of this list, the docs and a Ouija board for answers, with no success.. Can anyone provide a pointer to what it is I'm missing? Thanks in advance.

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

Hi folks, It seems that the setting acl_xattr:ignore system acls = yes reduces Windows compatibility when defined for a share. In all attempts I have used Windows tools (except editing smb.conf) Assume there is a share, where the files and folders in the share root should at least be readable by anybody having access to the share. For the sake of simplicity the following permissions apply on

Hi, I have two samba domains. On one member of DOMAIN1 I set up a share "intranet" with valid users = +"DOMAIN1+webmaster" +"DOMAIN2+TestGroup" Winbindd is running. When I try to access the share from a DOMAIN2 workstation permission is denied. When I look at the logfile, I see that the server tries to find the group of DOMAIN2 (TestGroup) in ldap of the local

Hai, > > In short. My network design previously work with Debian Stretch > Servers and clients and some Windows clients (not many). > > Debian Stretch use Samba 4.5.16 so there is no unix_primary_group > option for the clients. So I have to use the "dirty" tweak of > modifying all my users "primaryGroupID" to the corresponding >

Does you filesystem support extended attributes? What does "|getfattr -n security.NTACL |filename" return?|| On 30.01.2024 16:13, Peter Milesson wrote: > Hi folks, > > It seems that the setting acl_xattr:ignore system acls = yes reduces > Windows compatibility when defined for a share. In all attempts I have > used Windows tools (except editing smb.conf) > > Assume