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

Similar Messages

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]

Unable to connect to Deployment share via the 2012 Update 1 workbench.

Hi Everyone,
This is a tricky one, I've been scratching my head for a few days now. I have a MDT deployment share, which lives on a server, for argument sake, lets call it: MDT-01. Via the Servers MDT Workbench, I can connect to the deployment share just fine, from
any PC, other than my main PC (which is running Windows 8.1), I can connect to the deployment share just fine. If I load the MDT Workbench on my main PC, it just has a deployment share folder with a red cross on it. If I attempt to remove it, it crashes the
MMC, if I try and open the same deployment share it crashes the MMC. If I give the Deployment Share a different share name, it errors and says I can't use an existing deployment share folder.
I used to be able to connect to the share just fine, but since the last couple of days I've not been able to connect.
Further investigation with PowerShell reveals that the console thinks it has a persistent drive, DS001, but the path is blank, as in ''.
Restore-MDTPersistentDrive -verboseVERBOSE: Restoring drive 'DS001' with path ''WARNING: Unable to restore drive DS001.
If I try to remove the Persistent drive, it errors, and if I try to add any new drive to either the same deployment share, or an alternative, it fails.
I can use the New-PSDrive and Remove-PSDrive Powershell commands to create/remove a replicated drive, but that doesn't actually change the Path value in the Get/Restore-MDTPersistantDrive, as they seem to be separate, even though I think they should
be linked.
The Internet has been no help, so I'm asking the Microsoft crew to be helpful, and not just do the usual "This is posted in the wrong place, this question will now be closed... etc, etc!" This is an MDT question, not a Powershell question, I just
need anyone who has indepth MDT knowledge to look at this.
To make clear, this is not a question about a client connecting to the deployment share, that all works fine, and I can update the deployment share fine from any other workbench.
I cannot connect to my deployment share, from my local MMC MDT workbench, as it thinks it already has one, but with a blank path. I've uninstalled, and reinstalled both the MDT, and ADK components on my Local PC, but I still cannot connect to the Share.
My question is this: The files/registry that stores this DS001 path setting is clearly local to my PC, but where is it, I've search the reg, and I've check files, but to no avail, I'm likely to rebuild my PC because of this, but I'd rather not if I can help
it.
Any Ideas people?
P.s. Sorry if this post seems rude, I do appreciate the help, I just don't have time for being messed about, as we're migrating our XP system to 7, and with less than 60 days remaininf, I could do without this... Thanks for understanding. :D

Persistent drives are just a easy way for the MDT console to keep track of the Deployment Shares you like the most (think of it as "pinning" Deployment Shares to the console).
The list of persisted Deployment Shares are per user and stored in the file:
"%AppData%\Microsoft\Microsoft Deployment Toolkit\User.Config"
Mine looks like:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<userSettings>
<MDTProvider>
<setting name="Drive1Name" serializeAs="String">
<value>DS001</value>
</setting>
<setting name="Drive1Path" serializeAs="String">
<value>C:\DeploymentShare</value>
</setting>
<setting name="Drive1Description" serializeAs="String">
<value>MDT Deployment Share</value>
</setting>
</MDTProvider>
</userSettings>
</configuration>
Make sure the Drive Path points to something valid, otherwise, I would delete (rename) the file and let MDT re-create the file.
I hope this answers your question.
Keith Garner - keithga.wordpress.com

Unable to connect to file shares on xserve running 10.3.9

I just inherited a client that is running two xserves running 10.3.9. The servers are running workgroup manager/open directory. One server was out of commision due to a hardware issue. Users are divided equally on the two servers. The servers are only running OD and file sharing.
Any users who have their home directories on server A are able to connect to AFP shares fine. Any users who have their home directories on server B cannot connect to the AFP shares. When I look in the Server Admin program it does not have AFP even listed. And if I run disk repair utilities it says "AFP/appletalk listener not enabled because appletalk is off".
How do I turn this on if it is not listed as a check box?

Firefox 4 requires at least OS X 10.5 and an Intel Mac. There is a third party version of Firefox 4 that runs on OS X 10.4/10.5 and PPC Macs, for details see http://www.floodgap.com/software/tenfourfox
If you prefer, you can get the latest version of Firefox 3.6 from http://www.mozilla.com/en-US/firefox/all-older.html
Mozilla are working to prevent Mac users with non-compatible systems from getting the notification about Firefox 4, and also not displaying the "Download Firefox 4" button on http://www.mozilla.com

