memory leak

  • Thread starter Thread starter KFS
  • Start date Start date
K

KFS

i have a network with 3 servers running w2k server. One of
them suddenly starts to leak memory and use high CPU. Then
it triggers the two others too. I have installed sp4 so
article kb821712 doesn't aplly to my problem. Is there a
way I can find out what makes the dns server use all
available memory and CPU?
 
In
KFS said:
i have a network with 3 servers running w2k server. One of
them suddenly starts to leak memory and use high CPU. Then
it triggers the two others too. I have installed sp4 so
article kb821712 doesn't aplly to my problem. Is there a
way I can find out what makes the dns server use all
available memory and CPU?
Click to expand...

Does your domain have a single label domain name? (domain vs. domain.com)
300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;300684&FR=1
 
I'read the article, but are not sure that I
understand "singel label domain" correctly. The domain
here is naah.no. i understand it like this is not a single
label domain name, does the article still describe my
problem? In the eventlog I have the error 5781 Netlogon
that the article describes.
Should I try to do what the article says?
Thanx, so far

regards,
Kim=)
 
In (e-mail address removed) <[email protected]>
posted a question
Then Kevin replied below:
I'read the article, but are not sure that I
understand "singel label domain" correctly. The domain
here is naah.no. i understand it like this is not a single
label domain name, does the article still describe my
problem? In the eventlog I have the error 5781 Netlogon
that the article describes.
Should I try to do what the article says?
Thanx, so far
Click to expand...
Not unless it is a single label domain, the reason I posted the article was
because you stated this started with SP4 which does cause 5781s and you gave
no other information to help you further. If you want further assistance I
will need an ipconfig /all and the domain name from ADU&C a netdiag
/test:dns /v will help, too.
 
Sorry about my poor explaining of the problem. Here comes
the ipconfig all:
Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : server2
Primary DNS Suffix . . . . . . . : NAAH.no
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : NAAH.no

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC3163 Fast
Ethernet NIC
Physical Address. . . . . . . . . : 00-02-A5-ED-A7-
A3
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.2
DNS Servers . . . . . . . . . . . : 192.168.1.103
192.168.2.101
Primary WINS Server . . . . . . . : 192.168.1.103
Secondary WINS Server . . . . . . : 192.168.1.101

The domain name from ADU&C is NAAH.NO
the netdiag command came up with this:
NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{B730F64E-40A3-4911-8655-92590DE62DD8}
1 NetBt transport currently configured.


DNS test . . . . . . . . . . . . . : Passed
Interface {B730F64E-40A3-4911-8655-92590DE62DD8}
DNS Domain:
DNS Servers: 192.168.1.103 192.168.2.101
IP Address: 192.168.1.101
Expected registration with PDN (primary DNS domain
name):
Hostname: server2.NAAH.no.
Authoritative zone: NAAH.no.
Primary DNS server: sbsserver.NAAH.no
192.168.1.103
Authoritative NS:192.168.1.100 192.168.1.103
192.168.1.101
Verify DNS registration:
Name: server2.NAAH.no
Expected IP: 192.168.1.101
Server 192.168.1.100: NO_ERROR
Server 192.168.1.103: NO_ERROR
Server 192.168.1.101: NO_ERROR
The DNS registration for server2.NAAH.no is correct on
all DNS servers
Check the DNS registration for DCs entries on DNS
server '192.168.1.103'
The Record is different on DNS server '192.168.1.103'.
DNS server has more than one entries for this name,
usually this means there are
multiple DCs for this domain.
Your DC entry is one of them on DNS
server '192.168.1.103', no need to re-regist
er.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.NAAH.no.
DNS DATA =
SRV 0 100 389 server2.NAAH.no.

