This is a multi-part message in MIME format.
------=_NextPart_000_0BCE_01C2ADB7.E74D79F0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hey everyone!
I'm having a strange issue with Samba. Here's the setup:
WindowsNT 4 PDC (I know, I know, but there are reasons for this beyond =
my control)
Mixture of Linux and Windows 2000 clients.
Samba 2.2.7 on a Mandrake 9 system that has successfully joined the =
domain and is visible when the client's browse the network.
The Linux clients behave themselves fine, as you would expect. No =
problems with them.
The problem is getting the Win2k clients to authenticate when they try =
to connect to shares that aren't open to everyone. The Samba machine =
does appear to be communicating with the NT4 PDC, but it appears that =
the clients are sending a user name with the domain name added to the =
front of the actual user name (or Samba is sending it that way to the =
PDC anyway). So if there's a user named bearl in the domain alpha, the =
Samba system is checking with the domain controller for a user named =
"alphabearl" and the PDC correctly replies that there is no user by that =
name.
Does anyone have any suggestions for what could be causing this and how =
to fix it? I'll be off the list until Monday morning, but I do =
appreciate the help that you folks provide here.
Bill
------=_NextPart_000_0BCE_01C2ADB7.E74D79F0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hey everyone!
I'm having a strange issue with Samba. =
Here's the=20
setup:
WindowsNT 4 PDC (I know, I know, but =
there are=20
reasons for this beyond my control)
Mixture of Linux and Windows 2000=20
clients.
Samba 2.2.7 on a Mandrake 9 system that =
has=20
successfully joined the domain and is visible when the client's browse =
the=20
network.
The Linux clients behave themselves =
fine, as you=20
would expect. No problems with them.
The problem is getting the Win2k =
clients to=20
authenticate when they try to connect to shares that aren't open to =
everyone.=20
The Samba machine does appear to be communicating with the NT4 PDC, but =
it=20
appears that the clients are sending a user name with the domain name =
added to=20
the front of the actual user name (or Samba is sending it that way to =
the PDC=20
anyway). So if there's a user named bearl in the domain alpha, the =
Samba=20
system is checking with the domain controller for a user named =
"alphabearl" and=20
the PDC correctly replies that there is no user by that =
name.
Does anyone have any suggestions for =
what could be=20
causing this and how to fix it? I'll be off the list until Monday =
morning,=20
but I do appreciate the help that you folks provide here.
Bill
------=_NextPart_000_0BCE_01C2ADB7.E74D79F0--