Atrox wrote:
Atrox wrote:
Hi.
I've got a strange issue here. Some time ago (in march ;) I upgraded my
FreeBSD-6.0 Samba 2.2 to 3.0 (currently 3.0.24). After creating groupmaps
and doing all the other upgrade tasks, everything seemed to be alright.
However, it was not possible
Michael H. Warfield wrote:
On Mon, 2007-10-22 at 23:16 -0700, Atrox wrote:
Michael Lueck wrote:
Atrox wrote:
Michael Lueck wrote:
So, how do you know Samba can not find itself?
Well, server doesn't answer to nmblookup by broadcast:
$ nmblookup -B 192.168.1.255 frontier
Michael Lueck wrote:
Atrox wrote:
Michael Lueck wrote:
So, how do you know Samba can not find itself?
Well, server doesn't answer to nmblookup by broadcast:
$ nmblookup -B 192.168.1.255 frontier
querying frontier on 192.168.1.255
name_query failed to find name frontier
If I
Michael Lueck wrote:
Atrox wrote:
Ah, yes, it's plain-text :)
??? Should be binary, yet readable with cat.
But there's only 1 IP for the server, but there are 8 lines for the
server:
Sounds good. Probably not the same problem as I had then. Yes, I recall
multiple entries
Michael Lueck wrote:
Atrox wrote:
Hmm, actually the machine runs OpenVPN too, so its (bridged) tap device
has
its own IP that falls into the same netmask /24. Is it possible that
Samba
may get confused about that? Should specifying only the internal
interface
(and lo0 maybe
Atrox wrote:
Hello.
I'm using Samba 3.0.25a on FreeBSD-6.0. Samba is configured to be a PDC.
Samba can't find its hostname via nmblookup:
$ nmblookup -B 192.168.1.255 frontier
querying frontier on 192.168.1.255
name_query failed to find name frontier
If I query Samba via unicast
Michael Lueck wrote:
Atrox wrote:
Samba can't find its hostname via nmblookup:
$ nmblookup -B 192.168.1.255 frontier
querying frontier on 192.168.1.255
name_query failed to find name frontier
Have you ever had another (multiple) IP addresses on this particular
installation? Long long
Hello.
I'm using Samba 3.0.25a on FreeBSD-6.0. Samba is configured to be a PDC.
Samba can't find its hostname via nmblookup:
$ nmblookup -B 192.168.1.255 frontier
querying frontier on 192.168.1.255
name_query failed to find name frontier
If I query Samba via unicast, it answers OK:
$ nmblookup
Atrox wrote:
Logan Shaw wrote:
4) Make sure the new server has the same SID as the old.
There are lots of ways of doing this, but I believe the
one I used was to run rpcclient's lookupsids command
against the domain itself to get the old SID on 2.2.x, then
I used
Logan Shaw wrote:
4) Make sure the new server has the same SID as the old.
There are lots of ways of doing this, but I believe the
one I used was to run rpcclient's lookupsids command
against the domain itself to get the old SID on 2.2.x, then
I used net setlocalsid
Atrox wrote:
Hi.
I've got a strange issue here. Some time ago (in march ;) I upgraded my
FreeBSD-6.0 Samba 2.2 to 3.0 (currently 3.0.24). After creating groupmaps
and doing all the other upgrade tasks, everything seemed to be alright.
However, it was not possible to login from some
Hi.
I've got a strange issue here. Some time ago (in march ;) I upgraded my
FreeBSD-6.0 Samba 2.2 to 3.0 (currently 3.0.24). After creating groupmaps
and doing all the other upgrade tasks, everything seemed to be alright.
However, it was not possible to login from some machines (getting error
12 matches
Mail list logo
