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?

Similar Messages

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.

How to access ZFS share from Windows 7?

I am new to UNIX and am having a hard time to get a ZFS share to access from windows 7 on my home network.
I was able to access both WHS 2011 and QNAP 459 share on SE 11 by using the file manager - Server - windows & then just using the IP address, username, password. That was easy or at least similar to what I was used with windows 7.
However, I have yet to be able to access a ZFS pool containing a share that I can access from another windows 7 machine at home.
Apparently, I can mount the share from windows but the login name/password do not get accepted when I add a network connection in windows. Windows does seem to find the path \\solaris\tank_share1 and even mounts it, but the login for SE 11 does not work for some reason.
I changes the workgroup name to WORKGROUP in windows but that did not change anything. I tried to edit the pam.conf file by changing the ownership from root to myself so I could use gedit since it has been 15 years since I last used vi. However, that corrupted the setup as I got "system error" message on reboot that never got out of that infinite loop.
I am basically using the instruction through the following link:
http://blogs.oracle.com/observatory/entry/accessing_opensolaris_shares_from_windows
Any help to get this problem resolved is much appreciated
Thanks,
Kurt

The documented procedure of having to edit the pam_conf file seems to work followed by resetting one's password seems to work after all. I believe, by taking away ownership from root to "admin user" screwed things up. I had to relearn how to use vi but that didn't take very long.
Got about 50 MB/s speed coping from Windows SSD to SE11 SSD via very small (5 GB) RAIDZ array in VMWare (running on top of WIN 7-64). I have to try native SE11 SSD next as the VMWare setup is just for practice.
Q: Is there a way to launch gedit from the terminal window in root mode so I wouldn't have to use vi?
Kurt

Cannot access SMB shares from Windows boxes in AD domain

Hey folks
I've needed to tackel this for sometime, but Santa is bringing me a dual core G5 and the urgency just increased.
I have an Active Directory domain and all of my macs are successfully joined and get Kerberos tickets upon login. I can access any shares I need from OS X -> windows but NOT the other way around.
I did finally noticed that only local user accounts seem to appear in the accounts list in the sharing pref pane. So I have figured out that I can access any users folder with that one account- OUCH! What I need is access control based on the user.
For instance if I want to share ~jdoe and jdoe is a mobile account and an AD user then if I am logged into windows as [email protected] then I should be able to access the share on the mac. Conversly I should not be able to access ~jdoe with the mac's local admin account and pass.
Do I need to change my smb.conf to reflect AD and if so, where/what?
Also, do I need to map UIDs to anything? And, is that a security risk?
Thanks!
-N

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.

Can't access Network share from Windows 8 computer

I have a clean install of Windows 8 x64 running in a workgroup environment. I can access multiple computer/NAS shares except one share off a partifular NAS. This share is accessible from other computers and the other shares on the NAS are accessible from
this Windows 8 computer. I have cheked the credentials and they are fine, added them under the credential manager, tried to map a drive and selected use other credentials etc but it continually says "Windows cannot access \\ComputerName\ShareName"
you do not have permission. I have permission and nothing is wrong with the permissions or the server. This is driving me crazy if anyone could help it would be greatly appreciated.
I have tried:
1. Mapping drive with ip address e.g. \\ip address\sharename
2. disabled ipv6, made sure netbios enabled, made sure client for ms networks enabled.
3. Setup a new account on server, doesn't work either.
4. All sharing options enabled. I even modified the permissions on the share for "everyone" full access and it still didn't work.
Has to be something with this windows 8 machine.

Dear all,
Hi am using 2012 r2 server and i have created share folder ,and added the user Id in that share folder but while accessing in windows pc (local admin) its opning all share folder , but its not asking password if i click in share folder it shows you do not have
permission to access . but till lastweek it was worked fine . and if i tried in administrator login its asking password authentication. Please help me ASAp.
Thanks
mahamad
8884209555

Unable to access CIFS shares using SSL Web portal

