Displaying 20 results from an estimated 4000 matches similar to: "Windows cannot access \\server check the spelling of the name 0x800704cf"
2019 Aug 13
2
Windows cannot access \\server check the spelling of the name 0x800704cf
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.
2019 Aug 10
4
Windows cannot access \\server check the spelling of the name 0x800704cf
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
>
2019 Aug 13
0
Windows cannot access \\server check the spelling of the name 0x800704cf
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
2019 Aug 12
1
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
2019 Aug 12
0
Windows cannot access \\server check the spelling of the name 0x800704cf
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
2019 Aug 09
2
Windows cannot access \\server check the spelling of the name 0x800704cf
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 file server (fs1)
I am using the internal DNS server on the domain
2019 Aug 09
2
Windows cannot access \\server check the spelling of the name 0x800704cf
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
>
2019 Aug 09
0
Windows cannot access \\server check the spelling of the name 0x800704cf
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
2020 May 25
4
Failed to commit objects: DOS code 0x000021bf attempting to add DC to Zentyal 3.2 domain (samba 4.1.7)
----- 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:
2020 May 25
2
Failed to commit objects: DOS code 0x000021bf attempting to add DC to Zentyal 3.2 domain (samba 4.1.7)
----- 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
2020 Apr 23
3
Share inaccessible intermittently and often - restarting smb cures for short time
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
2019 Aug 10
0
Windows cannot access \\server check the spelling of the name 0x800704cf
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.
2020 Apr 23
2
Share inaccessible intermittently and often - restarting smb cures for short time
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]
2020 Apr 24
3
Share inaccessible intermittently and often - restarting smb cures for short time
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
2020 May 25
2
Failed to commit objects: DOS code 0x000021bf attempting to add DC to Zentyal 3.2 domain (samba 4.1.7)
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: Failed to commit objects: DOS code 0x000021bf
And the domain join fails. It looks like it's having some sort of problem with the replication stage but I'm not exactly sure what.
I'm
2020 Apr 24
2
Share inaccessible intermittently and often - restarting smb cures for short time
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
2020 Apr 24
3
Share inaccessible intermittently and often - restarting smb cures for short time
I just installed version 4.11.7 and the problem has gone away so either it's a bug or a new "feature" that we have to set some config setting to fix.
I am still having the annoying issue with deleting thumbs.db files which I currently have on the other install as well. I'm not sure why there is a locking issue with these files but every time I try to delete a folder I get an
2020 May 25
2
Failed to commit objects: DOS code 0x000021bf attempting to add DC to Zentyal 3.2 domain (samba 4.1.7)
So there is no migration path? I really don't want to rebuild my domain if I can help it. I wouldn't mind so much having to recreate users as much as having user's desktop profiles be orphaned.
How would I tell if it was openldap vs pure samba ad-dc?
Rich
----- On May 25, 2020, at 10:52 AM, samba samba at lists.samba.org wrote:
> On 25/05/2020 15:26, Rich Webb via samba
2011 Aug 11
6
unable to mount zfs file system..pl help
# uname -a
Linux testbox 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
# rpm -qa|grep zfs
zfs-test-0.5.2-1
zfs-modules-0.5.2-1_2.6.18_194.el5
zfs-0.5.2-1
zfs-modules-devel-0.5.2-1_2.6.18_194.el5
zfs-devel-0.5.2-1
# zfs list
NAME USED AVAIL REFER MOUNTPOINT
pool1 120K 228G 21K /pool1
pool1/fs1 21K 228G 21K /vik
[root at
2015 Feb 09
3
smbclient works with IP address but not hostname
Hi Ashish,
On 09/02/15 17:50, Ashish Yadav wrote:
> Hi,
>
> On Sun, Feb 8, 2015 at 11:23 AM, Graeme Russ <gruss at tss-engineering.com
> <mailto:gruss at tss-engineering.com>> wrote:
>
> Hi All,
>
> I've configured a Fedora 20 server with samba to share a few user
> directories and a printer.
>
> From a Windows 8 laptop, I am able