Unable to connect to Windows share

I had this problem before, I have no idea how I fixed it. I cannot connect to my Windows machine via Finder any more. I hooked a printer up to that machine, shared it, decided to add a guest account for others to access it. And bam, can't connect to the Windows machines via OS X.
I've ran the network setup wiz on the machine and made sure file sharing was on. I disabled the firewall. I can connect to the machine perfectly fine via a Linux box and another Windows machine.
Finder sees the server in the server list. Clicking on it just has Finder connecting indefinitely.
Finder->Connect to Server hangs for a bit and then returns:
There was an error connecting to the server “192.168.1.156”. Check the server name or IP address, and then try again.
Mounting via the command line fails:
mount -t smbfs //[email protected]/shows shows
mount_smbfs: mount error: /Users/Giblet/Movies/shows: Broken pipe
But smbclient works and lists information just fine.
smbclient -U giblet -W workgroup -L 192.168.1.156

Yup! Thanks. But ya know what.. I'm so used to not rebooting my Macs.. Reboot fixed it. Now to figure out how to get the printer work.

Cannot access local DFS shares while VPN is active

Hi
We use Windows Server 2008 Standard as a domain controller. It also hosts DFS. Although the namespaces are hosted on the server, the data is stored on a Windows 2008 Storage Server. We do not use DFS replication.
I have several DFS shares mapped on my Windows 7 client, which has just replaced my XP client, and can access them without any problems.
However, as soon as I connect to a remote network (located on a different domain - it has nothing to do with our network at all), I am unable to access our DFS shares. If I try to access a DFS share an error message pops up stating:
Location is not available
Logon failure: unknown user name or bad password.
The first time I connected the VPN a network dialog popped up asking what type of network it was and I chose Work. After connecting via the VPN I use remote desktop to carry out daily maintenance on a server on the remote network.
Other local resources are available. I can ping machines via IP, name and FQDN. I can access the same DFS shares using UNC paths. So, although I receive the error message described above when accessing AD-name.local-backslash-share-name1 I have no trouble
accessing server-name-backslash-share-name1
As soon as I close the VPN connection normal functionality is restored and I can again access the DFS shares without any problems.
Can someone help me fix this, please? When this was setup on my XP machine I never experienced this problem.
Also, is there a way of typing LAN addresses without the forum software converting them to a customised hyperlink? Thanks!

Thank you, fupin
Sabrina's suggestion to edit the pbk file worked. I changed the setting from 1 to 0 and connected to the remote network via the VPN and am still able to access the local DFS shares.
As per the OPs comments, the username and password I am using for the remote network are both different from the credentials I am using on the local network.
... take the steps in the KB 822707 to resolve it:
1). Locate the .pbk file that contains the entry that you dial. To do so, click Start, click Search, type *.pbk in the All or part of the file name box, and then
click Search.
2). Open the file in Notepad.
3). Locate the following entry: UseRasCredentials=1
4). Modify the entry to the following: UseRasCredentials=0
5). On the File menu, click Save, and the click Exit.
Cheers!

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

Unable to access DFS shares when server 1 goes down

Hello all,
I have a test domain I am building in order to prepare for a new domain we are going to create. We currently have an SBS 2003 that is reaching the end of its' life. We are going to start fresh. I have setup domain-based DFS along with DFS folder replication
for each of the folders. So far, all is working ok, up to this point.
Replication is occurring as it should and my Hyper-V test machines can connect to the mapped drives via the DFS namespace.
\\domain\namespace\target folder
However, once I shut down the primary server (SRV01) I am no longer able to access the shares. The namespace servers tab on the center window of the namespace MMC, has both SRV01 and 02 listed. I receive no errors except "Unable to connect to \\domain\namespace\target
folder because it is unavailable". It is not "failing over" to the secondary available server.
Once I power SRV01 back up, connectivity is then restored to the folders and mapped drives. Is there something I should check for, or am missing?
Any and all insight is appreciated.
Dario Garcia

Hi,
1. Run DFSUTIL /pktinfo to see if the referral target is still the primary server when it is actually down.
If so, run DFSUTIL /pktflush to flush the cached information and try to access the namespace again.
2. If 1 cannot help, whether DNS is also configged on primary server? If so, as it is down,
\\domain may not be recognized.
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected]

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

