domain authentication

From: Evan Mann (emann@questinc.org)
Date: 12/26/01 

From: Evan Mann <emann@questinc.org>
To: focus-ms@securityfocus.com
Date: Wed, 26 Dec 2001 15:09:43 -0500

Today I noticed a potentially large problem. My network is a hybrid with an
NT4.0 SP6a PDC and 8 NT4.0 SP6a BDCs as well as a # of Win2000 Servers just
as members to the network. 95% of my workstation are Windows 2000 Pro SP2
and this issue concerns the Win2000 computers.

It appears that not one single Windows 2000 machine on my network is
actually authenticating on the domain with the PDC . I've checked a dozen
machines and so far every one of them has a LOGONSERVER that was a BDC, and
it seems to always vary as to which BDC that is.

I've searched the KB about this and can't come up with anything that seems
to address this issue, only an issue of Win2000 machines still hitting BDC's
have a PDC has been upgaded to Win2000 Server, which is not the case here.

I'm worried this may cause problems when we do kick our PDC to Win2000
Server+AD in the next few months and would like to at least resolve the
issue while I'm on NT4 and get my workstations actually authenticating with
the PDC.

Relevant Pages

  • Printer driver-related network delays
    ... I've got a Windows XP LAN comprised of several workstations and printers. ... Every time someone on a workstation tries to print to a network printer from ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Printer driver-related network delays
    ... I've got a Windows XP LAN comprised of several workstations and printers. ... Every time someone on a workstation tries to print to a network printer ... Why does Windows XP insist on gathering information or drivers from ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Domain not available
    ... this is a Windows 2003 Server. ... It also appears that my DNS is hosed on the ... The workstation can log in IF it is rebooted and you immediately log in. ... computers on the network, and if you cannot determine that it is set ...
    (microsoft.public.windows.server.sbs)
  • Re: Domain not available
    ... you may be better off in the standard Windows Server group. ... I can add that if as you seem to say, you cannot logon to the errant workstation, and it cannot be found on the network from other computers on the network, and if you cannot determine that it is set to receive DHCP, or indeed that the network adapter is working, you probably need to fix those issues. ...
    (microsoft.public.windows.server.sbs)
  • Very slow response when MDB stored on Small Business Server 2003 network share
    ... I have a client running Windows XP sp1 workstations and a Windows 2003 ... The Server is an Intel PIV Xeon with 512Mb Ram and RAID 5 SATA. ... The network is a 100Mb switched network. ... If I move the files over to a workstation share. ...
    (microsoft.public.windows.server.sbs)