Re: Can't login the morning after.

From: Roger Abell [MVP] (mvpNOSPAM@asu.edu)
Date: 08/14/02 

From: "Roger Abell [MVP]" <mvpNOSPAM@asu.edu>
Date: Tue, 13 Aug 2002 23:14:55 -0700

Bruce,

Let us know if what Bruce offered is informative to your
problem, but it actually sounds to be the exact opposite.
You say, all is good freshly after a reboot.

Comments are inlined . . .
"Bruce A. Knack" <bknack@removeme.fin.uoguelph.ca> wrote in message
news:1e0201c24308$74be8ec0$a4e62ecf@tkmsftngxa06...
> Hi everyone:
>
> Here's the scoop:
> 1 Windows 2000 server and a slew (about 50) Windows XP
> Pro workstations. Each night we RESTART the workstations.
> In the morning, most of them won't login (actually, it's
> more accurate to say that they take forever to do so
> after which the network drives aren't connected properly).
>
> If we reboot them first, they login in nice and fast with
> proper working network drives.
>

OK - so I am left no knowing what is a "Restart" if it is
something different from a reboot.

> Each workstation has netbios turned off, and uses no WINS
> addresses or LMHOST file.
>

I am sort of curious what you mean by netbios turned off,
as in the disabling of NetBT in the Tcp/Ip properties, or as
in not having Microsoft Networking, File and Print installed?

This should be a workable approach provided you have
no apps dependent on NetBIOS.

> Each workstation has one and only one DNS entry to the AD
> server (which runs its own DNS and points to itself
> only).
>

Great, and as it should be with one DC. However, this
does not guarantee all is well. Is the AD supporting zone
enable for dynamic updates or otherwise forced to contain
the AD supporting DNS resource records.

> I suspect that the workstations might be more that 5
> minutes out of sync with the server causing kerberos
> problems but I haven't confirmed this.
>

They should be automatically sync'ing to the DC. In an
multi-DC domain they would sync to the PDC emulator.

> Anyway, maybe the problem is a little less bizzare. What
> do you think?
>

I would run netdiag when logged into a DC, and then also
when logged into a member machine.
This may give some hints. I would also see whether dcdiag
gives any hints.

What you describe, at least if I make assumptions about
what a non-reboot restart is, sounds exactly like the behavior
seen when the client is configured with multiple DNS servers,
some of which are not aware or the AD supporting DNS zone(s).
But, you have ruled this out. With all NetBT disabled, everything
should be able to shift to being direct hosted on port 445 and to
using DNS location services - which apparently is the case at
first after a reboot.

> I'm desparate since our NT 4 network ran hitchless for
> years and this is making me look like a putz. Can you
> say "back to NT 4 on the server??"
>
Yes, although it is round-about, if you have not yet switched
the domain to being in native mode. IOW you can revert the
domain to NT 4 but you would need a second machine to
use as a BDC (to be PDC) in order to do this.

> Cheers and TIA!
> Bruce.

HTH 

--
Roger Abell
MS MVP (Windows Platform), MCSE, MCDBA
Associate Expert - Windows XP ExpertZone
http://www.microsoft.com/windowsxp/expertzone

Relevant Pages

  • Re: DNS Question
    ... If on my internal LAN I have workstations that are members of the ... External DNS resolution is done by the SBS, and those ISP DNS server IP ... Ethernet adapter Wireless Network Connection: ...
    (microsoft.public.windows.server.sbs)
  • Re: DCpromo issue. Health check on AD and group policy.
    ... We have also had intermittent issues with some workstations on the domain not ... The problem is I tryed to DCpromo this server yesterday and couldn't remove ... Single label AD DNS domain name. ... Otherwise, if you need additional specific assistance to get communication working, we'll need specific config info from your machines. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Strange Issue Moving from SBS 2000 to Server 2003 R2
    ... The following error occurred when DNS was queried for the service location ... Errors in your event logs on the workstations or W2k3 server? ... the workstations still know anything about the old SBS 2000 ISA server. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Strange Issue Moving from SBS 2000 to Server 2003 R2
    ... The following error occurred when DNS was queried for the service location ... What happens if you just turn the SBS 2000 off or remove it from the wires. ... Errors in your event logs on the workstations or W2k3 server? ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: No DNS
    ... "The Internet Assigned Numbers Authority has reserved private IP ... The workstations assigned themselves an address when DHCP failed. ... I enabled dhcp and dns on the server and insured my scope was ...
    (microsoft.public.windows.server.sbs)