InDesign CS4 -- unable to browse DFS share folders?

We've recently purchased a slew of CS4 licenses in anticipation for our company's migration from InDesign CS2 to CS4. However in testing we've noticed what appears to be a bug with InDesign. Anytime we use file browse dialog within InDesign CS4(ex. trying to open a new file, trying to import a file into the current .idd, etc..) we run into an issue where we are unable to browse to any DFS network share. The DFS shares are listed, however they are grayed out and unable to be selected. However, the first time InDesign is run, the shares show up correctly and are able to be accessed. When you close InDesign and re-open it, the DFS links are now grayed out and unaccessable.
InDesign CS2 also had the same issue however there was a workaround available: When browsing for a file in CS2, if you choose the "Use Adobe Dialog" all the DFS shares would then be displayed under the 'Computer' link on the left hand side. However after researching these forums and speaking with Adobe techs there is no such feature available in CS4.
Normally I would assume this was some type of compatability issue with DFS and Adobe products...however every other program in the CS4 suite works perfectly... it's just InDesign that's giving us problems(and of course, InDesign is the program we need the most).
Does anyone have any insight as to how we could possibly workaround this issue? Has anyone experienced any similar issues with DFS links being grayed out in InDesign?
Any help with this issue would be greatly appreciated.
Thanks in advance,
Tim

Thanks for the reply.
Apparently they have tried waiting (quite a while) before trying the delete but no joy they still have to close InDesign or reboot.
Message was edited by: elliott-1

Lion 10.7.2 DFS share access issue

hi
i have a macbook air running 10.7.2 and we have a DFS file server running windows 2008 r2
our name space is domain based and i can access the file server using \\domain.com\uk\data and \\domain\uk\home\xxx (where xxx is the username)
the first is the shared data drive and the 2nd is the users home drive
all works beautifully when i am connected via the ethernet. as soon as i move onto the internal wifi (sits on the same network as the ethernet lan and has full access to all network resource, our windows 7 laptops can access all shares just fine) i can all of a sudden no longer access the DFS share \\accel.com\uk\data
it either says it cannot find it or a username and password box comes up (i am using centrify to leverage our AD user accounts on our mac's) when i enter my username and password it does not accept it. I have the same issue when i am outside of the office and vpn's in.
this evening i discovered that i have no problems accessing our DFS share if i enter \\domain.com\uk and i am presented with the folder UK on my dekstop and when i click on it i can see the DATA and HOME drive subfolder
when i now go to the finder and click on connect to server SMB://domain.com/uk/home/xxx it connects fine
so it seems that the /uk/ bit of the DFS path is confusing the mac client when not connected via the ethernet lan cable.
i have tried to mount via the cli but it comes up with no route to host and the console log displays something similar
at least i have a work around now but does anyone know if this is an issue with my name space setup or whether this is a bug (i presume bug as windows 7 clients have no issue with this namespace but i am not taking anything for granted :-) )
thank you
ps i found this post but it is slightly different to the issue i am having https://discussions.apple.com/message/16187498#16187498

The issue has previously hit Apple TV owners. I think people came to the conclusion that it was a HDMI handshake problem. Basically the process where the device and TV greet each other, make up some rules about communicationg and what their secret key is and so on.
I haven't tried this yet, but my local service center says that basically I can do one of two things:
- Downgrade to 10.7 and then download the 10.7.1 update from Apples website. To do this without having a Mac OS X Lion disc, you can hold down CMD + R when the computer boots to be able to access the recovery partition on newer Macs that come without the OS disc.
or..
- Put something in between the computer and TV. For example, if you're using an amplifier as a part of your home theather set up, this will probably work. The service guy said he has his Mini connected to the amplifier, which in turn is connected to speakers and a projector. The inverted colors still appear, but only once per night (i.e. after the first problem is reset by resetting the link then it's fine).
For now, I'll do my little dance of changing the source on the TV from HDMI 1 to HDMI 2 and then back again to reset the link... But, I'll probably try downgrading in a few days.

[Solved] Samba log spam: Unable to connect to CUPS server

