Accessing Windows CIFS Shares via Nautilus

Hi,
I've recently installed and configured Solaris 11, am having problems accessing Windows CIFS shares via Nautilus.
I've installed both samba (needed for CUPS to print to printers connect to a windows pc) and smb/client. The smb/client and samba services are running. The smb/server service is not installed.
I can print to any printer on the windows PC I'm trying to access via Nautilus, so I know my username/password for accessing the pc are correct.
I can also manually mount any share on the windows PC via the cli (eg mount -F smfs -o user=elin //elink/users /mnt), and browse the files directly that way, except the file permisssions don't seem to align with any unix user. Again this just shows that the username/password combination is ok.
For Samba, I'm using the default smb.conf file as /etc/samba/samba.conf. Workgroup is set to WORKGROUP in smb.conf.
On the Windows pc, in the security event viewer, I can see the auth request, however is failing with bad password (event ID 4776, error code 0x006a). In the default group policy object for networking, I've set to accept "LM & NT, NTLMv2 when neogiatated", as this allows legacy clients to connect. (Legacy meaning NT4, Win95, etc, and also has the benefit of allowing other OSes to connect as well).
I'm also able to access the WIndows PC CIFS shares from an Arch Linux based setup (running GNOME 3.2 w/ Nautilus 3.2), so I doubt it's the Windows side of things causing the problems. Additionally, when I was running Solaris 10u9 (just before upgrading to Sol11), I was able to access the shares via Nautilus as well.
So my question is:
1. Does Nautilus use Samba or the Oracle smb/client service to handle mount windows CIFS shares?
2. What log files or configuration files do I need to looking at to help with this error?
As a side question,
I've found that on a clean installation running the "Print Manager" accesses CUPS fine, but once you install a printer, it'll no longer connect to CUPS, unless run from the cli "sudo system-config-printers". So this is a permissions issue, where's the best place to fix/handle that one.

Replying to my own thread, as I have a possible but very-hackish solution.
To add some further details to my original post.
There are 4 PCs on the LAN.
1. Hellfire - OS = Solaris 11 11/11
2. Brimstone - OS = Arch Linux
3. Elink - OS = Win7 Pro x64 SP1
4. IsaacPC - OS = WinXP Home SP3
Attempting to connect to Elink from Hellfire, accessing CIFS shares via Nautulis fails. (Mounting shares via Nautulis fails, but works fine from CLI using 'mount' command which to my understanding uses the smb/client service to work). Elink also hosts all the printers on the LAN, a HP LJ1200 and an Epson Fax/Printer/Scanner.
Helfire does attempt to authenticate, as listed in the event logs on the Win7 PC (elink), but is returning bad password when using Nautulis. (but printing from hellfire to either printer on elink works fine, as does mounting CIFS shares using 'mount').
Booting the live CD of Solaris 11, also exhibits the same non-working behaviour when attempting to mount CIFS shares in Nautulis.
Attempting to access CIFS shares on elink from Brimstone (via Nautulis 3.2 within GNOME 3.2), or from IsaacPC works fine.
Hellfire configuration.
Samba is installed, but NOT running (samba is needed for accessing the printers on elink, as CUPS needs smbspool which is part of the samba package), and the native smb/client service is also running.
smb.conf is a direct copy of the default *.conf file, except the WORKGROUP is set to 'WORKGORUP'. There is a symlink to smb.conf in /etc/sfw/smb.conf -> /etc/samba/smb.conf
Onto the hackish-fix.
I've noticed that there are 2 copies of libsmbclient.so installed on the system, one in /usr/sfw/lib (part of the "libsmbclient" package) and another in /usr/lib/samba (part of the "samba" package).
"libsmbclient" appears to be based on samba 3.5.8 codebase, and is linked to the gvfsd-smb daemon (this is the software that Nautulis uses to talk SMB to access CIFS shares).
"samba" is based on the samba 3.5.10 codebase, and it's installation has nothing to do with GNOME or Nautulis in any manner.
Using any of the samba included tools to test SMB/CIFS functions, work with 1 minor exception (which I'll list below). eg, using smbclient I can list all shares on any PC on the LAN, etc.
So as a hunch, I renamed the libsmbclient.so.0 in /usr/sfw/lib, and symlinked /usr/sfw/lib/libsmbclient.so.0 -> /usr/lib/samba/libsmbclient.so.0 (so that gvfsd-smb is linked against the slightly newer version of the libsmbclient.so as included in the samba package located in /usr/lib/samba).
I rebooted Hellfire, and now I'm able to access CIFS shares via Nautulis, provided that some form of authentication is needed (that is a username and password is needed - guest access and blanks passwords don't work - but these IMO should be disabled immediately as part of a baseline security package in regards to Windows - so no harm there).
Now to the minor exception I noted earlier. When using smbclient to actually connect and transfer files, I get:
ld.so.1: smbclient: fatal: relocation error: file /usr/lib/libreadline.so.5: symbol tgetent: referenced symbol not found
As far as I know, tgetent is part of libtermcap.so, so I guess when building smbclient or libreadline.so, the link reference to termcap was left out? (or something like that). Anyway, that's another issue...

Similar Messages

Windows XP users can't access SMB/CIFS shares on MAC OSX10.4.4 Xserve bug?

The Xserves are new for us. This problem involves two of the 10.4 xerserves.
1 serves as an Open Directory System Master(10.4.3). 2 Serves as a file share & backup (10.4.4).
Both are production machines and cannot easily be restarted.
There is no Windows network, Active Directory or Windows domain in our network.
We created a SMB and AFP share on the file server which is a member of the Open Directory. (It is bound and kerberized to server 1).
The users all have accounts in the OD system and all passwords are Open Directory. Our users can ssh into the various xserves (including the file share server 2) and authenticate against OD.
We made the shares available via smb under Protocols --> Windows File Settings. We turned the Windows Service on in Server Admin. I'ts a standalone server and all the authentication types are checked under access.
The MAC (powerbook) users can access the share fine. The Windows users can't. The Windows laptops can see the file share server (through search - not visable is Network Neighborhood) but when they try and connect they are presented by an authentication box that just keeps cycling over and over regardless of what the user types as user name & passwd.
I tried to access the smb share with my powerbook(10.4.4) and have the same issue. I'm presented with an authentication box but authentication fails.
The Windows File Service Log shows:
auth.c:checkntlmpassword(312)
checkntlmpassword: Authentication for user [csmith] -> [csmith] FAILED with error NTSTATUS_WRONGPASSWORD
[2006/02/24 21:52:03, 1] authods.c:opendirectory_authuser(212)
User "csmith" failed to authenticate with "dsAuthMethodStandard:dsAuthSMBNTKey" (-14090)
[2006/02/24 21:52:03, 1] authods.c:opendirectory_smb_pwd_checkntlmv1(427)
opendirectorysmb_pwd_checkntlmv1: [-14090]opendirectoryauthuser
[2006/02/24 21:52:03, 2] /SourceCache/samba/samba-92.15/samba/source/auth/auth.c:checkntlmpassword(312)
checkntlmpassword: Authentication for user [csmith] -> [csmith] FAILED with error NTSTATUS_WRONGPASSWORD
[2006/02/24 21:52:03, 1] authods.c:opendirectory_authuser(212)
User "csmith" failed to authenticate with "dsAuthMethodStandard:dsAuthSMBNTKey" (-14090)
[2006/02/24 21:52:03, 1] authods.c:opendirectory_smb_pwd_checkntlmv1(427)
opendirectorysmb_pwd_checkntlmv1: [-14090]opendirectoryauthuser
[2006/02/24 21:52:03, 2] /SourceCache/samba/samba-92.15/samba/source/auth/auth.c:checkntlmpassword(312)
checkntlmpassword: Authentication for user [csmith] -> [csmith] FAILED with error NTSTATUS_WRONGPASSWORD
[2006/02/24 21:52:03, 2] /SourceCache/samba/samba-92.15/samba/source/smbd/server.c:exit_server(595)
Closing connections
I've googled this error and it seems that there a lot of engineers out there with the same problem but no answers. Could this be a bug with Apple's SMB process? Is there something I've missed? (I've looked at the smb.conf and have even turned off deny clear text passwords - I've even tried granting guest access) Anyone have any ideas?

On the server itself, run the following in the Terminal:
(from a few different sources):
run ps -auxw | grep Password
to see if Password service is running
Also check the logs in /Library/Logs/PasswordService
Try: id username
and see if you get some info returned.
Ex: id jimguy
You should get some info about uid, gid, groups.
sudo killall -USR1 DirectoryService
Then try to login from a client machine.
Be sure to re-issue
sudo killall -USR1 DirectoryService
in order to stop the (far more) verbose logging.
Then check the logs in /Library/Logs/DirectoryService
In Open Directory, you might want to revert to standalone (this will destory the existing OD setup) and then re-promote to OD Master. You'll lose all OD users however when doing so. If you don't have many, this may be best.
You'll want to verify the hostname, and forward & reverse DNS lookups before re-promoting, and watch for any errors when promoting to OD master
See, when you say "The real clue is that I'm unable to access the shares from my Powerbook G4 with my Open Directory account. I can log in to the file share as the local admin though and that's why I'm thinking there is a bug in the samba/OD relationship. " - that's the real clue indeed.
The local admin account, the first admin account you setup on the server, is indeed local, and resides in NetInfo, not Open Directory.
So something is afoul in your OD.

Macbook pro can no longer access windows file share. 'This file server is available on your computer'

Hi all,
We have a consultant who uses a macbook pro to access the internet and a windows share within our network. He has been accessing the internet and the windows share fine for over 4 weeks and overnight he can no longer access the internet or this windows share. I have got the error down to a specific windows share which is actually a share on a DC hence the loss of internet. When this user plugs in via ethernet he can view all network locations as expected and can access everyone succesfully bar this specific one. Everytime he tries to access this share he gets the following error: 'This file server is available on your computer. Access the volumes and files locally'. I have another macbook pro that can successfully access this share.
I have tried renewing leases, browsing the network in finder, using 'cmd + k' all produce the same message.
The user is running Mountain Lion
Any ideas?
Adam

Find and delete the ~/Library/Preferences/com.apple.sidebarlists.plist file. This is what keeps track of all your current server share mounts. Maybe the file is corrupt or something. Once you delete it, reboot the machine and then try again. Don't empty the trash until you're sure everything works after the reboot.

Cannot access Windows 7 share from 10.5.8

I have a PC running Windows 7 Ultimate with a share named "share" secured to my Windows user id. I am able to connect to the share from my Macbook pro (in finder) with my id/password and I can see the share, but when I try to open the folder representing the share I get the message "The operation cannot not be completed because the original item for share cannot be found.
If I go to the PC and disable sharing the folder, and then re-enable sharing the folder I can access the files in the share temporarily. After some period of time (often after the Macbook has gone to sleep) the error returns.
Running OS X 10.5.8 on a Macbook pro.

Hi -
Sorry for not being more clear: I can only have file access from my Mac. I.e. I have no other access to the PC Server than through smb. I have no right to set or reset access rights. But if the rights are set ok for smb://server/main and I cannot open the sub-directory /a though finder, why does it then work if I use
smb://server/main/a ? And so forth? That problem did not occur before upgrading to 10.5.5.

Accessing windows shared printer via mac over wireless

So i want to share my deskjet 812c thats attached to my pc and be able to print via my MBP over wireless. I simply shared teh printer in windows, but have yet been able to figure it out, or to get it to work. It seems that the MBP will not see the printer, so any advice or any walk throughs would be appreciated.
Thanks

To connect to a shared Windows printer, open the Printer Setup Utility and click More Printers. For the new window, click the drop-down and select Windows Printing and then Network Neighborhood. The workgroup name that has been configured in the Windows computer should display. Double-click the workgroup name and then select the computer name from the new list. A new window will appear asking you to enter your Windows account name and password. Enter these details and click OK. Select the printer share name from the list and then for the Printer Model, browse to HP and then to the Deskjet 812C. If this model is not listed, download a copy of Gutenprint 5.0.0 for Mac OS X (http://gimp-print.sourceforge.net/MacOSX.php3). This has the 812C which you can use for network printing. With the 812C selected, click Add.
Note that if you are not prompted to authenticate to the Windows computer, then this can impact your ability to connect to shares, especially on XP SP2. You will need to either enable the Guest account or create an account on the Windows computer for the MacBook.

Accessing Windows file share painfully slow in OS X 10.8

Hello!
I work with a company that has one Mac in the network - an iMac 12,2 running OS X 10.8.4. The computer's user needs to work off of the server quite frequently - it's a Windows Server 2008 R2 server - particularly with shared files. Problem is, when she goes to access the shared drives through the Finder, it is painfully slow. It often takes 5-10 seconds just for a directory listing to show, and opening and manipulating files takes significantly longer. I've tried a number of things to try to speed things up, most recently indexing the network drives she uses and installing a Thunderbolt Ethernet Adapter to use instead of the regular wired network card. That hasn't helped though. Has anyone else run into this problem, and if so, how were you able to fix it?
Thanks in advance!

Hello!
I work with a company that has one Mac in the network - an iMac 12,2 running OS X 10.8.4. The computer's user needs to work off of the server quite frequently - it's a Windows Server 2008 R2 server - particularly with shared files. Problem is, when she goes to access the shared drives through the Finder, it is painfully slow. It often takes 5-10 seconds just for a directory listing to show, and opening and manipulating files takes significantly longer. I've tried a number of things to try to speed things up, most recently indexing the network drives she uses and installing a Thunderbolt Ethernet Adapter to use instead of the regular wired network card. That hasn't helped though. Has anyone else run into this problem, and if so, how were you able to fix it?
Thanks in advance!

Cannot access CIFS shares from Windows 2008R2 on NSS3000

Hi,
I am trying to upgrade our 2008 domain to 2008R2 but with that last version we cannot access to cifs shares on the NSS3000. Access from all other clients are OK. It was 100% OK under 2008...
Whether I use the IP or the FQDN, I got an error from Windows 2008R2. From IP, I got "No process is on the other end of pipe." and from network Gui, I got "Windows cannot access \\nas0026CB647BC6. Check the spelling of the name...blabla. Details : Error Code : 0x80070035, The network path was not found".
On the NAS, I got this errors in the cifs logs :
Feb 24 14:12:45 NAS0026cb647bc6 winbindd[28457]: rpc_api_pipe: Remote machine WIN2008-PDC.bluemoon.holywell.leics pipe \NETLOGON fnum 0x4002returned critical error. Error was NT_STATUS_PIPE_DISCONNECTED
Feb 24 14:12:45 NAS0026cb647bc6 winbindd[28457]: [2011/02/24 14:12:45, 0] rpc_client/cli_pipe.c:rpc_api_pipe(790)
Feb 24 14:12:45 NAS0026cb647bc6 winbindd[28457]: rpc_api_pipe: Remote machine WIN2008-PDC.bluemoon.holywell.leics pipe \NETLOGON fnum 0x4002returned critical error. Error was NT_STATUS_PIPE_DISCONNECTED
Feb 24 14:12:45 NAS0026cb647bc6 winbindd[28457]: [2011/02/24 14:12:45, 0] rpc_client/cli_pipe.c:rpc_api_pipe(790)
Feb 24 14:12:45 NAS0026cb647bc6 winbindd[28457]: rpc_api_pipe: Remote machine WIN2008-PDC.bluemoon.holywell.leics pipe \NETLOGON fnum 0x4002returned critical error. Error was NT_STATUS_PIPE_DISCONNECTED
Feb 24 14:12:45 NAS0026cb647bc6 winbindd[28457]: [2011/02/24 14:12:45, 0] rpc_client/cli_pipe.c:rpc_api_pipe(790)
Feb 24 14:12:45 NAS0026cb647bc6 winbindd[28457]: rpc_api_pipe: Remote machine WIN2008-PDC.bluemoon.holywell.leics pipe \NETLOGON fnum 0x4002returned critical error. Error was NT_STATUS_PIPE_DISCONNECTED
Feb 24 14:12:45 NAS0026cb647bc6 winbindd[28457]: [2011/02/24 14:12:45, 0] rpc_client/cli_pipe.c:rpc_api_pipe(790)
Feb 24 14:12:45 NAS0026cb647bc6 winbindd[28457]: rpc_api_pipe: Remote machine WIN2008-PDC.bluemoon.holywell.leics pipe \NETLOGON fnum 0x4002returned critical error. Error was NT_STATUS_PIPE_DISCONNECTED
Feb 24 14:12:48 NAS0026cb647bc6 winbindd[28457]: [2011/02/24 14:12:48, 0] rpc_client/cli_pipe.c:rpc_api_pipe(790)
It is likely to be an incompatibility between Windows 2008R2 smbv2 and the NSS3000 smbd but I can't find any firmware update and I can't find the process to allow in the registry.
I can ping it, I can connect on the web interface, I can connect on FTP but no CIFS at all.
Firmware version running is 1.20.1. Hardware rev : V03.
Any idea?

Hi SpaceBass, have you looked into sharepoints or into Netinfo manager. I have been playing around with sharepoints and it does let me enter non local users into the sharing prefs- albeit manually. Only thing is , depending on the number of macs you have, it could be a long and tedious job entering it all by hand. Netinfo may have an easier way, I'll do some more digging and post back.
Cheers.

Random error accessing CIFS shares from Windows

I am setting up some CIFS shares to be used from Windows clients and in the process I had some random problems accessing the shares.
In hope of finding the answer I checked the CIFS Service and the Active Directory Service, and while watching the screen for Active Directory Service I saw that the "Selected Domain Controller" changed from one to another. I now stayed within this screen and noticed that the "Selected Domain Controller" continued to change and then I found the problem, because an unknown Domain Controller appeared. The IP was 216.150.17.8
I found that when ever this Domain Controller was the selected one, all access to CIFS shares from Windows clients failed! This is correct, because the 216.150.17.8 of course is unaware of all users in Our Domain
So the Questions are:
- what is happening?
- and how to solve this?
- why is a Domain Controller 216.150.17.8 sometimes the Selected Controller?
- where does this 216.150.17.8 come from?
Have You seen anything like this?

I now have found out why the DC changes - it is because the CIFS service is restarting ;-(
This is a log snip
2009-5-14 09:24:53 Executing start method ("exec /usr/lib/smbsrv/smbd start").
2009-5-14 09:24:53 Executing stop method (:kill).
2009-5-14 09:24:53 Stopping because all processes in service exited.
2009-5-14 09:24:39 Method "start" exited with status 0.
2009-5-14 09:23:48 Executing start method ("exec /usr/lib/smbsrv/smbd start").
smbd: NetBIOS services started
2009-5-14 09:23:48 Executing stop method (:kill).
2009-5-14 09:23:48 Stopping because all processes in service exited.
2009-5-14 09:23:34 Method "start" exited with status 0.
It seems to happen when I access the share and thereby force a uservalidation
Any ideas?

Access to Samba\vfiler share via shortname

I wasn't sure which section to post this under as it occurs on different
operating Systems (Windows XP SP3, WIndows 7, Windows 8, Server 2003, Server
2008) and is random.
Basically, some of our end users experience problems accessing shares to a
vfiler for example with shortname \\example\share.
They can access this specific share via ip address or fqdn
\\example.domain.local\share. The
user can even access \\example and be
able to
view shares there but when clicking on the share it comes back with network
error or access denied.
This does not happen to all users at a time and on the same
workstations\servers and there are no specific times. On the end users
workstation DNS and wins is working, they have
no problems accessing other
vfilers or F&P Windows shares.
I tried all flushing DNS and wins cache, tried rebuilding CSC (Offline files)
to no avail. We don't have this enabled in our environment in any case
but
gave it a try.
One way I got it working via shortname is by adding a new security group to
the security permissions on the share. The group only had my account as a
member
and exsiting groups remained. After this the end user was able to map
via shortname.
I've tried many things and just can't figure this out or where to look. My
team doesn't manage the vfilers or samba shares so
can't look at the logs or
anything.
Another scenarion I have is for a Samba share, very similar situation but
this time its accessing the share on a Windows 2008 R2 server.
Basically
similar symptoms, can't access via shortname, get 'Network Error', tried several
things, even Windows Network Diagnostic
where it states that "The remote
device or resource won't accept the connection', "The device or resource (samba)
is not setup to accept connection
on port "The File and printer sharing
(SMB)". Port 139 is open, can access other shares on different storage devices
successfully.
What's weird is that after some time, An hour, 2 or 3 later functionality
returns without any changes. Obviously restarting the server resolved this
quicker.
There are no scheduled tasks or tasks running in the background,
Windows firewall is disabled, disabled AV etc.
I managed to get a log from this Samba device but not sure if its
related or not.
[root@samba] [09:30:52] /var/log/samba
# tail /var/adm/messages
Apr
3 08:33:06 samba adbindd[24524]: [ID 323999 auth.error] ERROR samba.adbindd2
Task exit with cims error: Error sending response: Broken pipe
Apr 3
09:10:07 samba adbindd[24524]: [ID 323999 auth.error] ERROR samba.adbindd2 Task
exit with cims error: Error sending response: Broken pipe
Only other thing I can think of is that is may have something to do with the
device, folder redirection, cache or something of that sort.
I'm stuck, anyone have any ideas. I would like to know what else to try if
the issue re-coccurs.
MCSE: 2003, MCITP: Enterprise Administrator, MCITP: Enterprise Messaging Administrator

Hi,
I installed KB 2194664 and haven't had the problem since.
http://support.microsoft.com/kb/2194664
If it happens again I will revisit.
Thanks.
MCSE: 2003, MCITP: Enterprise Administrator, MCITP: Enterprise Messaging Administrator

Mapped GID is changing while accessing CIFS share

Hi guys
We're seening a strange issue on our AD-bound macs that the mapped GIDs of files on a CIFS share are changing without any change on the filesystem.
First of all let me explain our setup:
1. All macs are joined to our active directory domain. The output of "dsconfigad -show" for the uid/gid mapping looks as follows:
<snip>
Advanced Options - Mappings
Mapping UID to attribute = not set
Mapping user GID to attribute = not set
Mapping group GID to attribute = not set
Generate Kerberos authority = Enabled
<snap>
2. Macs access a cifs share on a netapp filer.
3. Username and groupnames are mapped correctly. The output of "id rth" for my user looks as follows:
uid=1973125731(rth) gid=2108864217(OSAG\corp) groups=2108864217(OSAG\corp),....
Problem:
When I mount the netapp CIFS share and enter it, everything looks good:
<snip>
rth@mac-rth:~$ ls -l /Volumes/os/it
total 696
drwx------+ 1 rth OSAG\corp 16384 Nov 29 11:48 admin
drwx------+ 1 rth OSAG\corp 16384 Mar 29 2004 corphtmlstats
<snap>
However when I execute a second ls a few seconds later, it can't map the group anymore:
<snip>
rth@mac-rth:~$ ls -l /Volumes/os/it
total 696
drwx------+ 1 rth 2181038096 16384 Nov 29 11:48 admin
drwx------+ 1 rth 2181038096 16384 Mar 29 2004 corphtmlstats
<snap>
It seems that the mapping doesn't work anymore even tough nothing has changed in the meantime. The same behaviour can be seen on any folders on this share. With the first ls everything seems to be OK and with the 2nd execution the mapping is not correct anymore.
From time to time it happens, that the mapping is correct again for single files or folders for a short period of time.
Has anyone seen a similar behaviour so far?
Thanks for your help.
Cheers
Raphi

Sounds like an issue that has to do with JavaScript Origin policy. You'll have to use Domain Relaxing for this. Read all about it here:
http://help.sap.com/saphelp_nw04/helpdata/en/59/87b54064c2742ae10000000a155106/frameset.htm
here:
http://help.sap.com/saphelp_nw04/helpdata/en/5e/473d4124b08739e10000000a1550b0/frameset.htm
and here:
http://help.sap.com/saphelp_nw04/helpdata/en/cb/f8751d8c6b254dac189f4029c76112/frameset.htm

CIFS share authentication is slow

The problem I’m having is when accessing a CIFS share authentication is taking several minutes. The Mac OS is LION and I’m connecting via SMB to a share on NetApp storage using a local account on the NetApp. Are there any options I could change in LION that would speed up authentication?

Hi
I have similar issue. Ldap 5.1 crashes after upgrade from siteminder 4.61 to 5.5. But if i remove the certain indexes, it does not crash, but LDAP becomes very slow due to unindexed search.
If you get any solution..pls inform us too.
Thanks in advance
[email protected]
chennai

App that can access windows file sharing

Hello... I've got my Nokia 500 today, but i'm looking for an app that can access windows file sharing via wifi. I want to transfer my picture from cellphone to my computer via wifi..
Nokia 500 -> Wifi -> Computer (Windows File Sharing)...
Anyone please create an app for me

Telexy SymSMB used to be such an app, but was taken off the market (Nokia demanded it, because apparently some Nokia employees were involved in developing the app). Don't know if anything similar has come out since then.

Windows 2012 R2 - Access problems to NFS shares via IPv6

Hello,
we setup some NFS shares on HNAS storage box. The connection to this storage is only possible over IPv6 network.
My server with Windows 2012 R2 has the feature 'Client for NFS' installed and a 'showmount -e servername/or IPv6 address' works. I can see all shares when i try to open the storagebox in Windows Explorer with the command "\\servername" or "\\IPv6
address", too.
My problem is, when I try to mount the share via "Map network drive" or "mount \\servername\sharename *" I get Error 53 - Network path not found.
The share is configured that every server in the IPv6 subnet could access it and it works on Unix machines, but not on Windows.
It does not matter if i set some option parameters for the "mount" command like sec=sys or anon, everytime error 53.
I don't know, if the share needs special options for Windows. I hope somebody can help.
Kind regards

Hi,
here is the output of your 2 commands:
PS C:\Users\admin> get-SmbConnection
PS C:\Users\admin> get-SmbServerConfiguration
AnnounceServer                  : False
AsynchronousCredits             : 64
AutoShareServer                 : True
AutoShareWorkstation            : True
CachedOpenLimit                 : 0
AnnounceComment                 :
EnableDownlevelTimewarp         : False
EnableLeasing                   : True
EnableMultiChannel              : True
EnableStrictNameChecking        : True
AutoDisconnectTimeout           : 0
DurableHandleV2TimeoutInSeconds : 30
EnableAuthenticateUserSharing   : False
EnableForcedLogoff              : True
EnableOplocks                   : True
EnableSecuritySignature         : True
ServerHidden                    : True
IrpStackSize                    : 15
KeepAliveTime                   : 2
MaxChannelPerSession            : 32
MaxMpxCount                     : 50
MaxSessionPerConnection         : 16384
MaxThreadsPerQueue              : 20
MaxWorkItems                    : 1
NullSessionPipes                : HydraLsPipe
NullSessionShares               :
OplockBreakWait                 : 35
PendingClientTimeoutInSeconds   : 120
RequireSecuritySignature        : False
EnableSMB1Protocol              : True
EnableSMB2Protocol              : False
Smb2CreditsMax                  : 2048
Smb2CreditsMin                  : 128
SmbServerNameHardeningLevel     : 0
TreatHostAsStableStorage        : False
ValidateAliasNotCircular        : True
ValidateShareScope              : True
ValidateShareScopeNotAliased    : True
ValidateTargetName              : True
EncryptData                     : False
RejectUnencryptedAccess         : True
I try to access the file share with Windows Explorer. When I enter \\fe08--babe-face-cafe-dead.ipv6-literal.net (just example), I can see all shares on the storage box. When I double-click the share, I want to access, where an access is definitely allowed,
it takes a while and then the error "\\fe08--babe-face-cafe-dead.ipv6-literal.net\share is not accessable. You might not have permission to use this network resource. ..." appears. Of this action a recorded the trace.
Another way I tried is to open command line an type "mount \\fe08--babe-face-cafe-dead.ipv6-literal.net\share *". After this an error 53 occurs immediately without any wait time.

How to access Windows shares on Arch?

I would like to access my Windows Vista shares (on the same network) as any other folder in Arch. For instance, I have the "Public" folder shared on Windows and I was able to access this folder in Nautilus by navigating to smb://nazbtm/Public. This worked and pointed to the correct folder...
But I don't know how to navigate to that folder in a terminal (which I need).
How can I mount the "Public" shared folder to /home/nazgulled/public, for instance? And do it with every boot of course...

Nazgulled wrote:
This works:
mount -t cifs //192.168.1.100/Public /home/nazgulled/public
This doesn't:
mount -t cifs //vmhost/Public /home/nazgulled/public
To use the vmhost name instead of the IP address, make sure your /etc/hosts file contains the following line: (assuming the IP address is static. if it changes at every boot with DHCP, then this obviously ain't gonna work too well )
192.168.1.100 vmhost
And you mentioned that you would like to have this mounted at every boot, so instead of having to manually do a mount -t cifs //blah, blah blah every time, simply throw this in your fstab.
//192.168.1.100/Public /home/nazgulled/public cifs user=whatever,password=whatever,uid=whatever,users 0 0
And if you don't want to put your user and password in the fstab where others on the same computer can see them, use a reference to a credentials file:
//192.168.1.100/Public /home/nazgulled/public cifs credentials=/home/nazgulled/.smbcredentials,uid=whatever,users 0 0
Then, in the /home/nazgulled/.smbcredentials file have:
user=whatever
password=whatever
And if your home directory is mod 700, other people using the same computer won't be able to read your password file, but fstab during boot will.
And, a third option, and the way I do it since I don't necessarily want everything mounted at every boot is to mount only when you want, but without needing to type a long mount command, change the fstab line to:
//192.168.1.100/Public /home/nazgulled/public cifs credentials=/home/nazgulled/.smbcredentials,uid=whatever,user,noauto 0 0
Note the user (without the s) and the noauto, which means it won't automatically mount at boot, but has the information ready so that later, if you execute the command mount /home/nazgulled/public it will mount (without needing to be root). (Make sure you chown and chgrp that directory to you).
Hope that helps
Bob
Last edited by Hrod beraht (2009-03-28 22:34:07)

Cannot access windows shares with NTFS junction points

Hi,
I upgraded to Mavericks and now I cannot access Windows shared where the folders are access through NTFS junction points. (NTFS junction points are like symbolic links to files/folders).
Regular shares are working fine and these shares are working on Windows PC's. I also tried before and after on another Mac Mini I have, so is definitatley something to do with upgrading to Mavericks.
Thanks in advance
A.

This is related to Apple's new SMB2 implementation in Mavericks.
Instead of connecting to your Windows share via SMB, connect via CFIS. Note that I had to disconnect from Windows share, restart, and then reconnect with CFIS to get the NTFS junction points to work.
From ZDNet:
You can also try forcing Mavericks to use the older SMB variant, Common Internet File System (CIFS). To do this, simply edit your server connection URL so that it uses CIFS. Use the Finder to choose the "Go" menu and select "Connect to Server..." (or just use command-K) and type "cifs://YourServerName" and hit Return; the server should mount. If it doesn't, try entering the share's designation as well, e.g. "cifs://YourServerName/YourDriveName."
[BE SURE TO RESTART AFTER DISCONNECTING FROM SMB SHARES AND BEFORE THE CFIS CONNECT TO MAKE SURE ALL ACCESS THREADS CLOSE!]
https://discussions.apple.com/thread/5467191?start=0&tstart=0
http://www.zdnet.com/mavericks-smb2-problem-and-fixes-7000022519/
Kevin

Accessing Windows CIFS Shares via Nautilus

Similar Messages

Maybe you are looking for