Hi,
I hope this hasn't already been discussed to death, but I didn't find the
answer through Google.
In short, my question is: how can I advertise a Samba server through
UPnP/Network Discovery? I'm currently using Samba 3.2.6, but should be able to
upgrade if needed.
I am trying to build an I
understand about LLMNR,
it, too only handles name resolution.
After Googling some more with your info as starting point, it seems that in
actuality I would need LLTD (Link Layer Topology Discovery).
From: David Holder [mailto:david.hol...@erion.co.uk]
Sent: Monday, November 16, 2009 9:10 AM
To: K
I haven't tried it, but you should be able to join more than one domain. It's
not trivial. Unlike Windows, you can make a Samba server appear as more than
one server at the same time. You'd basically have to run multiple instances of
Samba completely independent of each other. Each instance woul
> -Original Message-
> From: samba-boun...@lists.samba.org [mailto:samba-
> boun...@lists.samba.org] On Behalf Of Alex Ferrara
> Sent: Tuesday, November 24, 2009 8:33 PM
> To: samba@lists.samba.org
> Subject: [Samba] Windows 7 domain issues
>
> I am running Windows 7 Professionaly 64-bit w
> -Original Message-
> From: samba-boun...@lists.samba.org [mailto:samba-
> boun...@lists.samba.org] On Behalf Of Alex Ferrara
> Sent: Wednesday, November 25, 2009 2:17 PM
> To: samba@lists.samba.org
> Subject: Re: [Samba] Windows 7 domain issues
>
> The DNS update issue I have resolved by
Seems like a nightmare in the making... Basically, no matter what you do, the
data has to be transferred.
How are users going to access the files on site B? If it is through a Web
browser, then a caching proxy in Site A might be your best answer.
Your best option might be to cache the files on
> -Original Message-
> From: samba-boun...@lists.samba.org [mailto:samba-
> boun...@lists.samba.org] On Behalf Of mistofeles
> Sent: Wednesday, November 25, 2009 1:52 PM
> To: samba@lists.samba.org
> Subject: Re: [Samba] how to join to AD ?
>
>
>
> Jason Gerfen-2 wrote:
> >
> > ADS serve
. So maybe I'm better off
> installing
> a 2d server on site B?
>
> > -Oorspronkelijk bericht-
> > Van: samba-boun...@lists.samba.org [mailto:samba-
> > boun...@lists.samba.org] Namens Kevin Keane
> > Verzonden: donderdag 26 november 2009 8:41
> > Aan
> -Original Message-
> From: samba-boun...@lists.samba.org [mailto:samba-
> boun...@lists.samba.org] On Behalf Of mistofeles
> Sent: Thursday, November 26, 2009 8:08 AM
> To: samba@lists.samba.org
> Subject: Re: [Samba] how to join to AD ?
> > Windows already uses IPv6 as the primary protoc
t; > -Oorspronkelijk bericht-
> > Van: samba-boun...@lists.samba.org [mailto:samba-
> > boun...@lists.samba.org] Namens Kevin Keane
> > Verzonden: donderdag 26 november 2009 9:20
> > Aan: samba@lists.samba.org
> > Onderwerp: Re: [Samba] NAS on 2 sites connec
> -Original Message-
> From: samba-boun...@lists.samba.org [mailto:samba-
> boun...@lists.samba.org] On Behalf Of Koen Linders
> Sent: Thursday, November 26, 2009 10:36 PM
> To: samba@lists.samba.org
> Subject: Re: [Samba] NAS on 2 sites connected via slow link
>
>
> > Oh, I thought the N
Thanks for including your whole smb.conf and IP address configuration - that
helped! I notice that your global hosts allow statement (and several others)
only allows for a subnet of 192.168.0, but the IP addresses you list below is
in a different subnet. Basically, you are telling Samba "reject
There are a few ways you could do it, but none of them are good.
Basically, the principle has to be that because you can't touch the LDAP
server, you have to use user name/passwords for authentication. The situation
is fundamentally the same as if you had your users listed in /etc/passwd, so
al
> -Original Message-
> From: samba-boun...@lists.samba.org [mailto:samba-
> boun...@lists.samba.org] On Behalf Of Fabrizio Reale
> Sent: Tuesday, December 01, 2009 5:37 AM
> To: samba@lists.samba.org
> Subject: Re: [Samba] Authenticate Samba with an LDAP w/o the schema
&
You would probably need to define a few more things. Specifically, what does
"discoverable" mean, how much legacy Windows do you want to support? And also,
how much engineering time do you want to spend?
Generally, I'm sure you can go lower than 22mb. There are quite a few low-end
NAS devices o
With GPL software, you don't have to ask permission (and you can't ask
permission here anyway, since most people on this list - including me - are
simply users, not authorized to speak on behalf of the Samba copyright
holders). You must meet certain terms, though.
Hire an intellectual-property
Backup to a network drive is tricky at best with Windows 2008.
It is supposed to work if you use a UNC path instead of a drive letter.
Be aware that R2 is actually a quite different animal (Windows 2008 = Vista
Server, Windows 2008 R2 = Windows 7 Server) so I am not sure if even that is
still s
First of all, I have Samba working in an Active Directory environment. The
Samba server has been basically unchanged for a couple of years now, and
survived an upgrade to Windows 2008 without changes. So it can be done.
Here are the relevant settings from my [global] section in smb.conf (for a
> -Original Message-
> From: Lennart Sorensen
> >
> > Next, you need to make sure that DNS resolution works and uses the
> Windows box as DNS server. This is critically important.
>
> Well you have to make your DNS use the windows box as the DNS server
> for the mydomain.local domain. To
Are you listening on port 139, or only on port 445?
Microsoft had a great idea when they implemented SMB over TCP on port 445 and
eliminated the ancient and inefficient NETBIOS over TCP, or NetBT (on port
139). Unfortunately, they didn't think it all the way through - you still need
NETBIOS to
There isn't a Windows "port" but a Samba-clone. It was made by a company called
Microsoft. You should check them out someday, some of their software actually
doesn't suck.
Seriously, a Windows port of Samba wouldn't make much sense since the whole
point of Samba is to do what Windows already do
You may also want to look into setting up avahi to advertise your CUPS printer.
Avahi is the Linux implementation of the Bonjour advertising protocol; Bonjour
is for Apple what UPnP is for Windows.
> -Original Message-
> From: samba-boun...@lists.samba.org [mailto:samba-
> boun...@lists.
The problem with dual-booting is that you end up with two DNS records pointing
to the same IP address. Active Directory regularly tries to contact the clients
one by one (it does that for any number of administrative purposes). If the
machine is turned off and isn't responding at all - no proble
Quite possibly, this is not actually a Samba problem. Quickbooks is pretty
poorly written and goes very deep into the system; simple file sharing isn't
enough to get it to work. In fact, the main reason Microsoft implemented UAC in
Windows Vista was that Intuit had flat out refused to fix the Qu
You are probably right. Remember that a Samba domain is based on a Windows NT
technology, more than ten years old. Almost everything Microsoft now relies on
Active Directory.
Create an Active Directory domain with a Windows domain controller, and make
your Samba Server a member. Samba works bea
First of all, Windows actually is case sensitive, too (at least on NTFS, not on
FAT). You can actually create C:\tmp\foo and C:\tmp\Foo at the same time, just
not in Explorer (or though most standard Windows APIs).
Secondly, even with case sensitive = No , Samba is not truly case insensitive
(n
It's probably an authentication or permission problem. Since you can see
\\Server, name resolution is working, but the Samba server won't let your XP
user have access to anything. To confirm that this is the problem, try turning
on guest accounts with the setting
(be careful with this setting;
I think part of your problem is that both of your NICs are on the same subnet.
That will usually cause headaches; it confuses the routing table. It is
entirely possible that Samba responds from IP 10.0.0.246 even when the
connection goes to .245 - and you don't have firewall rules for that. Note
Exactly WHY do you need AD instead of NT domains? Without understanding that, I
don't think your question can be answered. In some cases, you can use a
stand-alone Kerberos and/or LDAP server. Or conversely, some application you
use may require a Microsoft AD server, sometimes even a specific ve
> -Original Message-
> From: samba-boun...@lists.samba.org [mailto:samba-
> boun...@lists.samba.org] On Behalf Of Morty
> Sent: Tuesday, April 27, 2010 1:08 AM
> To: samba@lists.samba.org
> Subject: Re: [Samba] samba 4 for new authentication domain?
>
> On Tue, Apr 27, 2010 at 07:36:39PM +
It may also be network discovery, and/or an IPv6 issue. Windows 7 tries to
default to IPv6. There is no NETBIOS or WINS in IPv6, so DNS is pretty much
mandatory (there also is Network Discovery, which is basically UPnP renamed).
My guess is that in your case, Windows 7 first tries to resolve 192
That is conceptually not possible, because "logged in" means that the user is
authenticated - and that is always server-wide or even domain-wide (unless you
use per-share authentication).
If you did kill "his" smbd subprocess, he could connect right back. What you
could do is change the permiss
There are numerous issues with the original poster's request.
For one, he doesn't want to deal with the "complexities" of a Windows domain or
home group - but considers ripping out the heart of Windows networking and
replacing it with Samba. That's akin to taking your brand new Hybrid car to the
33 matches
Mail list logo
