Re: [Samba] Unable to access and browse a DFS tree
Theo: You could try experimenting w/ the following options in your [dfs] section.: map to guest = [ never | bad user | bad password ] public = yes (a.k.a. guest ok = yes ) guest only = yes guest account = ftp Good luck. -Bill Theo Kanter wrote: 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 windows, I get a login dialog box and I do not understand why this is the case. Moreover, no userid/password from either the Samba server or the Windows machine with the share works. I compiled samba (version 3.0.21b) with the option --with-msdfs. Below I include smb.conf and fstab, showing how the share gets mounted via smbfs, as well as an 'ls' showing the access rights and ownership of the directory. The remote share on the Windows machine grants read access to everyone. Thanks for your help in advance, Theo --- smb.conf --- [global] dos charset = ISO-8859-1 unix charset = ISO-8859-1 display charset = ISO-8859-1 workgroup = VERKSTAD server string = Kanter Samba Server interfaces = eth0, 192.168.0.100/24 security = SHARE encrypt passwords = No guest account = theo log file = /var/log/samba/log.%m max log size = 50 socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = cups os level = 33 dns proxy = No wins support = Yes host msdfs = Yes hosts allow = 192.168.0., 127.0.0.1 [dfs] comment = DFS Share path = /export/dfsroot msdfs root = Yes -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba, LDAP, and unix account
Ether: If you're new to samba, you may want to start w/ smbpasswd, or tdb authentication before going to LDAP. http://us5.samba.org/samba/docs/man/Samba3-ByExample/simple.html#id2517375 http://us5.samba.org/samba/docs/man/Samba3-HOWTO/install.html#tdbdocs -Bill Ether wrote: Hi every one! Until now, I used samba as a simple public share server... and now, I would like to use it with many account. I know it's possible, but I would like something particular: I would like to have SAMBA account independent from the unix account system! Here is how I think my system: all files on the server will be owned by a unix account dedicated to samba storage, but I would like to set owner and access right from user of the samba acount system. I also would like to be able to set up right on each directory from windows and being able to get the samba account list from windows without creating a PDC with samba and registering each pc to this domain Is it possible, or Do I have to create a PDC? Franck thanks to every one for your answers ! -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba LDAP caching when LDAP server unavailable - possible?
Tomasz: I had heard that some people were interested in caching passwords (which could be stored in NIS, or LDAP) on linux laptops so that a user could log in even when disconnected from their LDAP or NIS domain. The theory was that the nss (name service switch) and nscd (name service cache daemon) system(s) could be tuned/modified to cache this information. As far as I know, this has not been done/tested for use w/ samba the way you describe. See section: 2.1.4 The Name Service Caching Daemon http://www.saas.nsw.edu.au/solutions/ldap-auth-pam.html -Bill Tomasz Chmielewski wrote: I've been using Samba with OpenLDAP with great success on normal servers. Recently however, it appeared to us that for remote locations it is more economically viable to replace Samba servers with Samba running on little routers like ASUS WL-500g with openwrt firmware/software. It has a broadcom/mipsel CPU, and thanks to openwrt (http://openwrt.org), it is possible to run lots of software on it. Pretty nice for small offices - small, no fan, no hard disk etc. other moving parts (you can connect a USB stick to it if you want to store files/profiles). There is one glitch however - no OpenLDAP port. So a Samba domain controller running on these tiny routers would have to authenticate users users against an external OpenLDAP server (probably in the company headquaters). My experience shows that a company with several branches located throughout the city/country/world have connectivity problems from time to time (especiall when there is no IT staff in the branches). With no local LDAP server this would mean users not able to work (as they can't authenticate). Is it possible to set up Samba to cache credentials retrieved from the LDAP, and when LDAP is unavailable, to use these cached credentials? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] A hierarchy of DFS trees...
I just made a DFS link that pointed to another DFS share on a different server... It seems to confuse the Win'XP client a bit, but it can be made to work. That means I can build a tree structure w/ DFS. I can arrange all my servers and shares into a hierarchy. It may not be practical, but in theory, This could be used as a hierarchical substitute for the network neighborhood. I could configure a server called browse, w/ a number of DFS shares. \\browse.mycompany.com\northeast \\browse.mycompany.com\westcoast \\browse.mycompany.com\gulfcoast browse # cd /dfsshares browse # mkdir northeast browse # ln -s msdfs:vermont.mycompany.com/servers northeast/vermont browse # ln -s msdfs:jersey.mycompany.com/servers northeast/jersey browse # ln -s msdfs:newyork.mycompany.com/servers northeast/newyork browse # mkdir westcoast browse # ln -s msdfs:irvine.mycompany.com/servers westcoast/irvine browse # ln -s msdfs:hollywood.mycompany.com/servers westcoast/hollywood browse # ln -s msdfs:pasadena.mycompany.com/servers westcoast/pasadena browse # mkdir gulfcoast browse # ln -s msdfs:louisiana.mycompany.com/servers gulfcoast/louisiana browse # ln -s msdfs:missippi.mycompany.com/servers gulfcoast/missippi browse # ln -s msdfs:texas.mycompany.com/servers gulfcoast/texas Or.. I guess I could just have shares w/ shortcut icons in them. -Bill -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba without netbios
Windows 2000 with ADS, and the ability to disable NetBIOS over TCP/IP. In its place Windows 200X uses DNS, Kerberos, LDAP, and Raw SMB over TCP/IP. The DNS, Kerberos and LDAP services run over the standard well-known ports. Raw SMB over TCP/IP uses TCP port 445. On Windows 200X clients, when NetBIOS over TCP/IP is disabled, and an attempt is made to join a domain, the client automatically tries to use the combination of DNS, Kerberos, LDAP and TCP port 445 services with the expectation that Microsoft Active Directory is being used. In order to remain backwards compatible, TCP port 139 can also be used. The mechanisms behind TCP ports 139 and 445 are very different. A connection made on port 445 must be able to resolve the fully qualified hostname using the protocols expected within ADS. That is, via DNS using SRV records as well as A records. Additionally, the client will try to use Kerberos information to contact the DNS server and the LDAP server. It expects to find SMB information in the Kerberos PAC (a data blob inside the Kerberos ticket that is unique to ADS's implementation). With ADS browsing involves DNS, LDAP and Raw SMB traffic over ports 445 and 139. The client expects all the information that it wold obtain if it were a member of an ADS domain. Samba-3 supports port 445 and all operations necessary to be an ADS domain member server. It can not be an ADS server, and it can not be an ADS domain controller. That functionality is being added in the Samba-4 project. What this means is, that if you disable NetBIOS over TCP/IP on your clients and on Samba-3, you will not be able to browse the network. Additionally, Samba can NOT be a domain controller. It can be a stand-alone server without NetBIOS over TCP/IP. Samba-3 can be a file and print server for Windows clients that have NetBIOS disabled - but some things may break. In short, NetBIOS-less SMB implies ADS. Samba-3 is not an ADS server. Ergo, NO ADS for all practical purposes means DOES NOT WORK. On Tuesday 25 October 2005 07:12, William Burns wrote: On Monday 24 October 2005 14:06, julius Junghans wrote: ive read a lot in the howto about netbios/ddns, but im still confused if its possible for samba to only use tcp/ip without netbios. are there any howtos for this topic that are not mentioned in the samba3 howto? John H Terpstra wrote: Please point me to the documentation (section and page number please) that you have referred to and that is not clear to you. I need to know so I can fix it. John: I don't know what Julius is looking at but... I'm looking into similar docs re: DFS not working on SAMBA servers that are referred to w/ fully.qualified.sub.domains... (even though a straight samba share WILL work under that name) I figure that all the info that Julius needs is in the docs... I am not sufficiently tuned in to answer what Julius' needs are. I offer a speculative answer below. Here's how he might proceed to get where he wants to go. At the bottom of this section: http://us3.samba.org/samba/docs/Samba-Guide.pdf 13.3.1.2 Routed Networks - Page 480 There's a pretty definitive sounding statement: Note The use of DNS is not an acceptable substitute for WINS. DNS does not store specific information regarding NetBIOS networking particulars that get stored in the WINS name resolution database and that Windows clients require and depend on. That sounds like a no. Correct - DNS can not substitue for WINS or Broadcast UDP-based name resolution for NetBIOS over TCP/IP enabled configurations. ^^ But, later in section 15.1 Joining a Domain: Windows 200x/XP Professional at the bottom of page 495, there's this: Where NetBIOS technology uses WINS as well as UDP broadcast as key mechanisms for name resolution, Active Directory servers register their services with the Microsoft Dynamic DNS server. Windows clients must be able to query the correct DNS server to find the services (like which machines are domain controllers or which machines have the Netlogon service running). So, sometime you HAVE to use DNS For ADS DNS is essential. Later there's a note that you don't have to do this [DNS] if you're in a SAMBA domain. Correct - You must use NetBIOS over TCP/IP. But... Does this mean I can disable Netbios/Netbeui? Well, yes you can, but your network wil not be browseable and some SMB operations will fail. There's A direct answer to Julius' question in section 16.5 Questions and Answers at the bottom of page 554 6. Q: Is it possible to reduce network broadcast activity with Samba-3? A: Yes, there are two ways to do this. The first involves use of WINS (See TOSHARG2, Chapter 9, Section 9.5, “WINS — The Windows Inter-networking Name Server”); the alternate method involves disabling the use of NetBIOS over TCP/IP. This second method requires a correctly
Re: [Samba] samba without netbios
On Monday 24 October 2005 14:06, julius Junghans wrote: ive read a lot in the howto about netbios/ddns, but im still confused if its possible for samba to only use tcp/ip without netbios. are there any howtos for this topic that are not mentioned in the samba3 howto? John H Terpstra wrote: Please point me to the documentation (section and page number please) that you have referred to and that is not clear to you. I need to know so I can fix it. John: I don't know what Julius is looking at but... I'm looking into similar docs re: DFS not working on SAMBA servers that are referred to w/ fully.qualified.sub.domains... (even though a straight samba share WILL work under that name) I figure that all the info that Julius needs is in the docs... Here's how he might proceed to get where he wants to go. At the bottom of this section: http://us3.samba.org/samba/docs/Samba-Guide.pdf 13.3.1.2 Routed Networks - Page 480 There's a pretty definitive sounding statement: Note The use of DNS is not an acceptable substitute for WINS. DNS does not store specific information regarding NetBIOS networking particulars that get stored in the WINS name resolution database and that Windows clients require and depend on. That sounds like a no. But, later in section 15.1 Joining a Domain: Windows 200x/XP Professional at the bottom of page 495, there's this: Where NetBIOS technology uses WINS as well as UDP broadcast as key mechanisms for name resolution, Active Directory servers register their services with the Microsoft Dynamic DNS server. Windows clients must be able to query the correct DNS server to find the services (like which machines are domain controllers or which machines have the Netlogon service running). So, sometime you HAVE to use DNS Later there's a note that you don't have to do this [DNS] if you're in a SAMBA domain. But... Does this mean I can disable Netbios/Netbeui? There's A direct answer to Julius' question in section 16.5 Questions and Answers at the bottom of page 554 6. Q: Is it possible to reduce network broadcast activity with Samba-3? A: Yes, there are two ways to do this. The first involves use of WINS (See TOSHARG2, Chapter 9, Section 9.5, “WINS — The Windows Inter-networking Name Server”); the alternate method involves disabling the use of NetBIOS over TCP/IP. This second method requires a correctly configured DNS server (see TOSHARG2, Chapter 9, Section 9.3, “Discussion”) Plus the following note: Note Use of SMB without NetBIOS is possible only on Windows 200x/XP Professional clients and servers, as well as with Samba-3. Personally, I find the answer to question 6 a little confusing because I *thought* that in Win'9x, disabling NetBIOS over TCP/IP meant that you'd get no SMB traffic on the TCP/IP side of that client. (It'd be all NetBEUI) This Win' 9x NetBIOS over TCP/IP config feature does not exist in Win' XP as such, but is provided by Win' XP's TCP/IP NetBIOS Helper in Control-Panel/Services which Enables support for NetBIOS over TCP/IP (NetBT) service and NetBIOS name resolution This service sometimes inexplicably gets turned off, causing the Win'XP client to fail to use DNS resolution to resolve SMB names. But... it IS possible That brings us to this section http://tr.samba.org/samba/docs/man/Samba-HOWTO-Collection/NetworkBrowsing.html#id2551944 which is not numbered in the html version ??? but in the PDF version has a section number: http://us3.samba.org/samba/docs/Samba3-HOWTO.pdf 9.3.2 TCP/IP without NetBIOS On page 151 we learn: Use of raw SMB over TCP/IP (No NetBIOS layer) can be done only with Active Directory domains. Samba is not an Active Directory domain controller: ergo, it is not possible to run Samba as a domain controller and at the same time not use NetBIOS. But, it should be possible to do this w/ a stand-alone SAMBA server. And then, a very interesting statement: Where Samba is used as an Active Directory domain member server (DMS) it is possible to configure Samba to not use NetBIOS over TCP/IP. This is interesting because I *thought* that I was concerned about replacing NetBIOS w/ DNS name resolution on my Win'XP clients. Is this also about how SAMBA resolves names? I hadn't given any thought to the possibility that SAMBA might need to resolve an IP from a PC name.., or even know the PC name at all... IS this a requirement? I mean, isn't the smbd process passive? Maybe not.? if NetBIOS over TCP/IP is disabled, it is necessary to manually create appropriate DNS entries for the Samba DMS because they will not be automatically generated either by Samba, or by the ADS environment. Now, it seems like I've been told that: if I want to have a SAMBA server without NetBIOS (only DNS) name services enabled on the clients, my only hope is to get a SAMBA member server into my Active Directory domain. I'd expect to see the SRV records that I need to put into A.D. spelled out... Is that what's on page 152? Instead, it
Re: [Samba] MSDFS redirection WinXP SP2
David:
I'm running w/ smbd version 3.0.10
and have DFS working w/ XP-SP2.
In my smb.conf, I have:
smb ports = 139
Possibly that will help w/ your problem.
-Bill
David Richardson wrote:
I am currently having problems accesing our samba msdfs shares from
Windows XP SP2, Windows 2000 and WinXP SP1 seem unaffected. I have
attached the smb.conf and the exports files that define the shares.
Running ethereal on the different clients seems to point to the fact
that XP SP2 no longer seems to be using the netbios-ssn (139) port.
for GET_DFS_REFERRAL instead its using microsoft-ds (445). I have
ethereal dumps if required.
Any advice would be most welcome.
Many thanks Dave
smb.conf
# Global parameters
[global]
workgroup = LONDON
security = DOMAIN
encrypt passwords = Yes
password server = bonky
passwd program = /usr/bin/passwd %u
passwd chat = *New*password* %n\n *Retype*new*password* %n\n
*passwd:*all*authentication*tokens*updated*successfully*
max log size = 50
log file = /var/log/samba/log.%m
os level = 0
local master = No
domain master = no
NIS homedir = Yes
comment = Samba %v + msdfs redirector
#print command = /usr/samba/bin/sambalp %p %s %U %m
lppause command =
lpresume command =
wins server = 10.123.10.50
name resolve order = wins host bcast
locking = yes
socket options = TCP_NODELAY
preserve case = yes
short preserve case = yes
#log level = 4
interfaces = eth0 lo
bind interfaces only = Yes
host msdfs = yes
netbios aliases = cvs hades hosts jobs packages production
publicity vdisk
# Some virus protection
veto files = /*.eml/*.nws/riched20.dll/*.{*}/
exports.hades.conf
[2d]
msdfs root = yes
msdfs proxy = \dualit\data-2d
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] DFS question
Scott: The approach that you're taking seems reasonable. The syntax looks good. If one of the servers goes down for an extended time, the clients that authenticated to it might have to logout/login again after their DFS cache times out. -Bill Scott Mayo wrote: Was wondering if someone could tell me if this is correct. I want to set up some DFS shares. I have 3 servers with SAMBA/LDAP on them. My first is basically my PDC and the other two are my BDCs. I assume that I will have to set all of this up on each server, so that no matter which server catches the logon, the logon script will get run. Also, if one of the servers was to go down for a bit, the other two could still handle logons and some of the directories would be available. Each server has: Need to add these to samba: [global] host msdfs = yes [teacher] path = /export/teachers msdfs root = yes [student] path = /export/students msdfs root = yes Create these directories and add the links in each like so (shares are already there): /export/teachers ln -s msdfs:bes-serve\\bes elemstudents ln -s msdfs:bms-serve\\bms midstudents ln -s msdfs:bhs-serve\\bhs highstudents ln -s msdfs:bes-serve\\teachpublic teacherspublic ln -s msdfs:bes-serve\\lemburg lemburger ln -s msdfs:bes-serve\\school elemteachers ln -s msdfs:bms-serve\\school midteachers ln -s msdfs:bhs-serve\\school highteachers /export/students ln -s msdfs:bes-serve\\bes elemstudents ln -s msdfs:bms-serve\\bms midstudents ln -s msdfs:bhs-serve\\bhs highstudents Logonscript would contain: teacher.bat net use T: \\b?s-serve\teacher (where the ? is either e,m or h depending on which server the script is run) student.bat net use S: \\b?s-serve\student (where the ? is either e,m or h depending on which server the script is run) I was just wanting to get confirmation on this before I enter it all on my servers. Thanks. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] DFS not working w/ fully.qualified.sub.domain
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 being re-architected... The clients will be in multiple IP subnets, and the server needs to be moved to a subdomain of domain.com. I configured a sub.domain.com on my DNS server. I can browse via the new name: \\server.sub.domain.com\dfsroot, and I can see all the links, but when I rt-click, and view properties on any of these links, the DFS tab is missing. If I rt-click/view-properties on a dfs-link using the old server name, I can see the DFS tab again. How do I get the DFS tab back? How do I make the DFS links work when the DFS server is in a subdomain? - Other info: clicking on a DFS link gives me the error message: \\server.sub.domain\dfsroot\remoteshare refers to a location that is unavailable. I don't know if this is a server-side issue, or a client side issue. I get the same results when trying to access the DFS links from a windows 2003 machine. An nt4 machine will refuse to talk to the samba server on the new name at ALL. It gives a message The network path was not found when trying to browse the path \\server.sub.domain.com. Is this some feature of windows clients? Is this a known problem? Does anyone know if the same behavior exists when trying to browse a DFS share on a win'2000 server when it has its host-name in a sub-domain? -Bill -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] DFS not working w/ fully.qualified.sub.domain
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 being re-architected... The clients will be in multiple IP subnets, and the server needs to be moved to a subdomain of domain.com. I configured a sub.domain.com on my DNS server. I can browse via the new name: \\server.sub.domain.com\dfsroot, and I can see all the links, but when I rt-click, and view properties on any of these links, the DFS tab is missing. If I rt-click/view-properties on a dfs-link using the old server name, I can see the DFS tab again. How do I get the DFS tab back? How do I make the DFS links work when the DFS server is in a subdomain? - Other info: clicking on a DFS link gives me the error message: \\server.sub.domain\dfsroot\remoteshare refers to a location that is unavailable. I don't know if this is a server-side issue, or a client side issue. I get the same results when trying to access the DFS links from a windows 2003 machine. An nt4 machine will refuse to talk to the samba server on the new name at ALL. It gives a message The network path was not found when trying to browse the path \\server.sub.domain.com. Is this some feature of windows clients? Is this a known problem? Does anyone know if the same behavior exists when trying to browse a DFS share on a win'2000 server when it has its host-name in a sub-domain? -Bill -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] one opinion about searching samba docs for answers
John:
I agreee about the searchability of the samba list.
Using the site parameter of google helps by keeping your search
results limited (mostly) to the samba list.
http://www.google.com/search?q=domain_master_node_status_fail+site%3Asamba.orghl=enlr=
domain_master_node_status_fail site:samba.org
I've often wondered why there isn't a next by thread link on the
archived messages.
You can always take the extra click to get to the thread view, but often
there's no reply, and there's a tedious succession of wasted clicks.
This probably isn't an immediate help, but the code can be browsed online:
http://websvn.samba.org/cgi-bin/viewcvs.cgi/*checkout*/branches/SAMBA_3_1_RELEASE/source/nmbd/nmbd_browsesync.c?rev=2563content-type=text%2Fplain
Someone probably thought that error message was self explanatory.
It does mention the term Master Browser, which might cause a person to
look here:
How Browsing Functions
http://us4.samba.org/samba/docs/man/Samba-HOWTO-Collection/NetworkBrowsing.html#id2561439
It also contains the term/phrase: node status request, which might
prompt an aggressive google-jockey to try this search:
http://www.google.com/search?hl=enq=node-status-request
Which (among other things) returns this link:
http://www.cpan.org/modules/by-module/Net/Net-NBName-0.25.readme
Which yields this info:
The node status request can be used to query the NetBIOS name table
of a remote host
All this together is *probably* enough to put a sys-admin on the right
track.
It's not always possible to direct a user to a single relevant area of
configuration.
A lot depends on the circumstances of the application, and the intent of
the user.
Link-rot is another problem. If the documentation gets a significant
overhaul, then links (from error messages) into that documentation might
break over time.
If the code that generates the error messages in SAMBA is consistent
enough, it might be possible to generate a list of all the error messages.
From there, it might be helpful to link all the buzzwords to glossary
entries.
If we assume that the list can be generated easily enough, how many
volunteers do you think might be available to identify terms, link to
definitions, solutions, and/or documentation?
-Bill
From:
http://websvn.samba.org/cgi-bin/viewcvs.cgi/*checkout*/branches/SAMBA_3_1_RELEASE/source/nmbd/nmbd_browsesync.c?rev=2563content-type=text%2Fplain
/
Function called when a node status query to a domain master browser
IP fails.
/
static void domain_master_node_status_fail(struct subnet_record *subrec,
struct response_record *rrec)
{
struct userdata_struct *userdata = rrec-userdata;
if( DEBUGLVL( 0 ) ) {
dbgtext( domain_master_node_status_fail:\n );
dbgtext( Doing a node status request to the domain master
browser\n );
dbgtext( for workgroup %s , userdata ? userdata-data :
NULL );
dbgtext( at IP %s failed.\n, inet_ntoa(rrec-packet-ip) );
dbgtext( Cannot sync browser lists.\n );
}
}
John Stile wrote:
It sure is hard to find info in the documentation/mailing list for a
specific error. If an error log message was created by smbd, nmbd, or
winbind, shouldn't the documentation contain a description, cause, and
possible solution?
Specific case in point:
[2005/08/05 11:31:22, 0]
nmbd/nmbd_browsesync.c:domain_master_node_status_fail(250)
domain_master_node_status_fail:
Doing a node status request to the domain master browser
for workgroup MS at IP 192.168.40.20 failed.
Cannot sync browser lists.
Searching the docs returned nothing for search strings:
nmbd_browsesync
domain_master_node_status_fail
Cannot sync browser lists
The documents cover just about everything, except how to go from a log
message to the relevant areas of configuration. On the other hand, the
documentation does a very good job of going from theory to high level
samba planning (with some configuration details). Shouldn't the
documentation contain common error names, so that a search will direct
the reader to the proper place?
It might be nice if there was a good search-able mailing list archive at
samba.org, but the archive doesn't search well. Maybe because too many
people abused the search tool because answers are not in the docs.
So I end up using an Internet Search Engine only to find many hits with
the same questions and no concise answers.
I might be the only own who feels this way, but I would love to know how
to fix it. Every time I go through this, I have these thoughts.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Dfs is not working
Daniel: What does it look like when you do a: ls -l name When you did the ln -s statement, did you enclose your msdfs: parameter in single quotes? That's what the SAMBA docs say to do. If you don't escape the comma somehow, it'll screw up your ln statement. Second issue: Why would you use DFS to serve out two different shares (shareA, and shareB) on the same server? AFAIK, that's not what DFS is for, and maybe it doesn't like that. Plus, that gives you no redundancy. You should use DFS for redundancy on identical read-only shares. serverA, and serverB should both have a copy of shareA. -Bill Daniel Müller wrote: Hi, i have a smba 3 working, and I’ m trying to build dfs .When I set up my dfs this way: ln –s msdfs:serverA\\shareA name, or ln-s msdfs:serverA\\shareB, it is working! But if I try ln-s msdfs:serverA\\shareA,serverA\\shareB name, I only can get the first share (shareA) in the network. Have someone did it and how can I succeed ? Daniel -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] My first LDAP PDC - Win2k Profiles, redirection and guest accounts
Louis: The howto refers to win'95 machines. Are there no changes to this procedure for working w/ win2k, or XP clients? -Bill Louis van Belle wrote: hi, its a policy template so you can manage you computers in your Domain. But you need poledit.exe to use it. .. never used policies ?? here's a small howto http://www.rescomp.berkeley.edu/about/training/senior/tc/Policy-HOWTO/Policy -HOWTO.html#toc2 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Redundant DFS via DNS entries?
Hi: I'm trying to create a group of samba/NFS servers. The NIS/NFS/Automount part has always worked fine. Now I'm trying to duplicate what automount does w/ DFS. A single DFS server would be a single point of failure. I need redundant DFS. I've configured a pair of samba servers, w/ DFS on each one. Each machine has a few non-dfs shares referred to by dfs links. I've configured two DNS A records, pointing smbnfs.my.domain to *both* IP addresses of these two machines. Testing confirms that if one of the two machines goes down, after about a 15-sec timeout, the Win'XP clients will figure it out and switch to the other server. This means that if a single machine goes down, the DFS links will still be available. Also, I would still be able to use DFS to redirect client machines to a new SAMBA server without remapping drives. My problem is that DFS services under this DNS alias appear to be flakey. Sometimes the DFS links work fine. Other times, the DFS links stop working, and if (w/ the XP client) I get right-click/properties on those folder/links at those times, the DFS tab does not appear under the folder's properties box. Other times, if I look at the DFS properties of a link, the name of the DFS server alias appears instead of the name of the back-end server that's listed in the msdfs links. (smbnfs.my.domain appears instead of server1.my.domain) How can I make the redundant DFS system work? Or... What other methods could be used to give me SAMBA based redundant DFS services? -Bill -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