The record on DNS server 192.168.1.103 is:
DNS NAME = _ldap._tcp.NAAH.no
DNS DATA =
SRV 0 100 389 server2.naah.no
SRV 0 100 389 sbsserver.naah.no
SRV 0 100 389 ntserver.naah
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.103'.
DNS server has more than one entries for this name,
usually this means there are
multiple DCs for this domain.
Your DC entry is one of them on DNS
server '192.168.1.103', no need to re-regist
er.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.1a271654-ddec-4cb0-9fc6-
37a218fa67b1.domains._msdcs.NAAH.n
o.
DNS DATA =
SRV 0 100 389 server2.NAAH.no.

The record on DNS server 192.168.1.103 is:
DNS NAME = _ldap._tcp.1a271654-ddec-4cb0-9fc6-
37a218fa67b1.domains._msdcs.NAAH.n
o
DNS DATA =
SRV 0 100 389 server2.naah.no
SRV 0 100 389 sbsserver.naah.no
SRV 0 100 389 ntserver.naah
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.103'.
DNS server has more than one entries for this name,
usually this means there are
multiple DCs for this domain.
Your DC entry is one of them on DNS
server '192.168.1.103', no need to re-regist
er.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.dc._msdcs.NAAH.no.
DNS DATA =
SRV 0 100 389 server2.NAAH.no.

The record on DNS server 192.168.1.103 is:
DNS NAME = _ldap._tcp.dc._msdcs.NAAH.no
DNS DATA =
SRV 0 100 389 server2.naah.no
SRV 0 100 389 sbsserver.naah.no
SRV 0 100 389 ntserver.naah
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.103'.
DNS server has more than one entries for this name,
usually this means there are
multiple DCs for this domain.
Your DC entry is one of them on DNS
server '192.168.1.103', no need to re-regist
er.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Default-First-Site-
Name._sites.NAAH.no.
DNS DATA =
SRV 0 100 389 server2.NAAH.no.

The record on DNS server 192.168.1.103 is:
DNS NAME = _ldap._tcp.Default-First-Site-
Name._sites.NAAH.no
DNS DATA =
SRV 0 100 389 server2.naah.no
SRV 0 100 389 sbsserver.naah.no
SRV 0 100 389 ntserver.naah
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.103'.
DNS server has more than one entries for this name,
usually this means there are
multiple DCs for this domain.
Your DC entry is one of them on DNS
server '192.168.1.103', no need to re-regist
er.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.dc._msdcs.NAAH.no.
DNS DATA =
SRV 0 100 88 server2.NAAH.no.

The record on DNS server 192.168.1.103 is:
DNS NAME = _kerberos._tcp.dc._msdcs.NAAH.no
DNS DATA =
SRV 0 100 88 server2.naah.no
SRV 0 100 88 sbsserver.naah.no
SRV 0 100 88 ntserver.naah
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.103'.
DNS server has more than one entries for this name,
usually this means there are
multiple DCs for this domain.
Your DC entry is one of them on DNS
server '192.168.1.103', no need to re-regist
er.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.Default-First-Site-
Name._sites.dc._msdcs.NAAH.no.
DNS DATA =
SRV 0 100 88 server2.NAAH.no.

The record on DNS server 192.168.1.103 is:
DNS NAME = _kerberos._tcp.Default-First-Site-
Name._sites.dc._msdcs.NAAH.no
DNS DATA =
SRV 0 100 88 server2.naah.no
SRV 0 100 88 sbsserver.naah.no
SRV 0 100 88 ntserver.naah
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.103'.
DNS server has more than one entries for this name,
usually this means there are
multiple DCs for this domain.
Your DC entry is one of them on DNS
server '192.168.1.103', no need to re-regist
er.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Default-First-Site-
Name._sites.dc._msdcs.NAAH.no.
DNS DATA =
SRV 0 100 389 server2.NAAH.no.

