similar to: DFS root only works for more recent Windows clients

Hi, I am trying to configure domain DFS (I think that's the correct term) as below, using the guide on the wiki: https://wiki.samba.org/index.php/Distributed_File_System_(DFS)#Configure_domain-based_DFS_in_Samba I am aware that the wiki says that this doesn't quite work... however it feels to me that it's very close, nearly working, and I might be able to get it going (hopefully?!)

Hi: I've got a samba/DFS server configured that works fine under it's original name, but I'm getting booted out of that DNS domain, into a subdomain. All my (WinXP) clients have drives mapped to names like \\server.domain.com\dfsroot. If I browse to the path, \\server.domain.com\dfsroot, everything works. I can access the shares pointed to via the dfs links But, now the network is

Hello, Anybody now how make with puppet dependence on other service on another node? like : require => Service[dbnode:postgresql] I need ensure that the db is running on another node before start my appserver. Thank you. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

We restored to 3.0.23d after update to 3.0.25a because of strange dfs behavior. the detailed situation: on msdfs root server 'samba' ls -lR dfsroot/: drwxr-xr-x appl1 dfsroot/appl1 lrwxrwxrwx share1 -> msdfs:server1\share1 [dfs] comment = "SaMBa DFS root" path = /path.../dfsroot # next line does not work prior 3.0.25 !!! # hide unreadable = Yes

Hi, Does anyone know if there has been any more progress on the problem of browsing 'complex dfs roots' see http://lists.samba.org/archive/smb-clients/2006-February/000622.html Basically it occurs whenever you have a Microsoft Distributed File System Tree where the links are to subfolders of the destination share. Microsoft clients have no trouble browsing such trees. The Samba HOWTO

Please help me understand why I am unable to connect to and browse the newly configured DFS tree that I installed on my Samba server according to the instructions found in Chapter 18. "Hosting a Microsoft Distributed File System Tree" of the official how-to. Irrespective of whether I try to access the dfs file tree from either the local file browser (and choosing the SMB tree) or from

Hi all, i use Samba 3.5.6 in ads mode (Windows 2008R2) with ldap idmap backend. Servers run Centos 4 and 5. I can't cope with next issue for long time. On all servers in domain winbind constantly tries to create mapping for <SID>-513 and fails because of already existing entry. It just wastes gid range. Note that <SID> is not SID of main domain but another which name equal to

Hi list DFS Links in a separate share seems to work, but in the [homes] section does not. Is this a known problem? Samba is 3.0.26a. /etc/smb.conf excerpts: ---------------------------- 8< ---------------------------- [global] ... host msdfs = yes ... [homes] ... msdfs root = yes ... [dfstest] path = /data/dfsroot msdfs root = yes ---------------------------- 8<

Hi, I'm trying to create a map of DFS links to actual server/share's.? I know that you can get this information by logging on to the DFS root server, but I'm trying to use the libsmbclient API to get this information. I have created a fairly simple DFS structure on 2003 servers with everything on the same domain. //MyDomain/DFSRoot /Link1 -> //Fileserv-1/FileShare1

Hi, I have the following situation concerning group mapping: when I enter > net getlocalsid I get > SID for domain PDC is: S-1-5-21-4166838278-3756557259-2095403906 when I enter > net getlocalsid DOMAIN I get >SID for domain DOMAIN is: S-1-5-21-2018781741-1218799122-1862565094 The group mapping shows > net groupmap list > Domain Users

Hi, I am in the process of migrating our windows workstations to a samba domain. Here is the problem: When creating the domain user I put every user additionalyy in the domain admin group so that he/she can copy his old files on the local profile to his new domain account. Then after this is done I put them to the domain users group but some (!) of the user the lose then access to the

Is there a trick to being able to access shares via \\domain\dfsroot\.. rather than \\computer\dfsroot\... ? Only the latter works for me - samba 3.0.22

Hello List, we have installed samba Version 3.0.20-0.1-SUSE. when I'm entering > net getlocalsid I get > SID for domain <netbios name> is: S-1-5-21-4166838278-3756557259-2095403906 entering > net getlocalsid <domain name> returns > SID for domain <domain name> is: S-1-5-21-2018781741-1218799122-1862565094 Does this mean that the pdc itself is not in the domain

Hi, We have been a samba shop since way back and have used DFS quit a lot the last years. When we went with security ads instead of domain our dfs died. We have tried 3.028(sun) in solaris wich we are leaving and 3.2.1 in linux, our migration target. For our 3.2.1 installation the config looks liket this and the problem manifests itself as a empty share. [Global] kernel oplocks = False oplocks

Since past the beta-times of samba 4 (and it worked in former times!!) it never worked like this: \\yourdomain\share or \\yourdomain \dfs-share. The only thing working along witch your domain is: \\yourdomain\netlogon. I had another thread open on this case some times ago. Greetings Daniel EDV Daniel Müller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tübingen

Hello all I am running into a problem and hoping you can provide a little guidance. I am currently running 3.3.7 downloaded and installed from pware Config file has the following [global] # Workgroup section workgroup = DOMAIN server string = installs-aix Samba Server local master = no # Logging section log file = /usr/local/samba/var/log.%m log

I'm dealing with a Linux environment with extensive automounting, that also has DFS configurations for the Windows clients of various CIFS systems. I've got CIFS automounting working for various CIFS servers, which definitely has its uses, but I'd *love* to be able to mount the DIFS published paths for the CIFS shares? Basically, if I have shares called \\example1\share1 and

Hello, everyone, I'm seeing some inconsistent behavior across SMB clients when configuring shares using the "msdfs proxy" parameter, and was hoping to get some advice from the community on this. My issue is that various SMB clients seem to behave differently when this parameter is pointed as a path that includes a sub-folder under the root share. So, given the following share

Hey all, I have a functioning Samba server in my test lab. All of my must-haves are met. My problem really boils down to a minor nuisance. Basically, when I log the test users in and open My Documents I only see one folder: My Music. Not that I really care but curiosity is killing me here and I can't figure out why the My Pictures folder is not present also. On top of that users love

I've set up a dfs share according to instructions. There is one part of the instructions that I don't understand. I've checked the forum archives but can't find any examples which might help. In the Instructions section (4.1 of the HTML Samba Project Documentation), is shows how to set up the symbolic links in a DFS share, as shown below. I have 2 Samba servers (SMB1 and SMB2).