Hello,
i have deployed Cisco Clientless Web VPN on my ASA5515.
I'm having an issue when I try to browse a file server (access CIFS shares) from the WEB VPN portal. I am prompted for login, and after logging in I get the "Error contacting host" immediately. it's seem like a bug on ASA ? i saw that on Cisco Web site : bug CSCsl94183
I already DONE those things :
1- reload the ASA
2- upgrade to the latest software release
3- test different web browser ( Firefox, IE, Chrome)
1- ASA Platform is 5515 running latest software release (9.1.4)
2- File server running Windows 2008 R2
3- Clients is using Firefox.
4- When I establish SSL VPN connection using Cisco AnyConnect I have no problems accessing files or folders on the same server.
NOTE : I have 2 other CIFS server running Window 2003 and there is no issue. the issue is happening ONLY with the server running Window 2008 R2

I've also seen this exact problem. We have several Windows 2008 R2 servers, one of our Domain controllers has been migrated to 2008 R2. I can access shares on the Windows 2008 R2 domain controller, but not a deicated (member) file share server.

I can't access folder share in WIndows Server 2012 R2 from windows 8.1

i have a strange case:
I have a Windows Server 2012 R2 machine with a shared folder. Accessing this folder using a Win7, Win8,
Win 2008 R2 machine using \\servername works fine but form windows 8.1 or windows
2012 r2 i can't so any one can help me.

Hi,
Would you please let me know the complete error message that you can find, when can’t access to the share folder
that host in the Windows Server 2012 R2?
If you logon the Windows 8.1 (or server 2012 r2) with administrator account, will encounter the same issue?
Meanwhile, please access the share folder via \\server’s IP address\share folder. Then please check if this issue still persists.
In addition, there is a similar thread. Please refer to and check if can help you.
Can't
access UNC share on Windows Server 2012 R2
Hope this helps.
Best regards,
Justin Gu

Can't add CIFS Share from iManager on OES

I recently install OES and have not been able to add a CIFS share from
iManager .
The error is:
Error: The given volume name could not be found on the specified server.
I've tried entering the path is various ways:
\vol1\share\
\vol1\share
vol1\share\
vol1\share
vol1:\share\
I've recreated the Pool and now have the volume name "VOLUME1" but still no
success.
Logger Screen reports:
GadgetManager......2796 Could not find resource file mapping for stylesheet:
NSSMgmt.xsl
GadgetManager......2796 Could not find resource file mapping for stylesheet:
NSSMgmt.xsl
Trying NCP protocol
Any suggestions?
Thank you.
Marc

The source of the CIFS issue is the cluster snapin.
The CIFS functionally is included in the cluster snapin for cluster
services version 1.6 (NetWare 6.0) and 1.7 (NetWare 6.5).
Unfortunately, with Cluster Services 1.8 (OES and NetWare 6.5 SP3),
Novell dropped the CIFS functionality from the cluster snapin. So when
you install an OES/NetWare server, or when you install SP3 to an
existing Server, you will loose the CIFS snapin.
Note that reinstalling SP3 will not bring you back the CIFS
functionality as it is actually the cause of the disappearence.
To get back the CIFS functionality, you have to get the NCS 1.7 cluster
snapins. The latest version of these snapins can be found in NW65SP2 in
the file NCS.ZIP. Unpack these file somewhere and use the files NCS.JAR
and NCSRES.JAR from this ZIP file to replace the corresponding files of
your ConsoleOne installation.
Marcel Cox
http://support.novell.com/forums

Accessing file shares from JSP

Hi,
I need to be able to access file shares from a JSP page. Here's the JSP code:
<%@ page language="java" %>
<%@ page import="java.io.*" %>
<%@ page errorPage="errorPage.jsp" %>
<%
String fileSystemPath = "\\\\130.26.1.199\\MeetingManager30\\test.txt";
File f = new File(fileSystemPath);
f.createNewFile();
%>The above code resides in a server with IP 130.9.68.6 and is deployed onto the Tomcat on the server.
When I tried to run the above code, I got this error
java.io.IOException: Access is denied at java.io.WinNTFileSystem.createFileExclusively(Native Method) at java.io.File.createNewFile(File.java:827) at org.apache.jsp.test_jsp._jspService
(test_jsp.java:55) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service
(JspServletWrapper.java:210) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2422) at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171) at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:163)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke
(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:199) at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:833) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processCon
nection(Http11Protocol.java:711) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:584) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
(ThreadPool.java:687) at java.lang.Thread.run(Thread.java:536) Seems like I'm having a system level security setting problem here.
I know it's a security issue, because I've encountered the equivalent problem in ASP/IIS, and I had to give a domain user rights to both the IIS Virtual Directory, and the file share to be able to access.
Any ideas how to set up Tomcat to be able to access the file share successfully?
Thanks in advance!