Hi everyone,
I'm running into an annoying issue with samba. I don't have any printers installed, and probably won't. However smbd complains to no end in /var/log/errors.log about not being able to connect to a cups server:
Apr 18 12:30:05 asakura nmbd[4361]: *****
Apr 18 12:30:05 asakura nmbd[4361]:
Apr 18 12:30:05 asakura nmbd[4361]: Samba name server ASAKURA is now a local master browser for workgroup MYGROUP on subnet 192.168.1.121
Apr 18 12:30:05 asakura nmbd[4361]:
Apr 18 12:30:05 asakura nmbd[4361]: *****
Apr 18 12:32:22 asakura smbd[4552]: [2009/04/18 12:32:22, 0] printing/print_cups.c:cups_connect(103)
Apr 18 12:32:22 asakura smbd[4552]: Unable to connect to CUPS server localhost:631 - Connection refused
Apr 18 12:32:22 asakura smbd[4553]: [2009/04/18 12:32:22, 0] printing/print_cups.c:cups_connect(103)
Apr 18 12:32:22 asakura smbd[4553]: Unable to connect to CUPS server localhost:631 - Connection refused
Those last two lines get spammed constantly.
I've done a little bit of research into the matter, and followed the steps here to try to resolve the problem: http://www.davekb.com/browse_computer_t … server:txt
Unfortunately it doesn't appear to make any difference.
Here is my /etc/samba/smb.conf:
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
# For a step to step guide on installing, configuring and using samba,
# read the Samba-HOWTO-Collection. This may be obtained from:
# http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
# Many working examples of smb.conf files can be found in the
# Samba-Guide which is generated daily and can be downloaded from:
# http://www.samba.org/samba/docs/Samba-Guide.pdf
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#======================= Global Settings =====================================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = MYGROUP
# server string is the equivalent of the NT Description field
server string = Samba Server
# Security mode. Defines in which mode Samba will operate. Possible
# values are share, user, server, domain and ads. Most people will want
# user level security. See the Samba-HOWTO-Collection for details.
security = user
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
load printers = no
# you may wish to override the location of the printcap file
; printcap name = /etc/printcap
# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
; printcap name = lpstat
# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
; printing = cups
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/%m.log
# Put a capping on the size of the log files (in Kb).
max log size = 50
# Use password server option only with security = server
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password server = *
; password server = <NT-Server-Name>
# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
; realm = MY_REALM
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
; passdb backend = tdbsam
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting.
# Note: Consider carefully the location in the configuration file of
# this line. The included file is read at that point.
; include = /usr/local/samba/lib/smb.conf.%m
# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24
# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes
# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat
# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
dns proxy = no
# These scripts are used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
; add user script = /usr/sbin/useradd %u
; add group script = /usr/sbin/groupadd %g
; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
; delete user script = /usr/sbin/userdel %u
; delete user from group script = /usr/sbin/deluser %u %g
; delete group script = /usr/sbin/groupdel %g
#============================ Share Definitions ==============================
; [homes]
; comment = Home Directories
; browseable = no
; writable = yes
# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /usr/local/samba/lib/netlogon
; guest ok = yes
; writable = no
; share modes = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /usr/local/samba/profiles
; browseable = no
; guest ok = yes
# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
; [printers]
; comment = All Printers
; path = /var/spool/samba
; browseable = no
# Set public = yes to allow user 'guest account' to print
; guest ok = no
; writable = no
; printable = yes
# This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes
# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = yes
; printable = no
; write list = @staff
# Other examples.
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes
# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no
# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
[shared]
path = /media/shared
valid users = foosoft
public = no
writable = yes
[tomato]
path = /media/data1/tomato
valid users = foosoft
public = no
writable = yes
show add printer wizard = no
printing = none
printcap name = /dev/null
disable spoolss = yes
I'm totally out of ideas here, anyone have a tip on what I could try next?
Last edited by FooSoft (2009-04-18 19:52:28)

glad you posted it first i had the same problem.
However, samba was complaining that
printing = none
was invalid. I removed that line and it works great.
thanks
Last edited by lio (2009-10-16 00:20:14)

Unable to Connect to iTunes Store for Apple TV Purchases

For the past 2 days I have been unable to make purchases from the iTunes store with Apple TV. I get the message "Unable to connect to iTunes Store. Temporarily unavailable. Try again later." Despite this message, I have a valid internet connection and I can still connect to the iTunes store to preview movies and TV shows content with my Apple TV. I just cannot make any purchases. My Apple TV software is currently up to date and I have valid credit in my iTunes account.
Apple support have suggested that I contact their support community to see if anyone can help me resolve this problem.

