Connection to windows DFS Shares

Can OS X 10.6 connect to a DFSR share and access files on a windows 2008 R2 server?
I see people using DAVE and ExtemeZ-IP for DFS but i also see people are able to connect with 10.6. Also if a user can't access the namespace dfs share, but could access the server dfs share directly that might be ok.
I figured you server guys would know more than the workstation forum browsers.
My goal is to have a physical win2k8r2 server in 2 office locations connected via VPN and be able to have users in both locations connect to a single share that is always in sync. DFSR seems to be the only good solution for this, but all the client machines are Mac's and we also have an Xserve in 1 location and an new mac mini as a OD replica in the other location.

g3sys,
How many Macs are you talking about? You are most likely going to need to buy a solution one way or the other, but the number of Macs that you need to support may be the determining factor.
Group Logic's ExtremeZ-IP server pricing is based on the number of Macs you are going to have connecting, and the DFS serving capability is an additional fee (based on Group Logic's pricing page).
Thursby's DAVE is a per-client cost, but includes DFS support built-in.
I usually recommend DAVE to my clients, since you don't have to change the Windows server, and DFS is built in, so it can be more cost effective. Group Logic may be better for hundreds or thousands of Macs, but I don't know what their pricing is in those cases.
Just my $.02

Similar Messages

Unable to Connect to Windows File Shares

Steps I take to attempt to connect to a Windows File Share within the office. Being relatively new to the Mac, I am curious on why I am not able to connect to Windows File Shares.
1. Command-K
2. Server Address: smb://[server-hostname]/[sharename]
3. Click Connect
4. Connecting To Server..... (takes a short amount of time)
5. SMB/CIFS File System Authentication
- I then enter the domain, username and password
6. Click OK
7. Error: Could not connect to the server because the name or password is not correct.
What gives? I have confirmed and validated server hostname, sharename, appropriate persmissions for windows account, etc. I have tried IP Address instead of hostname, same outcome.
Any Ideas?
MacBook Pro 17" Mac OS X (10.4.8)

Hi Arus, not really a Windows® expert, but I think I've seen were putting the Domain name in there fixed it, but I can't find the exact way to do it, this is the closest I could find...
"If I try to connect to smb://domain, that's when I can authenticate. If I try smb://machine/share, I still get the error -43."
http://discussions.apple.com/thread.jspa?messageID=4727809&#4727809

Connection to Windows Network Shares

After installing 10.5 I lost my automatic (Active Directory Domain mapping upon logon) and manual connection to some of our critical Windows network shares. All worked fine under 10.4. All connection attempts fail and report in a dialog:
Connection failed
There was an error connecting to the server. Check the server name or IP address and try again.
Manual connections then report in a dialog:
Connecting to Server
The Finder cannot complete the operation because some data in
"cifs://netstore2.colgate.edu/student6" could not be read or written.
(Error code -36)
Some of our servers connect fine but two of our most important servers do not. I haven't found a clear description of this in Apple support forums (but may have missed it in the flood of problems reported).
I have something that works for me based on something I read on the web (perhaps in one of the threads on http://www.macwindows.com/leopard.html but I can't find it now).
Our automatic mappings and my initial manual attempts use the FQDN (fully qualified domain name) for our server - netstore1.colgate.edu. Replacing this with netstore1 works! I have no idea why (Something to do with WINS? Apple engineers?) but I'm using it for myself and others.
That is:
cifs://netstore1.colgate.edu/employee2/dwheeler fails (as does smb://...)
while
cifs://netstore1/employee2/dwheeler works (as does smb://...)
I just duplicated this failure/success using mount_smbfs, where the failure looks like:
$ mount_smbfs //[email protected]/employee2/wheelerda ~/temp
mount_smbfs: server connection failed: Software caused connection abort
and
$ mount_smbfs //dwheeler@netstore1/employee2/wheelerda ~/temp
simply works.
Hopefully this will help someone while Apple fixes the problem (they can probably blame Microsoft, but remember that this all worked fine in 10.4).

Please make the following changes
On the Server whose map drives you don't see
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
Value: autodisconnect
Data type : REG_DWORD
Value: ffff (Hex)
On windows 7 client
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
Value Name: KeepConn
Value Type: REG_DWORD
Value: 65535 (dec value in seconds)

Connect to Windows Server shares

We have recently purchased two MacBook carts. I'm trying to connect to home directories on a Windows Server from Go/Connect to Server. When I enter the SMB path, I get "Failed to Mount Volume". I can see the root level share but not drill down any further. Don't know if this the correct forum but I figured I would start here.

For some reason I was able to connect by clicking Start->My Network Places->Add New Network Connection
I selected the second option to add by IP, put in \\xxx.xxx.xxx.xxx\share point it asked for a username and password then connected. Then when I went to another XP machine it let me go to Run //xxx.xxx.xxx.xxx and it asked for a username and password then showed my share points where I was able to right click and add them as network drives. It works now.
Cheers

10.3 using afp to connect to windows 2000 share

Here is my problem, I have two machines running 10.3 when I click on go - connect to server and enter my server that I want to connect to it tells me it could not connect to the server becuase the username or password is incorrect. What file do I need to delete to reset the password someone has saved?

You need to set up at least one shared folder on the Windows side. See the following for additional help:
http://docs.info.apple.com/article.html?artnum=151669
http://docs.info.apple.com/article.html?artnum=151667
http://joelshoemaker.com/computer/mac/macfilesharing.html

Unable to connect to DFS shares

I know it is a known issue in Windows 10, that it is not possible to connect to DFS shares. Can we expect any hotfix for this soon? Because to be able to test Windows 10 in a enterprise, it is essential to be able to connect to a DFS share (at least in
my case :) )