Hello Veer,
From what you have posted it looks like while logging your error another problem occurred. Did you get any output from your System.out calls? If not can you try adding a few in order to home in the problem area.
Hussein Badakhchani
www.orbism.com

Moving files on share from Windows results in permission loss

Here's the setup:
-- Leopard, with shared SMB folders; specific user and everyone have read/write permissions for the share
-- Windows machine is accessing the share via the specific user & password, connecting fine
When I access the share from the Windows machine, and move files between folders, the file loses all permissions (they are set to 0000) so it cannot be read by anyone at all. The only way of getting access to them again (from either machine) is to chmod them back to 0644.
Copying files is OK, as is creating files and moving a folder from Win -> Mac. It only affects moving files between folders on the Mac.
Can anyone else confirm this, or is it a setup issue here?

10.5.1 has not helped the situation. Any ideas???

Issues accessing domain share from domain controller

Hi,
About 2 weeks ago, 2 of my domain controllers at one of our facilities has lost access to a domain share. If I try to access the share from the dc's, it prompts for a username/password. Now if I go to my workstation at corp, the share works fine. I can't
seem to figure out where the problem is. Any suggestions?
Thanks in advance!

You can use dcdiag and repadmin to check your DCs and your replication health status. That should let you see if something is wrong.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

Canon MF4320d, share from Windows XP Prof

Is it possible to get work a printer share from Windows XP professional with Canon i-SENSYS MD4320d (USB-printer)?
I've installed the printer to my Windows computer. All of my computers are connected to a AirPort which share's my internet. Of course windows laptop finds the printer very easy, but Mac OS X does not..
Sharing a windows USB-printer is a bit tricky with Mac OS, is there a way to get share work with this printer?

Hi there,
Looking at the Canon UK web site, it shows this model uses the Canon UFR2 driver on OS X. This driver does not work at all on OS X when it is connected to a Windows share.
You mentioned that you had Airport. You may find the MF works better when connected to the USB port of the AE. Although I have experienced problems previously with a mates MF4150 that was connected via an Airport Extreme. It used an earlier version of the UFR2 driver and it never recognised the MF when connected to the AE's USB port.
If you can connect the printer to your Mac and then share it to the PC, then this may be a better solution for you.
PaHu

About the error: "The account is not authorized to login from this station" when you access NAS devices from Windows 10 Technical Preview (build 9926)

