Re: Event 5774 /DNS errors/Latest updates

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Mel (anonymous_at_discussions.microsoft.com)
Date: 08/11/04 

Date: Wed, 11 Aug 2004 11:27:32 -0700

Ok, Here are a couple of other things.

First you said the following:
101.107.192.1<--Is this your
>router?

Yes, this is a router. Router is handling DHCP.
Evidently, it too is handling DNS as well as all
workstations are set to obtain both automatically.
I have tried disabling DNS completely on this server and
it does not change anything.

What is puzzling is this has all worked for almost 2 years
and fell apart after an automatic update.

Here is current configuration:

Windows 2000 IP Configuration

        Host Name . . . . . . . . . . . . : SERVER1
        Primary DNS Suffix . . . . . . . :
local.sierradisplay.com
        Node Type . . . . . . . . . . . . : Hybrid

        IP Routing Enabled. . . . . . . . : No

        WINS Proxy Enabled. . . . . . . . : No

        DNS Suffix Search List. . . . . . :
local.sierradisplay.com
                                            
sierradisplay.com

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix . :
        Description . . . . . . . . . . . : Intel(R)
82540EM Based Network Connection
        Physical Address. . . . . . . . . : 00-C0-9F-20-2A-
E6

        DHCP Enabled. . . . . . . . . . . : No

        IP Address. . . . . . . . . . . . : 101.107.192.2

        Subnet Mask . . . . . . . . . . . : 255.255.255.0

        Default Gateway . . . . . . . . . : 101.107.192.1

        DNS Servers . . . . . . . . . . . : 101.107.192.2

Ok, Please consider the following:

1. Upon a reboot, the FIRST (and only the FIRST)
workstation can log onto the network successfully
(including logon script).

2. Subsequent logon by other workstations are all doomed.
It goes through the motions but scripts do not execute and
drives are not connected. If these users got to "My
Computer" and click on any network drives the see a
message stating.

X:\ is not accessible.
There are currently no logon servers available to service
the logon request.

If these users click on network places->entire network
etc, to get to the server they will also receive a message
stating the theree are currently no logon servers
available to service the logon request.

3. If I run my little batch file that issues these
commands:

ipconfig /flushdns
ipconfig /registerdns
net stop netlogon
net start netlogon

Then everything works correctly. Everyone can logon and
all scripts execute. All drives connect.

4. I found a knowledgebase article # 830063 that
describes similar behavior when Routing and Remote Access
is installed with DNS and a Hotfix has been installed. I'm
not sure if hotfix is installed. Not shown in Add/remove
Programs.

If I Stop the Routing and RAS process (before running by
batchfile) I get the same behavior.

Thanks for your help

Mel

>-----Original Message-----
>In news:1cdd01c47c44$61ea9380$a601280a@phx.gbl,
>Mel <anonymous@discussions.microsoft.com> wrote their
comments
>Then Kevin replied below:
>> Ok, here is the latest.
>>
>> I just did the following per your post.
>>
>> Deleted both zones. Forward and reverse.
>> created zones using the name local.sierradisplay.com and
>> enabled updates. Then rebooted.
>
>You did not need to reboot, all you needed to do was run
the commands you
>ran after you rebooted, these commands are needed to
create the SRV records
>and register the DC's IP addresses.
>
>>
>> Same problems. System very slow and sluggish until I
run
>> the following commands either in a batch file or
manually
>> from the command line.
>>
>> ipconfig /flushdns
>> ipconfig /registerdns
>> net stop netlogon
>> net start netlogon
>>
>> Then everything works.
>
>I just noticed, from your first reply with the
ipconfig /all
>
> IP Address. . . . . . . . . . . . : 101.107.192.2
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 101.107.192.1
> DNS Servers . . . . . . . . . . . :
101.107.192.1<--Is this your
>router? What DNS server is this? Does it allow dynamic
updates. If DNS is on
>this machine, which it should be, point it to its own
address for DNS.
>
>I believe everything would have worked if you had run
these commands without
>the reboot.
>run this command to see how everything checks out,
netdiag /test:dns /v
>
>
>--
>Best regards,
>Kevin D4 Dad Goodknecht Sr. [MVP]
>Hope This Helps
>================================================
>--
>When responding to posts, please "Reply to Group"
>via your newsreader so that others may learn and
>benefit from your issue, to respond directly to
>me remove the nospam. from my email address.
>================================================
>http://www.lonestaramerica.com/
>================================================
>Use Outlook Express?... Get OE_Quotefix:
>It will strip signature out and more
>http://home.in.tum.de/~jain/software/oe-quotefix/
>================================================
>Keep a back up of your OE settings and folders
>with OEBackup:
>http://www.oehelp.com/OEBackup/Default.aspx
>================================================
>
>
>.
>

Relevant Pages

  • Re: Event 5774 /DNS errors/Latest updates
    ... You did not need to reboot, all you needed to do was run the commands you ... > ipconfig /registerdns ... What DNS server is this? ...
    (microsoft.public.win2000.dns)
  • Re: A summery of some issues . . .
    ... DNS allow me to use a UNC? ... Or the clarification. ... > during net logon. ... > Point the DNS server to itself only then reboot and check the DNS zone. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Domain name at logon differs from the name of the domain
    ... In DNS manager right click on the zone, and look at "Allow Dynamic Updates" ... > but attempting to logon to it brings the error "no domain ... >>NetBIOS domain name, as this is part of SAM logon name. ... >>Microsoft MVP Windows Server - Active Directory ...
    (microsoft.public.win2000.active_directory)
  • Re: 2min or more delay longing on to domain with XP Pro SP2
    ... When you say that things changed with the fast logon optimization disabled, ... Certainly not DNS, ... >> As for logging, do you simply mean EVENT Viewer logging or ...
    (microsoft.public.win2000.active_directory)
  • Re: Please wait while the domain list is created
    ... Delayed logons are often a dns issue in that the computer is having a ... that W2K/XP Pro domain computers point ONLY to domain controllers running ... netdiag and dcdiag should be helpful to you. ... policy that can cause very long logon times and/or logon failures. ...
    (microsoft.public.windows.server.networking)