Hi Richard Diphoorn,
From the following news:
As with the last build, you’re getting hot-off-the-presses code which means there are a few issues. We’ll be publishing WU updates shortly to fix the first two, but the remainder will not be fixed for 9879.
•In some cases you may get a black screen when trying to log-in or unlock. The only option is to hold the power button to hard reboot.
•You will be unable to connect to Distributed File System network locations.
•Some systems may see disk growth of 20GB+ due to driver install duplication. On systems with low disk space this can block setup and cause a rollback to the previous build.
•Skype calls will disconnect and Music will stop playing if those apps are minimized.
•There are several known issues with screen sharing with Lync.
There should be newly update released to fix this issue. You can try the newest update which released in 11.24:
https://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB3019269
Alex Zhao
TechNet Community Support

Stand-alone DFS Share - Folder targets - wrong credentials

Hi all
I am currently setting up a stand-alone DFS root with some Folder targets on different servers.
All server are Windows 2012 R2 with all available patches.
I use the stand-alone DFS because many users will access it with non domain computers.
I changed the DFS to FQDN and i can reach it without any problems. But as soon as i click to a folder target i get the message that i use the wrong logon name or password.
On the server that host this folder target i can see that the client want to logon with the local username and credentials. What of course does not work.
What must i do, that the client use the same credentials for connecting to the folder target server as connecting to the DFS share? And it must be done on the server side because i have no control over the clients. Must i do a credential delegation between
the DFS Share Server and the folder target server?
Thanks for any hint
JBAB

Hi,
If they are accessing the shares using NetBIOS name from non-domain workstation, it will use the logged on account. If you access the stand-alone DFS share by using FQDN from non-domain workstation, it will prompt for credentials and should use the domain’s
credentials.
For more detailed information, please refer to the thread below:
DFS share across Domains will not Authenticate properly with non-domain workstation
http://social.technet.microsoft.com/Forums/windowsserver/en-US/6dc26639-740a-4148-aa48-673e9732242b/dfs-share-across-domains-will-not-authenticate-properly-with-nondomain-workstation?forum=winserverDS
Best Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows File Share configuration from AIX Portal

Hi,
we want to connect a Windows file share as KM Repository to a portal running on AIX.
The network path is configured using jCIFS and user (DOMAIN.NET\USERNAME) is entered with password. The corresponding path is also entered in the FS Repository manager using ACLSecurity manager. A Windows System is not configured .
In the repository managers monitoring view our new repository manager shows a green button. In the KM however, it is not visible. The portal log shows the following error:
"Cannot retrieve credentials from URL for file 'DOMAIN.NET; USERNAME/' "
We tried to connect the file share with the same user/password. This worked fine.
Is there something else to configure ?
Any help will be appreciated.
Thanks
Marcus

Hi,
the problem was the passwort. Using "?, %" or other special characters interpreted in a URL may not be used.
After changing password to a alphanumeric everything works just fine.

Why is my Mac pro slow to Open folders in a Windows SMB share?

Why is my Mac pro slow to Open folders in a Windows SMB share? We use a Windows Server for graphics storage and I can open the share just fine, but when I attempt to open folders within that share it takes sometimes as long at 15 minutes to display the contents of the folders. This happend before and I switched to the other NIC port, but now it is doing it in both. I can open other connections to Windows SMB shares with no problem.

Why is my Mac pro slow to Open folders in a Windows SMB share? We use a Windows Server for graphics storage and I can open the share just fine, but when I attempt to open folders within that share it takes sometimes as long at 15 minutes to display the contents of the folders. This happend before and I switched to the other NIC port, but now it is doing it in both. I can open other connections to Windows SMB shares with no problem.

Connection to the deployment share could not be made (DFS share, works fine on site A, not on Site B)

