Problem with DC

  • Thread starter Thread starter Miha Bernik
  • Start date Start date
M

Miha Bernik

Hi

Can anyone please help me with that.. We have 2 DC (Win2k) in our network.
On the first one I get the following error in event viewer (application)

"Windows cannot obtain the domain controller name for your computer network.
Return value (2146). "

The error is displayed 3 times every day all in about 10 minutes. On the
second DC there are no errors! It's quite a big problem, becasue when error
appears, it freezes all users running applications on this DC.

I checked and all my DNS settings in TCP/IP have the following 'boxes
marked'
- append primary and connection specific DNS suffixes
- append parent suffixes
- DNS suffix for this connection: I have my domain entered GV.SI
- register this connections addresses in DNS
- use this connections DNS suffix in DNS registration


Please help !!!

Thanks in advance
Regards
Miha
 
I checked and all my DNS settings in TCP/IP have the following 'boxes
marked'
- append primary and connection specific DNS suffixes
- append parent suffixes
- DNS suffix for this connection: I have my domain entered GV.SI
- register this connections addresses in DNS
Click to expand...

Generally the above are NOT part of the problem.

The following MIGHT be but you have it set.
- use this connections DNS suffix in DNS registration
Click to expand...

Almost always, it's related to NOT setting the DNS server to
accept Dynamic registrations, not having the DCs point to this
Dynamic DNS server (even on the DNS server if it's a DC),
or having no-name or a one-tag name entered in the System
Control Panel for your Machine\Domain.

You need a name of the form: Machine.Domain.tld (tld= top
level domain, e.g., .Com or .Local etc.)

Names like this Machine.Domain or with no domain, don't work
right. 3 or more tag names are just cumbersome but they
to work just fine.
 
In
Miha Bernik said:
Hi

Can anyone please help me with that.. We have 2 DC (Win2k) in our
network. On the first one I get the following error in event viewer
(application)

"Windows cannot obtain the domain controller name for your computer
network. Return value (2146). "

The error is displayed 3 times every day all in about 10 minutes. On
the second DC there are no errors! It's quite a big problem, becasue
when error appears, it freezes all users running applications on
this DC.

I checked and all my DNS settings in TCP/IP have the following 'boxes
marked'
- append primary and connection specific DNS suffixes
- append parent suffixes
- DNS suffix for this connection: I have my domain entered GV.SI
- register this connections addresses in DNS
- use this connections DNS suffix in DNS registration
Click to expand...

What address is this machine using for DNS in its TCP/IP properties?
Can you post an ipconfig /all from both DCs?
 
Here you go... The first one is the 'problematic'. The second DC is also a
RAS server. Both DC are NS for internal use, and forward
all 'not-known' request to external DNS server located on 10.10.10.1

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : gorila
Primary DNS Suffix . . . . . . . : gv.si
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : gv.si

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : gv.si
Description . . . . . . . . . . . : Compaq NC3163 Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-02-A5-09-47-31
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.11
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.10.10.1
DNS Servers . . . . . . . . . . . : 10.10.10.11
10.10.10.183
Primary WINS Server . . . . . . . : 10.10.10.11
Secondary WINS Server . . . . . . : 10.10.10.49
----------------------------------------------------------------------------
-----------------------------

Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : Tiger
Primary DNS Suffix . . . . . . . : gv.si
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : gv.si

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : gv.si
Description . . . . . . . . . . . : Intel 82558-based Integrated Ethernet
with Wake on LAN
Physical Address. . . . . . . . . : 00-A0-C9-AC-03-7A
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.183
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.10.10.1
DNS Servers . . . . . . . . . . . : 10.10.10.183
10.10.10.11
Primary WINS Server . . . . . . . : 10.10.10.11
Secondary WINS Server . . . . . . : 10.10.10.49
 
In
posted their urgent concerns said:
Here you go... The first one is the 'problematic'. The second DC is
also a RAS server. Both DC are NS for internal use, and forward
all 'not-known' request to external DNS server located on 10.10.10.1

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : gorila
Primary DNS Suffix . . . . . . . : gv.si
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : gv.si

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : gv.si
Description . . . . . . . . . . . : Compaq NC3163 Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-02-A5-09-47-31
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.11
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.10.10.1
DNS Servers . . . . . . . . . . . : 10.10.10.11
10.10.10.183
Primary WINS Server . . . . . . . : 10.10.10.11
Secondary WINS Server . . . . . . : 10.10.10.49
-------------------------------------------------------------------------- --
-----------------------------

Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : Tiger
Primary DNS Suffix . . . . . . . : gv.si
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : gv.si

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : gv.si
Description . . . . . . . . . . . : Intel 82558-based Integrated
Ethernet with Wake on LAN
Physical Address. . . . . . . . . : 00-A0-C9-AC-03-7A
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.183
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.10.10.1
DNS Servers . . . . . . . . . . . : 10.10.10.183
10.10.10.11
Primary WINS Server . . . . . . . : 10.10.10.11
Secondary WINS Server . . . . . . : 10.10.10.49
Click to expand...

I'll jump in for Kevin...

Point to the partner DNS first, instead of itself, on both machines.
Make sure too that updates are set to Yes.

Can you post the Event log error? Post the Event ID# please and what service
pack you're using.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Thanks I'll try this. Do I need to uncheck in my DNS settings ''Use This
Connection's DNS Suffix in DNS registration' ??
I have Service Pack 3 (for Win2k) installed.
This is from my event log (app)

Windows cannot obtain the domain controller name for your computer network.
Return value (2146).
Source: Userenv Category: None EventID: 1000
 
Thanks I'll try this. Do I need to uncheck in my DNS settings ''Use This
Connection's DNS Suffix in DNS registration' ??
Click to expand...

Probably not. There is really no reason to HAVE a
Connection suffix entered IF IT WOULD be the same
as your correctly configured Domain name.

If you do enter it, then presumably you want it DIFFERENT
and presumably you had a reason for registering it because
it isn't used for much else.

I leave this setting EMPTY except when they:

1) Are Different
2) Need to be registered

Of course if you need it registered you must check the box
and vice versa.

Only machines I typically use this on are MULTIHOMED
machines where I want an additional registration for every
NIC so that I can use the DNS name instead of having to
go find the IP to address that particular NIC.

If it had only a SINGLE NIC, it probably would only use
the name of the Domain from System Properties.
 
Back
Top