The record on DNS server 192.168.1.103 is:
DNS NAME = _ldap._tcp.Default-First-Site-
Name._sites.dc._msdcs.NAAH.no
DNS DATA =
SRV 0 100 389 server2.naah.no
SRV 0 100 389 sbsserver.naah.no
SRV 0 100 389 ntserver.naah
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.103'.
DNS server has more than one entries for this name,
usually this means there are
multiple DCs for this domain.
Your DC entry is one of them on DNS
server '192.168.1.103', no need to re-regist
er.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.NAAH.no.
DNS DATA =
SRV 0 100 88 server2.NAAH.no.

The record on DNS server 192.168.1.103 is:
DNS NAME = _kerberos._tcp.NAAH.no
DNS DATA =
SRV 0 100 88 server2.naah.no
SRV 0 100 88 sbsserver.naah.no
SRV 0 100 88 ntserver.naah
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.103'.
DNS server has more than one entries for this name,
usually this means there are
multiple DCs for this domain.
Your DC entry is one of them on DNS
server '192.168.1.103', no need to re-regist
er.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.Default-First-Site-
Name._sites.NAAH.no.
DNS DATA =
SRV 0 100 88 server2.NAAH.no.

The record on DNS server 192.168.1.103 is:
DNS NAME = _kerberos._tcp.Default-First-Site-
Name._sites.NAAH.no
DNS DATA =
SRV 0 100 88 server2.naah.no
SRV 0 100 88 sbsserver.naah.no
SRV 0 100 88 ntserver.naah
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.103'.
DNS server has more than one entries for this name,
usually this means there are
multiple DCs for this domain.
Your DC entry is one of them on DNS
server '192.168.1.103', no need to re-regist
er.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._udp.NAAH.no.
DNS DATA =
SRV 0 100 88 server2.NAAH.no.

The record on DNS server 192.168.1.103 is:
DNS NAME = _kerberos._udp.NAAH.no
DNS DATA =
SRV 0 100 88 server2.naah.no
SRV 0 100 88 sbsserver.naah.no
SRV 0 100 88 ntserver.naah
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.103'.
DNS server has more than one entries for this name,
usually this means there are
multiple DCs for this domain.
Your DC entry is one of them on DNS
server '192.168.1.103', no need to re-regist
er.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kpasswd._tcp.NAAH.no.
DNS DATA =
SRV 0 100 464 server2.NAAH.no.

The record on DNS server 192.168.1.103 is:
DNS NAME = _kpasswd._tcp.NAAH.no
DNS DATA =
SRV 0 100 464 server2.naah.no
SRV 0 100 464 sbsserver.naah.no
SRV 0 100 464 ntserver.naah
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.103'.
DNS server has more than one entries for this name,
usually this means there are
multiple DCs for this domain.
Your DC entry is one of them on DNS
server '192.168.1.103', no need to re-regist
er.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kpasswd._udp.NAAH.no.
DNS DATA =
SRV 0 100 464 server2.NAAH.no.

The record on DNS server 192.168.1.103 is:
DNS NAME = _kpasswd._udp.NAAH.no
DNS DATA =
SRV 0 100 464 server2.naah.no
SRV 0 100 464 sbsserver.naah.no
SRV 0 100 464 ntserver.naah
+------------------------------------------------------+

The Record is correct on DNS server '192.168.1.103'.

The Record is different on DNS server '192.168.1.103'.
DNS server has more than one entries for this name,
usually this means there are
multiple DCs for this domain.
Your DC entry is one of them on DNS
server '192.168.1.103', no need to re-regist
er.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = NAAH.no.
DNS DATA =
A 192.168.1.101

The record on DNS server 192.168.1.103 is:
DNS NAME = NAAH.no
DNS DATA =
A 192.168.1.101
A 192.168.1.100
A 192.168.1.103
+------------------------------------------------------+

PASS - All the DNS entries for DC are registered on
DNS server '192.168.1.10
3' and other DCs also have some of the names registered.
Check the DNS registration for DCs entries on DNS
server '192.168.2.101'
Query for DC DNS entry _ldap._tcp.NAAH.no. on DNS server
192.168.2.101 failed.
DNS Error code: ERROR_TIMEOUT (Dns server may be down.)
[WARNING] The DNS entries for this DC cannot be
verified right now on DNS
server 192.168.2.101, ERROR_TIMEOUT.


