similar to: Windows cannot access \\server check the spelling of the name 0x800704cf

>From FS1 (file server): #> cat /etc/hostname fs1.webb.local #> cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.5.161 fs1.webb.local fs1 #> cat /etc/resolv.conf # Generated by NetworkManager search webb.local nameserver 192.168.5.160 #> host -t A

I don't think that I have Avahi running anywhere. It wasn't found on DC2 or FS1 servers - even though everywhere I read that it's on by default in CentOS 7. Thanks, Rich > if your dns domain really is 'webb.local', then turn off Avahi everywhere. > > Rowland > > > > -- > To unsubscribe from this list go to the following URL and read the >

Hai Rich, Your output of ipconfig /all Where are these? Primary Dns Suffix . . . . . . . : DNS Suffix Search List. . . . . . : This one is below in the output. Connection-specific DNS Suffix . : Verify above again, if these 3 are all there and set to webb.local Then try this : in you network settings, disable ipv6 Beside ipv6 and the 2 missing outputs, i see the same here on my pc.

On 09/08/2019 21:31, Rich Webb via samba wrote: > Hello, > > I am randomly getting this message when attempting to connect to my samba 4 file server by entering \\server in the run command in Windows. If I enter \\ip address then it will work every time. This seems like a DNS issue but not sure why. > > I am running Samba version 4.9.2 on both the domain controller (dc2) and the

So then looking at my config files for both machines you see no problems there? I'm testing now, but I'm wondering if this is only happening on windows 10 clients. Thanks, Rich > Avahi is the usual problem if you use '.local' (which isn't recommended > any more), but the more I think about this, I begin to think this is a > Windows problem. > > Rowland >

Hai, Please keep mailing to the list, that migh help others later on also. Now, you pc config looks ok. > With NetBIOS disabled I continue to be able to access the > server with \\fs1 so is this likely a netbios bug maybe with 10? Able or not able? And not its not a bug, its a feature, SMB1 is getting killed, this is an inheritance of it. The other things in you configs look all

Windows 10? Then this is normal behaivor. > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Rowland penny via samba > Verzonden: maandag 12 augustus 2019 15:50 > Aan: sambalist > Onderwerp: Re: [Samba] Windows cannot access \\server check > the spelling of the name 0x800704cf > > On 12/08/2019 14:18, Rich Webb wrote:

On 09/08/2019 22:54, Rich Webb via samba wrote: > I don't think that I have Avahi running anywhere. It wasn't found on DC2 or FS1 servers - even though everywhere I read that it's on by default in CentOS 7. Avahi is the usual problem if you use '.local' (which isn't recommended any more), but the more I think about this, I begin to think this is a Windows problem.

Thanks Louis for the reply. I will have to check the version when I get home but I *believe* it's 1809. I have several windows 10 partitions with a multi-boot manager on my various drives that I use for different things and they all seem to exhibit this behavior. I haven't tried this in Windows 7 which I also have. I have a firewall on my internet connection so I have the Windows

----- On May 25, 2020, at 5:22 PM, Andrew Bartlett abartlet at samba.org wrote: > On Mon, 2020-05-25 at 10:26 -0400, Rich Webb via samba wrote: >> ----- On May 24, 2020, at 11:30 PM, samba samba at lists.samba.org >> wrote: >> >> > On Sun, 2020-05-24 at 23:01 -0400, Rich Webb via samba wrote: >> > > Hello, >> > > >> > > I'm

Ok increased logging and got the error here is what got logged: 2020/04/23 14:03:17.514132, 3] ../../source3/smbd/smb2_server.c:3274(smbd_smb2_request_error_ex) smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] status[NT_STATUS_SHARING_VIOLATION] || at ../../source3/smbd/smb2_create.c:334 [2020/04/23 14:03:17.514206, 3]

----- On May 24, 2020, at 11:30 PM, samba samba at lists.samba.org wrote: > On Sun, 2020-05-24 at 23:01 -0400, Rich Webb via samba wrote: >> Hello, >> >> I'm attempting to join a new samba 4 server version 4.12.3 to an >> existing samba 4 domain running on Zentyal 3.2 (samba version >> 4.1.7). >> >> I'm getting the error in the subject line:

Same here, I had also wrote to the mailing list, 2 Customers has the same issue after upgrading to 4.12 Windows Clients get the error ?another prosscess is in use? or ?wrong handle? when a user try to open a network share. After restart samba it?s working for a little moment but mostly not. We?re using Debian 10 Buster and Samba Version is: Version 4.12.1-SerNet-Debian-5.buster Von: samba

What's the content of your /etc/nsswitch.conf? Am 19. Dezember 2014 14:22:56 MEZ, schrieb Rich Webb <rwebb at zylatech.com>: >Matt, > >Thanks for the reply. I'm not trying to add the "users" group. I'm >trying to add the "Domain Users" group. That is the reason for the \ >in >front of the space. It's translated as a literal. I think

Hello, I'm running Samba 4.12.1 both as a domain controller on one box (DC1) and as a joined member on another box for a file server (FS1). I have three shares on FS1 and intermittently I am getting a message that says "\\fs1\shared is not accessible. You might not have permissions to use this network resource. Contact the administrator of this server to find out if you have access

Im did not follow the complete thread, but you can check the following. smb.conf ## map id's outside to domain to tdb files. idmap config *:backend = tdb idmap config *:range = 50001-80000 ## map ids from the domain the range may not overlap ! idmap config DOMAIN:backend = ad idmap config DOMAIN:schema_mode = rfc2307 idmap config DOMAIN:range = 10000-40000 winbind

Don?t think we?re the only one with this problem, We use it how I said for 3 Companies and we have this issue at all our customers after upgrade to 4.12, before we never had this problem. Downgrade will solve this problem but stay always on an old version brings in future new problems. We have a sernet subscription but no support package, that?s the reason why I write here. The question is here

On 19/12/14 13:22, Rich Webb wrote: > Matt, > > Thanks for the reply. I'm not trying to add the "users" group. I'm > trying to add the "Domain Users" group. That is the reason for the \ in > front of the space. It's translated as a literal. I think I could also > put quotes around it and not have to use the \ and the space. > > The

Hi there, I wonder if anyone can help me? I recently created an active directory setup with a primary domain controller ad1 and secondary domain controller ad2 for a domain SAMDOM. In-line with what I understand to be Samba best practices I then setup a separate file-server fs1 on which I created a file share, /fsrv/shares/OgdenFiles/. This has all been done using Samba version

We're beginning a migration from FreeBSD w/ Samba Version 3.0.28a to Gentoo Linux w/ Samba Version 3.0.33. Both the BSD system and the Linux system are joined to the domain, using the same krb5.conf file and nearly identical global sections of the smb.conf file. What I've found is the UID and GID are not aligned with each other. For example: (dc2: 14:52:53 </var/db/samba>)