Re: NT4.0 bdc cannot access network after installation of Service pack on w2k DC

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

anonymous_at_discussions.microsoft.com
Date: 02/13/04 

Date: Fri, 13 Feb 2004 11:17:43 -0800

The DHCP server gives the clients in range 192.168.3.0
the w2k DC's address for DNS.

A Static IP gives the same problem!
The NT BDC has SP6a.

I can't find any errors concerning Wins replication in
the event log.
I already tried to install another w2k DC in range
192.168.3.0 , after installing a SP on the DC in range
192.168.1.0 this DC (in range 192.168.3.0) gives the same
problem as w2k clients in this range (stuck on dialog
box "performing network connections" on startup).

After uninstalling the SP everything worked fine again, I
found the following errors on the DC in range 192.168.3.0:

Event ID 7022 Netlogon service hung on startup
Event ID 7022 DHCP service hung on startup
Event ID 7022 WINS service hung on startup
>-----Original Message-----
>OK, is the NT4 bdc DHCP information giving the
192.168.3.x clients the
>w2kDC's address for DNS ?
>
>If the wk2 clients are configured with static ip
information that points to
>the w2kDC's address for DNS do they come up normally?
>
>It sounds like the WINS servers stop replicating after
the SP, can you
>verify this happens? Any event log entries to that
effect registered on the
>DC or pdc?
>
>Does the NT4 box have the latest SP?
>
>
>--
>Scott Baldridge
>Windows Server MVP, MCSE
>
>
>
>> the domain name is BE.EOCGROUP.COM
>>
>> >-----Original Message-----
>> >What is your domain name? For example, is it
DOMAIN.COM
>> or DOMAIN?
>> >
>> >--
>> >Scott Baldridge
>> >Windows Server MVP, MCSE
>> >
>> >
>> >
>> >"Lode Van Durme"
>> >> When I install SP2 - 3 or 4 on my w2k DC in range
>> >> 192.168.1.0 the NT4 bdc in range 192.168.3.0 cannot
>> access
>> >> the AD database anymore.
>> >> W2k clients in range 192.168.3.0 are stuck on
startup
>> with
>> >> the dialog box "preparing network connection"
>> >>
>> >> The w2k DC is DNS server for both ranges and he is
WINS
>> >> and DHCP server for range 192.168.1.0.
>> >> The NT4 bdc is WINS and DHCP for range 192.168.3.0
>> >>
>> >> When I uninstall the SP everything works fine again.
>> >>
>> >> What is the problem?
>> >>
>> >
>> >
>> >.
>> >
>
>
>.
>

Relevant Pages

  • RE: VPN Clients Not Registering in AD DNS
    ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
    (microsoft.public.windows.server.sbs)
  • Re: Permissions across 2 Forrest
    ... Primary DNS server on 1.x and the 18.x network along with DHCP and WINS. ... For instance ForrestA DNS is now a secondary for Forrest B and vise versa. ... WINS clients must use the same "WINS Database"* ...
    (microsoft.public.windows.server.active_directory)
  • Re: Still strange not fully working DNS server
    ... On none of the computers (both DC and clients) no firewall software is ... For the rest nothing happens in the DNS forward lookup zone. ... Is the new server Global catalog? ... The config you mentioned was not configured so I have configured ...
    (microsoft.public.windows.server.dns)
  • Re: Client installation frustration.
    ... not, apparently, any DNS lookup issues on my network. ... connection's addresses in DNS" and "Use this connection's DNS suffix in DNS ... is a file and print server that we have at one of our secondary sites. ... Is there any way to cancel all current requests to install clients? ...
    (microsoft.public.sms.admin)
  • Re: problem with xp clients and windows 2003
    ... We now have the cross cable running from the room's switch ... >> policy but logs into the server. ... >> aware that this is a DNS issue but I have TRIPLE checked the DNS ... >> If I do NSlookup from the problematic clients, ...
    (microsoft.public.windows.server.networking)