The command completed successfully

C:\>

Thanx again!

Kim=)
-----Original Message-----
In (e-mail address removed)
Click to expand...
 
There are 3 w2k servers in my network. One small business
2000, and to w2k servers. I noticed that one of the w2k
servers only hav a singel-label domain name. It's called
ntserver.naah, the two others are named sbsserver.naah.no
and server2.naah.no.
Is this causing my problems? What is the easiest way to
correct it?
Should i run dcpromo and demote ntserver, and give it the
correct name? ntserver is a domain controller together
with sbsserver (small business server 2000).

Thanx!

Kim=)
-----Original Message-----
In (e-mail address removed)
Click to expand...
 
In
Kim said:
Sorry about my poor explaining of the problem. Here comes
the ipconfig all:
Click to expand...

No problem, the problem seems to be on this machine that is for sure here is
the error:
Check the DNS registration for DCs entries on DNS
server '192.168.2.101'
Query for DC DNS entry _ldap._tcp.NAAH.no. on DNS server
192.168.2.101 failed.
DNS Error code: ERROR_TIMEOUT (Dns server may be down.)
[WARNING] The DNS entries for this DC cannot be
verified right now on DNS
server 192.168.2.101, ERROR_TIMEOUT.
Click to expand...

Do you have "Allow dynamic updates" set to "Yes"
If it is set to "Only secure updates" then the system needs permission to
update the zone. I don't know if that is the problem but you can look on the
Security tab on the zone properties to see what the permissions look like.

On other thing you can look at is what are the forwarders on this server. I
have seen cases, and this is true, where the forwarder has been set to one
of the other DNS servers in the domain, which if they are forwarding back to
this one it will set up a DNS loop which will cause the DNS server to fail.
Then that will cause 5781s because DNS has failed. The forwarder on all
machines should be to an ISP or to a DNS server that has no relation to this
one, such as a Caching only DNS server.
 
In
KFS said:
There are 3 w2k servers in my network. One small business
2000, and to w2k servers. I noticed that one of the w2k
servers only hav a singel-label domain name. It's called
ntserver.naah, the two others are named sbsserver.naah.no
and server2.naah.no.
Is this causing my problems? What is the easiest way to
correct it?
Should i run dcpromo and demote ntserver, and give it the
correct name? ntserver is a domain controller together
with sbsserver (small business server 2000).
Click to expand...

You know what I did not see that one, no it is not necessary to DCPROMO that
one it probably only needs the DNS suffix fixed on it if you will email me
direct I can send a script to fix that machine.

Can you provide an ipconfig /all for that machine?
If you email me direct please remove the nospam. from my email address.
 
The forwarders were set to pointing to the two other
servers. I removed this. But there is one thing I don't
understand, and that is where "Query for DC DNS entry
_ldap._tcp.NAAH.no. on DNS server
192.168.2.101 failed." comes from. We have no servers
with the adress 192.168.2.101. The server has the adress
1.101 not 2.101. I'tried to find out where it says 2, but
can't find it.

Thanx, again, you're extremely helpful
Kim=)
-----Original Message-----
In Kim <[email protected]> posted a question
Then Kevin replied below:
Sorry about my poor explaining of the problem. Here comes
the ipconfig all:
Click to expand...

No problem, the problem seems to be on this machine that is for sure here is
the error:
Check the DNS registration for DCs entries on DNS
server '192.168.2.101'
Query for DC DNS entry _ldap._tcp.NAAH.no. on DNS server
192.168.2.101 failed.
DNS Error code: ERROR_TIMEOUT (Dns server may be down.)
[WARNING] The DNS entries for this DC cannot be
verified right now on DNS
server 192.168.2.101, ERROR_TIMEOUT.
Click to expand...