Scenario:
With the release of Windows 10 Technical Preview (build 9926), some users may encounter an error message of “The account is not authorized to login from this station” when trying to access remote files saved in NAS storage. In
addition, the following error log may also be found via Event Viewer:
Rejected an insecure guest logon.
This event indicates that the server attempted to log the user on as an unauthenticated guest but was denied by the client. Guest logons do not support standard security features such as signing and encryption. As a result,
guest logons are vulnerable to man-in-the-middle attacks that can expose sensitive data on the network. Windows disables insecure guest logons by default. Microsoft does not recommend enabling insecure guest logons.
Background:
The error message is due to a change we made in Windows 10 Technical Preview (build 9926) which is related to security and remote file access that may affect you.
Previously, remote file access includes a way of connecting to a file server without a username and password, which was termed as “guest access”.
With guest access authentication, the user does not need to send a user name or password.
The security change is intended to address a weakness when using guest access. While the server may be fine not distinguishing among clients for files (and, you can imagine in the home scenario that it doesn’t
matter to you which of your family members is looking at the shared folder of pictures from your last vacation), this can actually put you at risk elsewhere. Without an account and password, the client doesn’t end up with a secure connection to the server.
A malicious server can put itself in the middle (also known as the Man-In-The-Middle attack), and trick the client into sending files or accepting malicious data. This is not necessarily a big concern in your home, but can be an issue when you take your
laptop to your local coffee shop and someone there is lurking, ready to compromise your automatic connections to a server that you can’t verify. Or when your child goes back to the dorm at the university. The change we made removes the ability to connect
to NAS devices with guest access, but the error message which is shown in build 9926 does not clearly explain what happened. We are working on a better experience for the final product which will help people who are in this situation.
As a Windows Insider you’re seeing our work in progress; we’re sorry for any inconvenience it may have caused.
Suggestion:
You may see some workarounds (eg. making a registry change restores your ability to connect with guest access).
We do NOT recommend making that change as it leaves you vulnerable to the kinds of attacks this change was meant to protect you from.
The recommended solution is to add an explicit account and password on your NAS device, and use that for the connections. It is a one-time inconvenience,
but the long term benefits are worthwhile. If you are having trouble configuring your system, send us your feedback via the Feedback App and post your information here so we can document additional affected scenarios.
Alex Zhao
TechNet Community Support

Hi RPMM,
Homegroup works great in Windows 10 Technical Preview (9926 build), when I invited my Windows 10 Technical Preview (9926 build) joined in HomeGroup, I can access the shares smoothly:
My shares settings is like this:
Alex Zhao
TechNet Community Support

No access on podcast share from Windows clients

Hello together!
I have the following scenatio at home:
* 1 Server with Windows 2008 R2 with logged in user and iTunes running (everything is shared)
* 1 Laptop with Windows 7 x64 & iTunes
* 1 Desktop with Windows 7 x86 & iTunes
* 1 Macbook with Mac OS X Leopard & iTunes
With this constellation I want to have access to my iTunes library located on the server from all other computer. With the MacBook this funktions without any problem to access everything (podcasts too).
On both Windows computer the directory pocasts is invisible. I can find the podcast files in the main directory but they are grey and the the playback does not start.
Is here anyone who had already the same problem and perhaps solved it? Thank you in advance for your replies.
P.S. Generally I can play the files by changing the kind of media to movie.
Message was edited by: Mattn81

Oleg,
I had the exact same problem here - we have two XSERVE machines here running OSX 10.5.7 server, and we're accessing a samba share on these servers from Windows XP SP3 clients.
When moving a file, I noticed a message in /var/log/samba/log.smbd :
[2009/06/15 12:45:30, 0, pid=50709] /SourceCache/samba/samba-187.8/samba/source/modules/vfsdarwin_acls.c:fsp_setacl(126)
darwinacl: failed to set ACL on <filename>: Invalid argument
!#acl 1
I tried to look this up on google, but had no success.
Searching the file /etc/smb.conf for "acl" showed the following line:
vfs objects = darwinacl,darwin_streams
(Un)commenting this line (inserting a ";" in front of the first character) and restarting s,b solved the problem here - I'm now able to move files without having the permissions set to 0000, and the error in log.smbd doesn't appear any more.

Accessing Mac File Share from Windows Server 2003

I currently have a windows domain that has a few Mac OS x leopard servers on it. I can map a drive to the Mac share using windows XP and Windows Vista, but I cannot map the drive in Windows Server 2003. I have enabled the Windows Sharing on the Mac server, and enabled the Mac File Sharing on the Windows server, but the windows server does not find the Mac server. I can ping the Mac server by FQDN and IP, but when I go to map a drive to it I get the error:
The mapped network drive could not be created because the following error has occurred: An unexpected network error occurred.
I have also checked the Local Security Policies, and did not find anything that would cause the issue. Any ideas anyone?
Message was edited by: GovHelper
Message was edited by: GovHelper

Does anyone else have any ideas? I checked again today and receive "The specified network name is no longer available" and after a few more attempts "An unexpected network error occurred"

Random error accessing CIFS shares from Windows

Similar Messages

Maybe you are looking for