I'm trying to isolate this problem with MDT..., unable to find a solution matching this error.
We have two sites, with a DFS replica between the servers, which works fine.
Server A: Windows 2012 R2 standard
Windows Automated Installation Kit for Windows 7
MDT 2012, Update 1
WDS configured for PXE boot
Distributed File Share
Server B: Windows 2008 R2 Standard
MDT 2012, Update 1
WDS configured for PXE boot
Distributed File Share
The local path on both servers is on E:\DFS-Deploymentshare
The DFS path is \\domain.com\it\deploymentshare
When deploying on Site A, the deployment run smooth without problems.
When deploying on Site B, the deployment fails to create connection to the share.
A connection to the deployment share (\\domain.com\it\deploymentshare) could not be made.
Connection OK. Possible cause: invalid credentials.
Pressing F8, to reach a command prompt. "ipconfig" shows an IP-address. I can PING the deployment server. I can mount the Deployment share using "net use" and providing the username/password added in the bootstrap.ini and "retry"
in the message box and the deployment continues.
In the BDD log i get this timeout:
<![LOG[Unable to connect to \\domain.com\it\deplomentshare. Sleeping for 5 seconds.
<![LOG[<Message containinng password has been suppressed>
<![LOG[Access is denied.
However everything is the same both in site A and B so this seems very strange!
The complete system has worked this way before.
Bootstrap.ini contains:
DeployRoot=\\domain.com\it\deploymentshare
UserDomain="domain"
UserID="mdt-account"
UserPassword="password"
I've been trying all I can think of, but Im still faced with this error and to keep in mind the same share working on another site.

Ok, so by the sounds of it, there is something wrong with the share permissions (especially if your account works fine but the MDTserviceaccount does not work even when part of Domain Admins).
So you need to do the following:
Start in Site A:
Boot into WinPE on a workstation in site A
Ping server-a
Ping server-b
Run "net use * \\server-a\deploymentshare$ /user:DOMAIN\MDTserviceaccount"
Type in the password for MDTserviceaccount when prompted
Browse to the newly mapped drive and list the files/folders
Make sure you can see the relevant MDT folders, like Applications, Out-of-Box Drivers, etc
If all that works, then you can move to site B
Start in Site B:
Boot into WinPE on a workstation in site B
Ping server-a
Ping server-b
Run "net use * \\server-b\deploymentshare$ /user:DOMAIN\MDTserviceaccount"
Type in the password for MDTserviceaccount when prompted
Browse to the newly mapped drive and list the files/folders
Make sure you can see the relevant MDT folders, like Applications, Out-of-Box Drivers, etc
By going through all of the above, you should be able to see where the problem lies.
If all of the above works with no problems, then you have the details incorrectly specified in the BootStrap.ini (or possibly CustomSettings.ini). Confirm that you have the following specified in the relevant ini file:
DeployRoot
UserID
UserDomain
UserPassword
You can have a look in the help file if you need to confirm that these properties are configured correctly. Look under
Toolkit Reference - Properties - Property Definition in the help file.
Both Site A and Site B is successfully
I have changed the Password of deployuser to test if it is correct. and i have copy/pasted the password into the DC when changing the password.
I have tested the password by logging on to a client-pc with the deployuser as username and the temp password "Pa$$w0rd" successfully.
Both UserID, UserDomain and UserPassword is entered after the help file for Property Definition.
Please see the Bootstrap.ini and Customsettings.ini (NB! Servernames, Domainname and Passwords are fictive.)
http://1drv.ms/1tGDlUt

Cant access a DFS share from a Windows 7 computer

I am having DFS share access issues with a Windows 7 workstation.
My setup is I have 6 windows 7 stations accessing this DFS Share.
All computers have the same Administrator password and another User/Password
All but 1 are working as they should.
The DFS share is running under Server 2008 R2 and contains files from this and another server.
From the workstation, I can see the server under Network.
I can open it and see the individually shared volumes and I have full read/write permissions.
I can see the DFS share and I can map it.
If I try to open the shared volumes within the DFS file I get a message saying I dont have permission.
Interestingly, when I look at the properties of the DFS share form the workstation, I dont see a DFS tab.
If I do this from a workstation is is able to connect fully to the share, I see a DFS tab in the properties.
I tried to include everything,
Thanks in advance

Hi,
Please try hotfix in the following KB,and check the result.
You cannot access a DFS share through a mapped network drive on a computer that is running Windows 7 or Windows Server 2008 R2
http://support.microsoft.com/kb/983620/en-us
Some steps for troubleshooting DFS you can try
http://technet.microsoft.com/en-us/library/cc962144.aspx
How to troubleshoot Distributed File System Namespace access failures in Windows
http://support.microsoft.com/kb/975440/en-us
use command dfsutil /pktinfo to test the access to the DFS root and connectivity to the root shares
http://blogs.technet.com/b/askds/archive/2009/06/04/the-case-of-the-random-dfs-access-denial.aspx
Regarding to the missing dfs tab, there's a policy, locate to User Configuration\Administrative Templates\Windows Components\Windows Explorer\remove dfs tab, then users can not view or change the properties of the dfs shares
Yolanda Zhu
TechNet Community Support

Can't connect to DFS shares from machines not part of the domain

I'm not sure if this is by design, but we can't connect to DFS shares from machines that are not joined to the domain. We can't even map a drive using credentials of a domain account.
Is that how DFS is supposed to work?

Hi RJO22,
I did some research on this topic, and got a conclusion:
Clients that belong to a workgroup can only access the DFS namespace if the name resolution mechanism that is in place can locally resolve the domain name
https://social.technet.microsoft.com/Forums/windowsserver/en-US/c3214a4c-8088-446c-ba4d-643d5baf87cc/how-to-access-dfs-namespace-from-a-standalone-windows-2003-server
Regards,
Alex Zhao
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Error message when mapping to a network drive of a DFS share on Windows 7

Hi,
We are getting the following error when mapping to a network drive of a DFS share on Windows 7:
“The mapped network drive could not be created because the following error has occurred:
A specified logon session does not exist. It may already have been terminated."
In our case, the user logs on his workstation using his regular domain account, then maps to the network DFS share using the service account of an application.
There is a fix from Microsoft (MS KB968264). But this fix requires disabling the "Network access: Do not allow storage of credentials or .NET Passports for network authentication” property. This is against the Microsoft own best practices (Network access:
“Do not allow storage of passwords and credentials for network authentication” should be set to
ENABLED), and is NOT acceptable for us for obvious security reasons.
Question: Does anyone know an alternative fix to this issue that does not introduce security risks?
Thank you in advance!
Mdjona

Again I have tried this, but in my program if I try to save to the a drive when no disk is inserted, the JOptionPane i want to display is not coming up.
the system prints out
java.io.FileNotFoundException: A:\image.jpg <The device is not ready>
If that makes any sense to you

Since upgrading to Mac OS 10.6.8 I can't connect to a smb share on Windows Server 2003r2

Hi recently i upgraded from Mac OS 10.5.8 to Mac OS 10.6.8 on a 2.66 GHz Dual-Core Intel Xeon Mac Pro 1,1.
Prior to upgrading to 10.6.8 i had a viable connection to a Windows Server 2003r2 which hosts Pre-press client and all out work files as well as client applications. Now I can not connect to the server. I can ping the server. I can connect to another SMB share on different Windows Server 2003r2 that is our secondary server, but i can not connect to the primary. The Client software is associated with data base tracking the data.
This share does not show up in my volumes but I have a Max Host File with the share defined.
Can anyone come up with a solution to this. I have contacted my support for the Server 2003r2 Client software but they don't have a solution beyond clean installing the computer.

Hi recently i upgraded from Mac OS 10.5.8 to Mac OS 10.6.8 on a 2.66 GHz Dual-Core Intel Xeon Mac Pro 1,1.
Prior to upgrading to 10.6.8 i had a viable connection to a Windows Server 2003r2 which hosts Pre-press client and all out work files as well as client applications. Now I can not connect to the server. I can ping the server. I can connect to another SMB share on different Windows Server 2003r2 that is our secondary server, but i can not connect to the primary. The Client software is associated with data base tracking the data.
This share does not show up in my volumes but I have a Max Host File with the share defined.
Can anyone come up with a solution to this. I have contacted my support for the Server 2003r2 Client software but they don't have a solution beyond clean installing the computer.

Why do I get "Unknown user name or bad password" on Windows 7 when trying to connect to an SMB share on my Mac?

Before installing the update to 10.7.3 I could connect to an SMB share on my Mac from Windows 7 but I can't any longer. When I try I get the error "Unknown user name or bad password" on the Windows 7 system.
When I try to connect using the "net use..." command I get the error: "System error 86 has occurred".
Does anyone know how to resolve this? What really confuses me is that it was working fine until I installed the update to 10.7.3.

Check the Wins Tab in the Advanced section of Network in system preferences.
If you don't have the same workgroup name and the correct NetBIOS name showing up in the WINS tab you will get the Bad username or password.
I know I deal with this everyday.
There is something wrong with Lion and it does not automatically fill in those entries in the WINS tab.
What I have to do on every reboot/startup is open System preferences go to Sharing and uncheck File Sharing then recheck it. That will fill in the WINS tab entries.

Connection to windows DFS Shares

Similar Messages

Maybe you are looking for