Also having issue, it is ridiculous. Kinda defeats the purpose of having TV if you can't stream any content from iTunes since the change to no hard drive. Come on Apple, I think your better than this.
I have read on a couple forums that they suspect Family Share as the issue, does everyone have Family Share on? I for one do.

Suddenly unable to connect to wireless network...exhausted all fixes

I’ve got an odd problem with my two-week old MacBook Pro and its connection to my wireless network. I’ve done what I think is pretty exhaustive troubleshooting, but remain baffled. Here’s the story.
This morning I connected to my wireless network (DSL 2WIRE modem/router) with no problem. This afternoon I returned and Airport refused to connect, giving me the error message, “Airport is unable to connect to the wireless network…” The network shows up as being available, but when I attempt to connect, it wont. (I didn’t make any changes or install any programs this morning).
Here’s what I’ve done:
[1] Restarted the router
[2] Repaired permissions
[3] Deleted the network’s entry in Keychain Access
[4] Re-entered my WEP code (assuring it is in correctly; I’ve tried both with the “$” and without)
[5] Used interface robustness and without.
[6] Attempted to join the network from the System Preferences>Network.Airport route.
[7] Created a new account and tried connecting.
Other tidbits of information:
[1] Another MacBook in the house connects to the network with no problem.
[2] My MacBook can connect to another (unsecured) network that I can “see” in my house.
So, it would seem my Airport card is working okay.
Any ideas??

Some more info (in case anyone is listening...)
I tried turning off the WEP code and could connect. (Since I share files on my home network, this isn't a "solution").
I also tried Resetting the MacBook Pro System Management Controller (SMC)(See: http://docs.info.apple.com/article.html?artnum=303319). I did this (I think -- there wasn't any indication that the reset "took"), but alas -- no luck.
I gave Apple Care a call, but the support guy, while courteous and all, didn't have anything to offer other than telling me to take it in to an Apple Store for a repair (clearly it isn't a hardware issue).
Heeellllppppp!

Very slow responce when working with Office file on DFS-Share

Very slow responce when working with Office file on DFS-Share
We have implemented the following configuration
Domain level Windows 2000. Two member servers with Windows Server 2008 R2, sharing the same DFS namespace with, at the moment, one folder target called Home.
Users complaining that the access to different MS Office files is very slow. Even creating a new MS Word document using right click context menu takes up to 4 minutes to open. Saving, for example, one singe Excel sheet takes also few minutes.
Tested with both, MS Office 2007 and MS Office 2010. Makes no difference. When using Office 2010 you can see the message like contacting:
\\DomainName\Root\Home\UserName. Other files like TXT, JPG or PDF are not affected.
What makes the thing really weird is the fact, that the behavior described above can absolutely change after client machine being rebooted, suddenly everything becomes very fast and this condition can revert back again just after the next
reboot.
Considerations until now:
1. This has nothing to do with the file size. Even tiny files are affected.
2. AD Sites are configured correctly and the client workstations see themselves in the correct sites.
3. This is not an Office issue. If I map my folder target not as DFS, but directly as shared network drive
\\ServerName\Root\Home\UserName , everything functions as expected
What makes me suspicious: when using f.e. TCPView to monitor connections, I can see, that each time I make any operation on an office file, there will be a connection established to one of the domain controllers, sometimes to remote ones,
located in other countries. But on the other side, even if the connection is established to the nearest DC, operations are still very very slow!
Just forget to say. All clients are Windows 7
Thanks to all who respond.

Dear all,
sorry for the delayed reply. The problem has been solved now and since September 19<sup>th</sup>. everything is functioning as expected.
What was done:
Deleted replication targets excepting the initial ones
Carefully recreated folder targets
Deleted and recreated replication groups
Disabled SNP features on both namespace servers
Created EnableTCPA registry entry
Checked that the following Updates are installed
http://support.microsoft.com/kb/2688074
http://support.microsoft.com/kb/2647452
Concering Office File validation KB2553065 - This Update was already declined on our WSUS server
Kind Regards
Eduard

Unable to connect to DFS shares

Similar Messages

Maybe you are looking for