PDC / samba2.0.7 / NT4
blas.castro at netgiro.com
Fri Oct 27 17:03:27 GMT 2000
My point of view i that, you better use samba-tng as PDC instead of
samba 2.X, because though it is not an stable version its PCD functionality
is acceptable and works with Win9x, WinNT and Win2K.
Unfortunately printing functionality doesn't work yet.
There are some solutions for the last point but i don't know them
----- Original Message -----
From: "Graeme Humphries" <humphries at mail.inroad.net>
To: <samba-ntdom at us5.samba.org>
Sent: Friday, October 27, 2000 4:22 PM
Subject: Re: PDC / samba2.0.7 / NT4
> Message: 3 Date: Thu, 26 Oct 2000 10:10:30 -0500
> From: Simon Allaway <simona at uchicago.edu>
> To: samba <samba-ntdom at us5.samba.org>
> Subject: Re: PDC
> Kai Blin wrote:
> >> > In his mail on 26/10/00, 10:21:08, Spela <spela.svoljsak at aster.si>
> > Samba 2.0.7 works extremely well as a PDC for Windows NT 4.0 clients.
> >will happily serve Win2k clients but within the domain. I can't speak
> >for Win9x clients as we don't use them here.
> (I apologize in advance if this problem has been covered before)
> Well, I'm using Samba 2.0.6 (the RH6.2 package), and I'm having some
> problems running an NT domain. On first boot every morning, 3 of the NT
> workstations fail to find the Linux box when someone initially logs in,
> giving errors like "Unable to find a PDC, I will use your local profile",
> Logout, log back in, and they find the samba box and download their
> profiles properly. The rather unhelpful error message in the NT
> workstation's event viewer is:
> No Windows NT Domain Controller is available for the domain XXXXX. ...
> The following error occurred:
> The RPC server is unavailable.
> 0000: 17 00 02 c0
> On the samba-side I get errors like this:
> [2000/10/27 08:30:06, 0] lib/util_sock.c:write_socket_data(537)
> write_socket_data: write failure. Error = Broken pipe
> [2000/10/27 08:30:06, 0] lib/util_sock.c:write_socket(563)
> write_socket: Error writing 4 bytes to socket 8: ERRNO = Broken pipe
> [2000/10/27 08:30:06, 0] lib/util_sock.c:send_smb(751)
> Error writing 4 bytes to client. -1. Exiting
> (repeated once ~ 30 seconds later)
> And the next entry in the log is the successful login.
> Any ideas? If this has been fixed/worked around/etc. could someone point
> at the solution?
> Graeme Humphries
> --== Graeme Humphries == humphries at inroad.net ==--
> Note: My views are not my employers'.
> It's true, it's true.
More information about the samba-ntdom