Do you have "Allow dynamic updates" set to "Yes"
If it is set to "Only secure updates" then the system needs permission to
update the zone. I don't know if that is the problem but you can look on the
Security tab on the zone properties to see what the permissions look like.

On other thing you can look at is what are the forwarders on this server. I
have seen cases, and this is true, where the forwarder has been set to one
of the other DNS servers in the domain, which if they are forwarding back to
this one it will set up a DNS loop which will cause the DNS server to fail.
Then that will cause 5781s because DNS has failed. The forwarder on all
machines should be to an ISP or to a DNS server that has no relation to this
one, such as a Caching only DNS server.
Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : server2
Primary DNS Suffix . . . . . . . : NAAH.no
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : NAAH.no

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC3163 Fast
Ethernet NIC
Physical Address. . . . . . . . . : 00-02-A5- ED-A7-
A3
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.2
DNS Servers . . . . . . . . . . . : 192.168.1.103
192.168.2.101
Primary WINS Server . . . . . . . : 192.168.1.103
Secondary WINS Server . . . . . . : 192.168.1.101

The domain name from ADU&C is NAAH.NO
the netdiag command came up with this:
NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{B730F64E-40A3-4911-8655- 92590DE62DD8}
1 NetBt transport currently configured.
Click to expand...




.
Click to expand...
 
Supberb! I'll mail you tomorrow, when I'm back there.
have no terminalserver connection to that server so I
can't get it form where I am now.

Thanx
Kim=)
 
In
KFS said:
The forwarders were set to pointing to the two other
servers. I removed this. But there is one thing I don't
understand, and that is where "Query for DC DNS entry
_ldap._tcp.NAAH.no. on DNS server
192.168.2.101 failed." comes from. We have no servers
with the adress 192.168.2.101. The server has the adress
1.101 not 2.101. I'tried to find out where it says 2, but
can't find it.

Thanx, again, you're extremely helpful
Kim=)
Click to expand...
Duh, I must have my eyes closed on that one, I just looked through the
netdiag again and your config but you're right I don't no where netdiag
picked that up. But, it is there.

Does it appear on subsequent netdiags?
 
In
kfs said:
Supberb! I'll mail you tomorrow, when I'm back there.
have no terminalserver connection to that server so I
can't get it form where I am now.

Thanx
Kim=)
Click to expand...

I'll be watching my inbox.
 
it appears every time...
Any idea?

kim=)
-----Original Message-----
In KFS <[email protected]> posted a question
Then Kevin replied below:
Duh, I must have my eyes closed on that one, I just looked through the
netdiag again and your config but you're right I don't no where netdiag
picked that up. But, it is there.

Does it appear on subsequent netdiags?



.
Click to expand...
 
In
Kfs said:
it appears every time...
Any idea?
Click to expand...
Yea, I see it is in your ipconfig. that is the reason for the 5781 I'll
betcha.
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC3163 Fast
Ethernet NIC
Physical Address. . . . . . . . . : 00-02-A5-ED-A7-
A3
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.2
DNS Servers . . . . . . . . . . . : 192.168.1.103
192.168.2.101 <-----right here!
Primary WINS Server . . . . . . . : 192.168.1.103
Secondary WINS Server . . . . . . : 192.168.1.101
 
OOf, I feel bad, should have seen it.
Thanx again, and again and again...

Kim=)
-----Original Message-----
In Kfs <[email protected]> posted a question
Then Kevin replied below:
Yea, I see it is in your ipconfig. that is the reason for the 5781 I'll
betcha.
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC3163 Fast
Ethernet NIC
Physical Address. . . . . . . . . : 00-02-A5-ED- A7-
A3
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.2
DNS Servers . . . . . . . . . . . : 192.168.1.103
Click to expand...
192.168.2.101 <-----right here!
 
Back
Top