DNS Forward Lookupzone "subfolders" missing

C

Count Blackula

Hi everybody.

I have a W2000 SP4 Server running as PDC with Active Directory. I wanted to
add a backup DC two days ago and could not do so because " The primary DC
for "Domain" could not be found". After some investigation i found out that
the Forward Lookup Zone on my PDC has no subfolders in the "domain zone".
Normally you should have those _MSDSC, _Sites, _TCP, _UDP folders but even
after deinstalling DNS and Reinstalling, flushing and registering ( multiple
times ) i cant get those folders. The DNS-Server itself works well, adding
clients to the Domain works and they get registered in DNS too. I think that
my AD is somehow "broken" but i dont know what the cause and what the effect
is ( DNS or AD) .
LAN settings are correct ( PDC has itself as DNS, and registering itself). I
also get event 5782 ( dynamic registration failed) although i have activated
dyn.reg in the Forward Lookup Zone. Any ideas on this?

Thanks in advance,

Milenko
 
M

Matt Anderson

Count Blackula said:
Hi everybody.

I have a W2000 SP4 Server running as PDC with Active Directory. I wanted
to
add a backup DC two days ago and could not do so because " The primary DC
for "Domain" could not be found". After some investigation i found out
that
the Forward Lookup Zone on my PDC has no subfolders in the "domain zone".
Normally you should have those _MSDSC, _Sites, _TCP, _UDP folders but even
after deinstalling DNS and Reinstalling, flushing and registering (
multiple
times ) i cant get those folders. The DNS-Server itself works well, adding
clients to the Domain works and they get registered in DNS too. I think
that
my AD is somehow "broken" but i dont know what the cause and what the
effect
is ( DNS or AD) .
LAN settings are correct ( PDC has itself as DNS, and registering itself).
I
also get event 5782 ( dynamic registration failed) although i have
activated
dyn.reg in the Forward Lookup Zone. Any ideas on this?

Thanks in advance,

Milenko
Click to expand...
Have you tried restarting the netlogon service?

Matt
MCT, MCSE
 
K

Kevin D. Goodknecht Sr. [MVP]

In
Count Blackula said:
Hi everybody.

I have a W2000 SP4 Server running as PDC with Active
Directory. I wanted to add a backup DC two days ago and
could not do so because " The primary DC for "Domain"
could not be found". After some investigation i found out
that the Forward Lookup Zone on my PDC has no subfolders
in the "domain zone". Normally you should have those
_MSDSC, _Sites, _TCP, _UDP folders but even after
deinstalling DNS and Reinstalling, flushing and
registering ( multiple times ) i cant get those folders.
The DNS-Server itself works well, adding clients to the
Domain works and they get registered in DNS too. I think
that my AD is somehow "broken" but i dont know what the
cause and what the effect is ( DNS or AD) .
LAN settings are correct ( PDC has itself as DNS, and
registering itself). I also get event 5782 ( dynamic
registration failed) although i have activated dyn.reg in
the Forward Lookup Zone. Any ideas on this?
Click to expand...

Is it pointing to its own address for DNS only?

Is the domain a single-label name, domain instead of domain.com?

Does the primary DNS suffix match the domain name and forward lookup zone
name?

Posting an ipconfig /all, list of zones in DNS, and domain name from ADUC
will answer these.
 
C

Count Blackula

Reply below
Kevin D. Goodknecht Sr. said:
In

Is it pointing to its own address for DNS only?
Yes.


Is the domain a single-label name, domain instead of domain.com?
Click to expand...

The AD-Domain Name is "domain.lan"
Does the primary DNS suffix match the domain name and forward lookup zone
name?
Click to expand...
Yes. The created Forward zone is called "domain.lan" and ipconfig gives me
"domain.lan" as DNS-Suffix
IP-Adresse. . . . . . . . . . . . : 192.168.150.21
Subnetzmaske. . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 192.168.150.1
DNS-Server. . . . . . . . . . . . : 192.168.150.21
Primärer WINS-Server. . . . . . . : 192.168.150.21

I have DNS-Forwarding to my routers DNS for external DNS requests. Hmm maybe
i should disable this temporarily? Ill try it...
Posting an ipconfig /all, list of zones in DNS, and domain name from ADUC
will answer these.
Click to expand...
Thanks in advance for your efforts.
 
K

Kevin D. Goodknecht Sr. [MVP]

In
The AD-Domain Name is "domain.lan"
Yes. The created Forward zone is called "domain.lan" and
ipconfig gives me "domain.lan" as DNS-Suffix
IP-Adresse. . . . . . . . . . . . : 192.168.150.21
Subnetzmaske. . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 192.168.150.1
DNS-Server. . . . . . . . . . . . : 192.168.150.21
Primärer WINS-Server. . . . . . . : 192.168.150.21

I have DNS-Forwarding to my routers DNS for external DNS
requests. Hmm maybe i should disable this temporarily?
Click to expand...
No, this should not make a difference on the forwarder.


Can you post the results from netdiag /v and dcdiag /v?
There is a post size limit so you'll have to use to posts.
 
C

Count Blackula

Ok here are the netdiag results:


Gathering IPX configuration information.
Querying status of the Netcard drivers... Passed
Testing IpConfig - pinging the Primary WINS server... Passed
Testing Domain membership... Passed
Gathering NetBT configuration information.
Testing for autoconfiguration... Passed
Testing IP loopback ping... Passed
Testing default gateways... Passed
Enumerating local and remote NetBT name cache... Passed
Testing the WINS server
LAN-Verbindung
Sending name query to primary WINS server 192.168.150.21 -
Passed
There is no secondary WINS server defined for this adapter.
Gathering Winsock information.
Testing DNS
The DNS registration for mido-pdc-01.MIDO-EDV.LAN is correct on
all DNS servers
[WARNING] The DNS entries for this DC are not registered correctly on
DNS server '192.168.150.21'. Please wait for 30 minutes for DNS server
replication.
[FATAL] No DNS servers have the DNS records for this DC registered.
Testing redirector and browser... Passed
Testing DC discovery.
Looking for a DC
Looking for a PDC emulator
Looking for a Windows 2000 DC
Gathering the list of Domain Controllers for domain 'MIDO-EDV'
Testing trust relationships... Skipped
Testing Kerberos authentication... Passed
Testing LDAP servers in Domain MIDO-EDV ...
Gathering routing information
Gathering network statistics information.
Gathering configuration of bindings.
Gathering RAS connection information
Gathering Modem information
Gathering Netware information
Gathering IP Security information

Tests complete.


Computer Name: MIDO-PDC-01
DNS Host Name: mido-pdc-01.MIDO-EDV.LAN
DNS Domain Name: MIDO-EDV.LAN
System info : Windows 2000 Server (Build 2195)
Processor : x86 Family 15 Model 3 Stepping 3, GenuineIntel
Hotfixes :
Installed? Name
Yes KB828028
Yes KB835732
Yes Q147222
Yes Q295688
No ServicePackUninstall


Netcard queries test . . . . . . . : Passed

Information of Netcard drivers:

------------------------------------------------------------------------
---
Description: Asynchroner RAS-Adapter
Device: \DEVICE\{47D94540-6CB2-4A34-9F4C-7BF6A6DC079C}

Media State: Connected

Device State: Connected
Connect Time: 00:09:00
Media Speed: 28 Kbps

Packets Sent: 0
Bytes Sent (Optional): 0

Packets Received: 0
Directed Pkts Recd (Optional): 0
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

[WARNING] The net card 'Asynchroner RAS-Adapter' may not be working
because it has not received any packets.
------------------------------------------------------------------------
---
Description: Parallelanschluss (direkt)
Device: \DEVICE\{DD66C6F1-7AA0-4E52-945B-B73051EDB428}
GetStats failed for 'Parallelanschluss (direkt)'. [ERROR_NOT_SUPPORTED]
------------------------------------------------------------------------
---
Description: WAN-Miniport (IP) - Paketplaner-Miniport
Device: \DEVICE\{86B17E12-CEB3-4F5D-9BB7-C982B7559CBE}

Media State: Connected

Device State: Connected
Connect Time: 02:42:05
Media Speed: 28 Kbps

Packets Sent: 0
Bytes Sent (Optional): 0

Packets Received: 0
Directed Pkts Recd (Optional): 0
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

[WARNING] The net card 'WAN-Miniport (IP) - Paketplaner-Miniport' may
not be working because it has not received any packets.
------------------------------------------------------------------------
---
Description: 3Com EtherLink XL 10/100-PCI-NIC (3C905-TX) #2 -
Paketplaner-Miniport
Device: \DEVICE\{B41BB8FA-F15C-42B6-8685-8002A69A156D}

Media State: Connected

Device State: Connected
Connect Time: 02:42:05
Media Speed: 100 Mbps

Packets Sent: 27362
Bytes Sent (Optional): 0

Packets Received: 34544
Directed Pkts Recd (Optional): 34474
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

Packets SendError: 3
Packets RecvError: 8
------------------------------------------------------------------------
---
Description: WAN-Miniport (PPTP)
Device: \DEVICE\{B0713803-B84B-4CA5-A369-2445865E9FC1}
GetStats failed for 'WAN-Miniport (PPTP)'. [ERROR_GEN_FAILURE]
------------------------------------------------------------------------
---
Description: WAN-Miniport (IP)
Device: \DEVICE\NDISWANIP

Media State: Connected

Device State: Connected
Connect Time: 02:42:05
Media Speed: 28 Kbps

Packets Sent: 0
Bytes Sent (Optional): 0

Packets Received: 0
Directed Pkts Recd (Optional): 0
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

[WARNING] The net card 'WAN-Miniport (IP)' may not be working because it
has not received any packets.
------------------------------------------------------------------------
---
Description: WAN-Miniport (L2TP)
Device: \DEVICE\{2D334E02-125A-4BAD-A318-68BB7EC98F24}
GetStats failed for 'WAN-Miniport (L2TP)'. [ERROR_NOT_SUPPORTED]
------------------------------------------------------------------------
---
Description: AVM NDIS WAN CAPI-Treiber
Device: \DEVICE\{9AA6EE09-2311-4214-A191-E4CC71F5650C}

Media State: Connected

Device State: Connected
Connect Time: 02:42:05
Media Speed: 6 Mbps

Packets Sent: 0
Bytes Sent (Optional): 0

Packets Received: 0
Directed Pkts Recd (Optional): 0
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

[WARNING] The net card 'AVM NDIS WAN CAPI-Treiber' may not be working
because it has not received any packets.
------------------------------------------------------------------------
---
Description: 3Com EtherLink XL 10/100-PCI-NIC (3C905-TX) #2
Device: \DEVICE\{0B7AE966-AD6C-435A-874C-7DB3383728AB}

Media State: Connected

Device State: Connected
Connect Time: 02:42:07
Media Speed: 100 Mbps

Packets Sent: 27362
Bytes Sent (Optional): 0

Packets Received: 34544
Directed Pkts Recd (Optional): 34474
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

Packets SendError: 3
Packets RecvError: 8
------------------------------------------------------------------------
---
[PASS] - At least one netcard is in the 'Connected' state.



Per interface results:

Adapter : LAN-Verbindung
Adapter ID . . . . . . . . : {0B7AE966-AD6C-435A-874C-7DB3383728AB}

Netcard queries test . . . : Passed

Adapter type . . . . . . . : Ethernet
Host Name. . . . . . . . . : mido-pdc-01
Description. . . . . . . . : 3Com 3C90x Ethernet Adapter
(Microsoft's Packet Scheduler)
Physical Address . . . . . : 00-60-08-63-E1-68
Dhcp Enabled . . . . . . . : No
DHCP ClassID . . . . . . . :
Autoconfiguration Enabled. : Yes
IP Address . . . . . . . . : 192.168.150.21
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.150.1
Primary WINS Server. . . . : 192.168.150.21
Dns Servers. . . . . . . . : 192.168.150.21

IpConfig results . . . . . : Passed
Pinging the Primary WINS server 192.168.150.21 - reachable

AutoConfiguration results. . . . . . : Passed
AutoConfiguration is not in use.

Default gateway test . . . : Passed
Pinging gateway 192.168.150.1 - reachable
At least one gateway reachable for this adapter.

NetBT name test. . . . . . : Passed
NetBT_Tcpip_{0B7AE966-AD6C-435A-874C-7DB3383728AB}
MIDO-PDC-01 <00> UNIQUE REGISTERED
MIDO-EDV <00> GROUP REGISTERED
MIDO-EDV <1C> GROUP REGISTERED
MIDO-PDC-01 <20> UNIQUE REGISTERED
MIDO-EDV <1B> UNIQUE REGISTERED
MIDO-EDV <1E> GROUP REGISTERED
MIDO-PDC-01 <03> UNIQUE REGISTERED
MIDO-EDV <1D> UNIQUE REGISTERED
..__MSBROWSE__.<01> GROUP REGISTERED
INet~Services <1C> GROUP REGISTERED
IS~MIDO-PDC-01.<00> UNIQUE REGISTERED
MIDO-PDC-01 <BE> UNIQUE REGISTERED
MILENKO <03> UNIQUE REGISTERED

NetBios Resolution : Enabled

Netbios Remote Cache Table
Name Type HostAddress Life [sec]
---------------------------------------------------------------
MIDO-LAP-01 <20> UNIQUE 192.168.150.91 375
MIDO-EDV <1C> GROUP 192.168.150.21 375


WINS service test. . . . . : Passed
Sending name query to primary WINS server 192.168.150.21 -
Passed
There is no secondary WINS server defined for this adapter.
The test was successful. At least one WINS server was found.
IPX test : IPX is not installed on this machine.


Global results:


IP General configuration
LMHOSTS Enabled. . . . . . . . : Yes
DNS for WINS resolution. . . . : Enabled
Node Type. . . . . . . . . . . : Hybrid
NBT Scope ID . . . . . . . . . :
Routing Enabled. . . . . . . . : No
WINS Proxy Enabled . . . . . . : No
DNS resolution for NETBIOS . . : No



Domain membership test . . . . . . : Passed
Machine is a . . . . . . . . . : Primary Domain Controller Emulator
Netbios Domain name. . . . . . : MIDO-EDV
Dns domain name. . . . . . . . : MIDO-EDV.LAN
Dns forest name. . . . . . . . : MIDO-EDV.LAN
Domain Guid. . . . . . . . . . : {9D5F4C63-B31C-4866-A90E-E9B8CDC9EF95}
Domain Sid . . . . . . . . . . :
S-1-5-21-1863046954-1157215732-1395582089
Logon User . . . . . . . . . . : milenko
Logon Domain . . . . . . . . . : MIDO-EDV


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{0B7AE966-AD6C-435A-874C-7DB3383728AB}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed
PASS - you have at least one non-autoconfigured IP address


IP loopback ping test. . . . . . . : Passed
PASS - pinging IP loopback address was successful.
Your IP stack is most probably OK.


Default gateway test . . . . . . . : Passed
PASS - you have at least one reachable gateway.


NetBT name test. . . . . . . . . . : Passed
No NetBT scope defined

PASS - The NetBT is properly configured.
There is at least one interface where the <00> 'WorkStation Service',
<03> 'Messenger Service', <20> 'WINS' names are defined and they are
not in conflict.


Winsock test . . . . . . . . . . . : Passed
The number of protocols which have been reported : 16
Description: MSAFD Tcpip [TCP/IP]
Provider Version :2
Max message size : Stream Oriented
Description: MSAFD Tcpip [UDP/IP]
Provider Version :2
Description: RSVP UDP Service Provider
Provider Version :4
Description: RSVP TCP Service Provider
Provider Version :4
Max message size : Stream Oriented
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{624E378E-5224-4119-B297-890DE704251D}] SEQPACKET 20
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{624E378E-5224-4119-B297-890DE704251D}] DATAGRAM 20
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{0B7AE966-AD6C-435A-874C-7DB3383728AB}] SEQPACKET 3
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{0B7AE966-AD6C-435A-874C-7DB3383728AB}] DATAGRAM 3
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{40D991D7-E430-4F91-BEA1-2BDDA308CD12}] SEQPACKET 1
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{40D991D7-E430-4F91-BEA1-2BDDA308CD12}] DATAGRAM 1
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{4CCC4FB0-4736-471B-BC8B-66C44CDB1350}] SEQPACKET 2
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{4CCC4FB0-4736-471B-BC8B-66C44CDB1350}] DATAGRAM 2
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{48941FCC-1E8A-4B3C-8C84-1DBEA1C2CAF6}] SEQPACKET 9
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{48941FCC-1E8A-4B3C-8C84-1DBEA1C2CAF6}] DATAGRAM 9
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{4BE148B1-5584-432F-97FB-6894D6E85650}] SEQPACKET 10
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{4BE148B1-5584-432F-97FB-6894D6E85650}] DATAGRAM 10
Provider Version :2

Max UDP size : 65507 bytes


DNS test . . . . . . . . . . . . . : Failed
Interface {0B7AE966-AD6C-435A-874C-7DB3383728AB}
DNS Domain:
DNS Servers: 192.168.150.21
IP Address: 192.168.150.21
Expected registration with PDN (primary DNS domain name):
Hostname: mido-pdc-01.MIDO-EDV.LAN.
Authoritative zone: MIDO-EDV.LAN.
Primary DNS server: mido-pdc-01.MIDO-EDV.LAN 192.168.150.21
Authoritative NS:192.168.150.21
Verify DNS registration:
Name: mido-pdc-01.MIDO-EDV.LAN
Expected IP: 192.168.150.21
Server 192.168.150.21: NO_ERROR
The DNS registration for mido-pdc-01.MIDO-EDV.LAN is correct on all DNS
servers
Check the DNS registration for DCs entries on DNS server '192.168.150.21'
Query for DC DNS entry MIDO-EDV.LAN. on DNS server 192.168.150.21 failed.
DNS Error code: 0x0000251D
Query for DC DNS entry _ldap._tcp.MIDO-EDV.LAN. on DNS server 192.168.150.21
failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)
Query for DC DNS entry
_ldap._tcp.Standardname-des-ersten-Standorts._sites.MIDO-EDV.LAN. on DNS
server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)
Query for DC DNS entry _ldap._tcp.pdc._msdcs.MIDO-EDV.LAN. on DNS server
192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)
Query for DC DNS entry _ldap._tcp.gc._msdcs.MIDO-EDV.LAN. on DNS server
192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)
Query for DC DNS entry
_ldap._tcp.Standardname-des-ersten-Standorts._sites.gc._msdcs.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)
Query for DC DNS entry
_ldap._tcp.9d5f4c63-b31c-4866-a90e-e9b8cdc9ef95.domains._msdcs.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)
Query for DC DNS entry gc._msdcs.MIDO-EDV.LAN. on DNS server 192.168.150.21
failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)
Query for DC DNS entry
29d41657-b087-46c7-87c4-2c1bd658c063._msdcs.MIDO-EDV.LAN. on DNS server
192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)
Query for DC DNS entry _kerberos._tcp.dc._msdcs.MIDO-EDV.LAN. on DNS server
192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)
Query for DC DNS entry
_kerberos._tcp.Standardname-des-ersten-Standorts._sites.dc._msdcs.MIDO-EDV.L
AN. on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)
Query for DC DNS entry _ldap._tcp.dc._msdcs.MIDO-EDV.LAN. on DNS server
192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)
Query for DC DNS entry
_ldap._tcp.Standardname-des-ersten-Standorts._sites.dc._msdcs.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)
Query for DC DNS entry _kerberos._tcp.MIDO-EDV.LAN. on DNS server
192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)
Query for DC DNS entry
_kerberos._tcp.Standardname-des-ersten-Standorts._sites.MIDO-EDV.LAN. on DNS
server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)
Query for DC DNS entry _gc._tcp.MIDO-EDV.LAN. on DNS server 192.168.150.21
failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)
Query for DC DNS entry
_gc._tcp.Standardname-des-ersten-Standorts._sites.MIDO-EDV.LAN. on DNS
server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)
Query for DC DNS entry _kerberos._udp.MIDO-EDV.LAN. on DNS server
192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)
Query for DC DNS entry _kpasswd._tcp.MIDO-EDV.LAN. on DNS server
192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)
Query for DC DNS entry _kpasswd._udp.MIDO-EDV.LAN. on DNS server
192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)
[WARNING] The DNS entries for this DC are not registered correctly on
DNS server '192.168.150.21'. Please wait for 30 minutes for DNS server
replication.
[FATAL] No DNS servers have the DNS records for this DC registered.


Redir and Browser test . . . . . . : Passed
List of transports currently bound to the Redir
NetbiosSmb
NetBT_Tcpip_{0B7AE966-AD6C-435A-874C-7DB3383728AB}
The redir is bound to 1 NetBt transport.

List of transports currently bound to the browser
NetBT_Tcpip_{0B7AE966-AD6C-435A-874C-7DB3383728AB}
The browser is bound to 1 NetBt transport.
Mailslot test for MIDO-EDV* passed.


DC discovery test. . . . . . . . . : Passed

Find DC in domain 'MIDO-EDV':
Found this DC in domain 'MIDO-EDV':
DC. . . . . . . . . . . : \\mido-pdc-01.MIDO-EDV.LAN
Address . . . . . . . . : \\192.168.150.21
Domain Guid . . . . . . : {9D5F4C63-B31C-4866-A90E-E9B8CDC9EF95}
Domain Name . . . . . . : MIDO-EDV.LAN
Forest Name . . . . . . : MIDO-EDV.LAN
DC Site Name. . . . . . : Standardname-des-ersten-Standorts
Our Site Name . . . . . : Standardname-des-ersten-Standorts
Flags . . . . . . . . . : PDC emulator GC DS KDC TIMESERV WRITABLE
DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8

Find PDC emulator in domain 'MIDO-EDV':
Found this PDC emulator in domain 'MIDO-EDV':
DC. . . . . . . . . . . : \\mido-pdc-01.MIDO-EDV.LAN
Address . . . . . . . . : \\192.168.150.21
Domain Guid . . . . . . : {9D5F4C63-B31C-4866-A90E-E9B8CDC9EF95}
Domain Name . . . . . . : MIDO-EDV.LAN
Forest Name . . . . . . : MIDO-EDV.LAN
DC Site Name. . . . . . : Standardname-des-ersten-Standorts
Our Site Name . . . . . : Standardname-des-ersten-Standorts
Flags . . . . . . . . . : PDC emulator GC DS KDC TIMESERV WRITABLE
DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8

Find Windows 2000 DC in domain 'MIDO-EDV':
Found this Windows 2000 DC in domain 'MIDO-EDV':
DC. . . . . . . . . . . : \\mido-pdc-01.MIDO-EDV.LAN
Address . . . . . . . . : \\192.168.150.21
Domain Guid . . . . . . : {9D5F4C63-B31C-4866-A90E-E9B8CDC9EF95}
Domain Name . . . . . . : MIDO-EDV.LAN
Forest Name . . . . . . : MIDO-EDV.LAN
DC Site Name. . . . . . : Standardname-des-ersten-Standorts
Our Site Name . . . . . : Standardname-des-ersten-Standorts
Flags . . . . . . . . . : PDC emulator GC DS KDC TIMESERV WRITABLE
DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8


DC list test . . . . . . . . . . . : Passed
List of DCs in Domain 'MIDO-EDV':
mido-pdc-01.MIDO-EDV.LAN


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed
Cached Tickets:
Server: krbtgt/MIDO-EDV.LAN
End Time: 11/26/2004 18:53:19
Renew Time: 12/3/2004 8:53:19
Server: krbtgt/MIDO-EDV.LAN
End Time: 11/26/2004 18:53:19
Renew Time: 12/3/2004 8:53:19
Server: MIDO-PDC-01$
End Time: 11/26/2004 18:53:19
Renew Time: 12/3/2004 8:53:19
Server: ldap/mido-pdc-01.MIDO-EDV.LAN/MIDO-EDV.LAN
End Time: 11/26/2004 18:53:19
Renew Time: 12/3/2004 8:53:19


LDAP test. . . . . . . . . . . . . : Passed

Do un-authenticated LDAP call to 'mido-pdc-01.MIDO-EDV.LAN'.
Found 1 entries:
Attr: currentTime
Val: 17 20041126081909.0Z
Attr: subschemaSubentry
Val: 58
CN=Aggregate,CN=Schema,CN=Configuration,DC=MIDO-EDV,DC=LAN
Attr: dsServiceName
Val: 124 CN=NTDS
Settings,CN=MIDO-PDC-01,CN=Servers,CN=Standardname-des-ersten-Standorts,CN=S
ites,CN=Configuration,DC=MIDO-EDV,DC=LAN
Attr: namingContexts
Val: 45 CN=Schema,CN=Configuration,DC=MIDO-EDV,DC=LAN
Val: 35 CN=Configuration,DC=MIDO-EDV,DC=LAN
Val: 18 DC=MIDO-EDV,DC=LAN
Attr: defaultNamingContext
Val: 18 DC=MIDO-EDV,DC=LAN
Attr: schemaNamingContext
Val: 45 CN=Schema,CN=Configuration,DC=MIDO-EDV,DC=LAN
Attr: configurationNamingContext
Val: 35 CN=Configuration,DC=MIDO-EDV,DC=LAN
Attr: rootDomainNamingContext
Val: 18 DC=MIDO-EDV,DC=LAN
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 16 MaxActiveQueries
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Attr: highestCommittedUSN
Val: 5 12285
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Attr: dnsHostName
Val: 24 mido-pdc-01.MIDO-EDV.LAN
Attr: ldapServiceName
Val: 38 MIDO-EDV.LAN:[email protected]
Attr: serverName
Val: 107
CN=MIDO-PDC-01,CN=Servers,CN=Standardname-des-ersten-Standorts,CN=Sites,CN=C
onfiguration,DC=MIDO-EDV,DC=LAN
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 4 TRUE

Do NTLM authenticated LDAP call to 'mido-pdc-01.MIDO-EDV.LAN'.
Found 1 entries:
Attr: currentTime
Val: 17 20041126081909.0Z
Attr: subschemaSubentry
Val: 58
CN=Aggregate,CN=Schema,CN=Configuration,DC=MIDO-EDV,DC=LAN
Attr: dsServiceName
Val: 124 CN=NTDS
Settings,CN=MIDO-PDC-01,CN=Servers,CN=Standardname-des-ersten-Standorts,CN=S
ites,CN=Configuration,DC=MIDO-EDV,DC=LAN
Attr: namingContexts
Val: 45 CN=Schema,CN=Configuration,DC=MIDO-EDV,DC=LAN
Val: 35 CN=Configuration,DC=MIDO-EDV,DC=LAN
Val: 18 DC=MIDO-EDV,DC=LAN
Attr: defaultNamingContext
Val: 18 DC=MIDO-EDV,DC=LAN
Attr: schemaNamingContext
Val: 45 CN=Schema,CN=Configuration,DC=MIDO-EDV,DC=LAN
Attr: configurationNamingContext
Val: 35 CN=Configuration,DC=MIDO-EDV,DC=LAN
Attr: rootDomainNamingContext
Val: 18 DC=MIDO-EDV,DC=LAN
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 16 MaxActiveQueries
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Attr: highestCommittedUSN
Val: 5 12285
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Attr: dnsHostName
Val: 24 mido-pdc-01.MIDO-EDV.LAN
Attr: ldapServiceName
Val: 38 MIDO-EDV.LAN:[email protected]
Attr: serverName
Val: 107
CN=MIDO-PDC-01,CN=Servers,CN=Standardname-des-ersten-Standorts,CN=Sites,CN=C
onfiguration,DC=MIDO-EDV,DC=LAN
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 4 TRUE

Do Negotiate authenticated LDAP call to 'mido-pdc-01.MIDO-EDV.LAN'.
Found 1 entries:
Attr: currentTime
Val: 17 20041126081909.0Z
Attr: subschemaSubentry
Val: 58
CN=Aggregate,CN=Schema,CN=Configuration,DC=MIDO-EDV,DC=LAN
Attr: dsServiceName
Val: 124 CN=NTDS
Settings,CN=MIDO-PDC-01,CN=Servers,CN=Standardname-des-ersten-Standorts,CN=S
ites,CN=Configuration,DC=MIDO-EDV,DC=LAN
Attr: namingContexts
Val: 45 CN=Schema,CN=Configuration,DC=MIDO-EDV,DC=LAN
Val: 35 CN=Configuration,DC=MIDO-EDV,DC=LAN
Val: 18 DC=MIDO-EDV,DC=LAN
Attr: defaultNamingContext
Val: 18 DC=MIDO-EDV,DC=LAN
Attr: schemaNamingContext
Val: 45 CN=Schema,CN=Configuration,DC=MIDO-EDV,DC=LAN
Attr: configurationNamingContext
Val: 35 CN=Configuration,DC=MIDO-EDV,DC=LAN
Attr: rootDomainNamingContext
Val: 18 DC=MIDO-EDV,DC=LAN
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 16 MaxActiveQueries
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Attr: highestCommittedUSN
Val: 5 12285
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Attr: dnsHostName
Val: 24 mido-pdc-01.MIDO-EDV.LAN
Attr: ldapServiceName
Val: 38 MIDO-EDV.LAN:[email protected]
Attr: serverName
Val: 107
CN=MIDO-PDC-01,CN=Servers,CN=Standardname-des-ersten-Standorts,CN=Sites,CN=C
onfiguration,DC=MIDO-EDV,DC=LAN
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 4 TRUE

Registered Service Principal Names:
SMTPSVC/MIDO-PDC-01
SMTPSVC/mido-pdc-01.MIDO-EDV.LAN
NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/mido-pdc-01.MIDO-EDV.LAN
DNS/mido-pdc-01.MIDO-EDV.LAN
GC/mido-pdc-01.MIDO-EDV.LAN/MIDO-EDV.LAN
HOST/mido-pdc-01.MIDO-EDV.LAN/MIDO-EDV
HOST/MIDO-PDC-01
HOST/mido-pdc-01.MIDO-EDV.LAN
HOST/mido-pdc-01.MIDO-EDV.LAN/MIDO-EDV.LAN

E3514235-4B06-11D1-AB04-00C04FC2DCD2/29d41657-b087-46c7-87c4-2c1bd658c063/MI
DO-EDV.LAN
LDAP/29d41657-b087-46c7-87c4-2c1bd658c063._msdcs.MIDO-EDV.LAN
LDAP/mido-pdc-01.MIDO-EDV.LAN/MIDO-EDV
LDAP/MIDO-PDC-01
LDAP/mido-pdc-01.MIDO-EDV.LAN
LDAP/mido-pdc-01.MIDO-EDV.LAN/MIDO-EDV.LAN


Routing table test . . . . . . . . : Passed
Active Routes :
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.150.1 192.168.150.21
1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
127.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1
1
192.168.150.0 255.255.255.0 192.168.150.21 192.168.150.21
1
192.168.150.21 255.255.255.255 127.0.0.1 127.0.0.1
1
224.0.0.0 240.0.0.0 192.168.150.21 192.168.150.21
1
255.255.255.255 255.255.255.255 192.168.150.21 192.168.150.21
1
No persistent route entries.


Netstat information test . . . . . : Passed


Interface Statistics

Received Sent
Unicast Packets 10862155 4777767
Non-unicast packets 267 204
Discards 0 0
Errors 0 2
Unknown protocols 1 457224

Interface index = 1
Description = Interne Loopback-Schnittstelle des
127.0.0-Netzwerks
Type = 24
MTU = 32768
Speed = 10000000
Physical Address = 00-00-00-00-00-00
Administrative Status = 1
Operational Status = 1
Last Changed = 0
Output Queue Length = 0


Interface index = 16777219
Description = 3Com 3C90x Ethernet Adapter (Microsoft's
Packet Scheduler)
Type = 6
MTU = 1500
Speed = 100000000
Physical Address = 00-60-08-63-E1-68
Administrative Status = 1
Operational Status = 1
Last Changed = 3281783043
Output Queue Length = 0



Active Connections

Proto Local Address Foreign Address
State
TCP mido-pdc-01:echo mido-pdc-01.MIDO-EDV.LAN:51370
LISTENING
TCP mido-pdc-01:discard mido-pdc-01.MIDO-EDV.LAN:59575
LISTENING
TCP mido-pdc-01:daytime mido-pdc-01.MIDO-EDV.LAN:26788
LISTENING
TCP mido-pdc-01:qotd mido-pdc-01.MIDO-EDV.LAN:18558
LISTENING
TCP mido-pdc-01:chargen mido-pdc-01.MIDO-EDV.LAN:51345
LISTENING
TCP mido-pdc-01:ftp mido-pdc-01.MIDO-EDV.LAN:10308
LISTENING
TCP mido-pdc-01:smtp mido-pdc-01.MIDO-EDV.LAN:59522
LISTENING
TCP mido-pdc-01:nameserver mido-pdc-01.MIDO-EDV.LAN:34844
LISTENING
TCP mido-pdc-01:domain mido-pdc-01.MIDO-EDV.LAN:18478
LISTENING
TCP mido-pdc-01:http mido-pdc-01.MIDO-EDV.LAN:2064
LISTENING
TCP mido-pdc-01:kerberos mido-pdc-01.MIDO-EDV.LAN:10293
LISTENING
TCP mido-pdc-01:90 mido-pdc-01.MIDO-EDV.LAN:26648
LISTENING
TCP mido-pdc-01:epmap mido-pdc-01.MIDO-EDV.LAN:51366
LISTENING
TCP mido-pdc-01:267 mido-pdc-01.MIDO-EDV.LAN:51303
LISTENING
TCP mido-pdc-01:ldap mido-pdc-01.MIDO-EDV.LAN:26663
LISTENING
TCP mido-pdc-01:https mido-pdc-01.MIDO-EDV.LAN:26810
LISTENING
TCP mido-pdc-01:microsoft-ds mido-pdc-01.MIDO-EDV.LAN:18523
LISTENING
TCP mido-pdc-01:kpasswd mido-pdc-01.MIDO-EDV.LAN:26857
LISTENING
TCP mido-pdc-01:593 mido-pdc-01.MIDO-EDV.LAN:35043
LISTENING
TCP mido-pdc-01:ldaps mido-pdc-01.MIDO-EDV.LAN:10468
LISTENING
TCP mido-pdc-01:1026 mido-pdc-01.MIDO-EDV.LAN:34988
LISTENING
TCP mido-pdc-01:1029 mido-pdc-01.MIDO-EDV.LAN:18446
LISTENING
TCP mido-pdc-01:1041 mido-pdc-01.MIDO-EDV.LAN:26711
LISTENING
TCP mido-pdc-01:1061 mido-pdc-01.MIDO-EDV.LAN:2272
LISTENING
TCP mido-pdc-01:1070 mido-pdc-01.MIDO-EDV.LAN:51377
LISTENING
TCP mido-pdc-01:1071 mido-pdc-01.MIDO-EDV.LAN:18503
LISTENING
TCP mido-pdc-01:1072 mido-pdc-01.MIDO-EDV.LAN:10347
LISTENING
TCP mido-pdc-01:1073 mido-pdc-01.MIDO-EDV.LAN:10482
LISTENING
TCP mido-pdc-01:1078 mido-pdc-01.MIDO-EDV.LAN:10349
LISTENING
TCP mido-pdc-01:1081 mido-pdc-01.MIDO-EDV.LAN:18602
LISTENING
TCP mido-pdc-01:1084 mido-pdc-01.MIDO-EDV.LAN:26843
LISTENING
TCP mido-pdc-01:1086 mido-pdc-01.MIDO-EDV.LAN:2208
LISTENING
TCP mido-pdc-01:1095 mido-pdc-01.MIDO-EDV.LAN:51337
LISTENING
TCP mido-pdc-01:1096 mido-pdc-01.MIDO-EDV.LAN:2256
LISTENING
TCP mido-pdc-01:1099 mido-pdc-01.MIDO-EDV.LAN:43029
LISTENING
TCP mido-pdc-01:1111 mido-pdc-01.MIDO-EDV.LAN:26877
LISTENING
TCP mido-pdc-01:1118 mido-pdc-01.MIDO-EDV.LAN:2160
LISTENING
TCP mido-pdc-01:1137 mido-pdc-01.MIDO-EDV.LAN:51271
LISTENING
TCP mido-pdc-01:1164 mido-pdc-01.MIDO-EDV.LAN:2107
LISTENING
TCP mido-pdc-01:1184 mido-pdc-01.MIDO-EDV.LAN:34957
LISTENING
TCP mido-pdc-01:1470 mido-pdc-01.MIDO-EDV.LAN:18615
LISTENING
TCP mido-pdc-01:1494 mido-pdc-01.MIDO-EDV.LAN:43208
LISTENING
TCP mido-pdc-01:1499 mido-pdc-01.MIDO-EDV.LAN:34819
LISTENING
TCP mido-pdc-01:1535 mido-pdc-01.MIDO-EDV.LAN:2208
LISTENING
TCP mido-pdc-01:pptp mido-pdc-01.MIDO-EDV.LAN:34914
LISTENING
TCP mido-pdc-01:1775 mido-pdc-01.MIDO-EDV.LAN:34855
LISTENING
TCP mido-pdc-01:1777 mido-pdc-01.MIDO-EDV.LAN:10389
LISTENING
TCP mido-pdc-01:1779 mido-pdc-01.MIDO-EDV.LAN:18478
LISTENING
TCP mido-pdc-01:1786 mido-pdc-01.MIDO-EDV.LAN:26821
LISTENING
TCP mido-pdc-01:1788 mido-pdc-01.MIDO-EDV.LAN:2272
LISTENING
TCP mido-pdc-01:1798 mido-pdc-01.MIDO-EDV.LAN:18451
LISTENING
TCP mido-pdc-01:1799 mido-pdc-01.MIDO-EDV.LAN:2224
LISTENING
TCP mido-pdc-01:1800 mido-pdc-01.MIDO-EDV.LAN:26808
LISTENING
TCP mido-pdc-01:1801 mido-pdc-01.MIDO-EDV.LAN:51385
LISTENING
TCP mido-pdc-01:1802 mido-pdc-01.MIDO-EDV.LAN:2232
LISTENING
TCP mido-pdc-01:1803 mido-pdc-01.MIDO-EDV.LAN:43254
LISTENING
TCP mido-pdc-01:1809 mido-pdc-01.MIDO-EDV.LAN:35013
LISTENING
TCP mido-pdc-01:1818 mido-pdc-01.MIDO-EDV.LAN:43076
LISTENING
TCP mido-pdc-01:1819 mido-pdc-01.MIDO-EDV.LAN:2208
LISTENING
TCP mido-pdc-01:1820 mido-pdc-01.MIDO-EDV.LAN:18510
LISTENING
TCP mido-pdc-01:1822 mido-pdc-01.MIDO-EDV.LAN:2101
LISTENING
TCP mido-pdc-01:1829 mido-pdc-01.MIDO-EDV.LAN:26712
LISTENING
TCP mido-pdc-01:1833 mido-pdc-01.MIDO-EDV.LAN:34892
LISTENING
TCP mido-pdc-01:1838 mido-pdc-01.MIDO-EDV.LAN:10380
LISTENING
TCP mido-pdc-01:1840 mido-pdc-01.MIDO-EDV.LAN:2112
LISTENING
TCP mido-pdc-01:1841 mido-pdc-01.MIDO-EDV.LAN:35044
LISTENING
TCP mido-pdc-01:1843 mido-pdc-01.MIDO-EDV.LAN:43013
LISTENING
TCP mido-pdc-01:1846 mido-pdc-01.MIDO-EDV.LAN:59574
LISTENING
TCP mido-pdc-01:1848 mido-pdc-01.MIDO-EDV.LAN:43164
LISTENING
TCP mido-pdc-01:1852 mido-pdc-01.MIDO-EDV.LAN:26819
LISTENING
TCP mido-pdc-01:1853 mido-pdc-01.MIDO-EDV.LAN:43186
LISTENING
TCP mido-pdc-01:1857 mido-pdc-01.MIDO-EDV.LAN:34983
LISTENING
TCP mido-pdc-01:1861 mido-pdc-01.MIDO-EDV.LAN:51212
LISTENING
TCP mido-pdc-01:1885 mido-pdc-01.MIDO-EDV.LAN:2295
LISTENING
TCP mido-pdc-01:1886 mido-pdc-01.MIDO-EDV.LAN:10241
LISTENING
TCP mido-pdc-01:1921 mido-pdc-01.MIDO-EDV.LAN:18462
LISTENING
TCP mido-pdc-01:1980 mido-pdc-01.MIDO-EDV.LAN:2192
LISTENING
TCP mido-pdc-01:2024 mido-pdc-01.MIDO-EDV.LAN:34828
LISTENING
TCP mido-pdc-01:3268 mido-pdc-01.MIDO-EDV.LAN:2192
LISTENING
TCP mido-pdc-01:3269 mido-pdc-01.MIDO-EDV.LAN:34908
LISTENING
TCP mido-pdc-01:3372 mido-pdc-01.MIDO-EDV.LAN:35063
LISTENING
TCP mido-pdc-01:3389 mido-pdc-01.MIDO-EDV.LAN:18589
LISTENING
TCP mido-pdc-01:3628 mido-pdc-01.MIDO-EDV.LAN:18478
LISTENING
TCP mido-pdc-01:5005 mido-pdc-01.MIDO-EDV.LAN:10269
LISTENING
TCP mido-pdc-01:5168 mido-pdc-01.MIDO-EDV.LAN:2080
LISTENING
TCP mido-pdc-01:5169 mido-pdc-01.MIDO-EDV.LAN:51227
LISTENING
TCP mido-pdc-01:5800 mido-pdc-01.MIDO-EDV.LAN:43078
LISTENING
TCP mido-pdc-01:5900 mido-pdc-01.MIDO-EDV.LAN:10359
LISTENING
TCP mido-pdc-01:6101 mido-pdc-01.MIDO-EDV.LAN:59516
LISTENING
TCP mido-pdc-01:6881 mido-pdc-01.MIDO-EDV.LAN:18597
LISTENING
TCP mido-pdc-01:6969 mido-pdc-01.MIDO-EDV.LAN:43237
LISTENING
TCP mido-pdc-01:11798 mido-pdc-01.MIDO-EDV.LAN:2153
LISTENING
TCP mido-pdc-01:ldap mido-pdc-01.MIDO-EDV.LAN:1070
ESTABLISHED
TCP mido-pdc-01:ldap mido-pdc-01.MIDO-EDV.LAN:1071
ESTABLISHED
TCP mido-pdc-01:ldap mido-pdc-01.MIDO-EDV.LAN:1073
ESTABLISHED
TCP mido-pdc-01:ldap mido-pdc-01.MIDO-EDV.LAN:1499
FIN_WAIT_2
TCP mido-pdc-01:ldap mido-pdc-01.MIDO-EDV.LAN:1885
ESTABLISHED
TCP mido-pdc-01:microsoft-ds mido-pdc-01.MIDO-EDV.LAN:1061
ESTABLISHED
TCP mido-pdc-01:1061 mido-pdc-01.MIDO-EDV.LAN:microsoft-ds
ESTABLISHED
TCP mido-pdc-01:1070 mido-pdc-01.MIDO-EDV.LAN:ldap
ESTABLISHED
TCP mido-pdc-01:1071 mido-pdc-01.MIDO-EDV.LAN:ldap
ESTABLISHED
TCP mido-pdc-01:1073 mido-pdc-01.MIDO-EDV.LAN:ldap
ESTABLISHED
TCP mido-pdc-01:1499 mido-pdc-01.MIDO-EDV.LAN:ldap
CLOSE_WAIT
TCP mido-pdc-01:1521 mido-pdc-01.MIDO-EDV.LAN:18649
LISTENING
TCP mido-pdc-01:1534 mido-pdc-01.MIDO-EDV.LAN:10264
LISTENING
TCP mido-pdc-01:1534 mido-pdc-01.MIDO-EDV.LAN:1535
ESTABLISHED
TCP mido-pdc-01:1535 mido-pdc-01.MIDO-EDV.LAN:1534
ESTABLISHED
TCP mido-pdc-01:1774 mido-pdc-01.MIDO-EDV.LAN:51233
LISTENING
TCP mido-pdc-01:1774 mido-pdc-01.MIDO-EDV.LAN:1775
ESTABLISHED
TCP mido-pdc-01:1775 mido-pdc-01.MIDO-EDV.LAN:1774
ESTABLISHED
TCP mido-pdc-01:1776 mido-pdc-01.MIDO-EDV.LAN:18574
LISTENING
TCP mido-pdc-01:1776 mido-pdc-01.MIDO-EDV.LAN:1777
ESTABLISHED
TCP mido-pdc-01:1777 mido-pdc-01.MIDO-EDV.LAN:1776
ESTABLISHED
TCP mido-pdc-01:1778 mido-pdc-01.MIDO-EDV.LAN:51389
LISTENING
TCP mido-pdc-01:1778 mido-pdc-01.MIDO-EDV.LAN:1779
ESTABLISHED
TCP mido-pdc-01:1779 mido-pdc-01.MIDO-EDV.LAN:1778
ESTABLISHED
TCP mido-pdc-01:1885 mido-pdc-01.MIDO-EDV.LAN:ldap
ESTABLISHED
TCP mido-pdc-01:6880 mido-pdc-01.MIDO-EDV.LAN:2112
LISTENING
TCP mido-pdc-01:netbios-ssn mido-pdc-01.MIDO-EDV.LAN:10379
LISTENING
TCP mido-pdc-01:ldap mido-pdc-01.MIDO-EDV.LAN:1084
ESTABLISHED
TCP mido-pdc-01:ldap mido-pdc-01.MIDO-EDV.LAN:1929
TIME_WAIT
TCP mido-pdc-01:ldap mido-pdc-01.MIDO-EDV.LAN:1933
TIME_WAIT
TCP mido-pdc-01:ldap mido-pdc-01.MIDO-EDV.LAN:1983
TIME_WAIT
TCP mido-pdc-01:ldap mido-pdc-01.MIDO-EDV.LAN:2023
TIME_WAIT
TCP mido-pdc-01:ldap mido-pdc-01.MIDO-EDV.LAN:2024
ESTABLISHED
TCP mido-pdc-01:ldap mido-pdc-01.MIDO-EDV.LAN:2025
TIME_WAIT
TCP mido-pdc-01:microsoft-ds mido-pdc-01.MIDO-EDV.LAN:1980
ESTABLISHED
TCP mido-pdc-01:microsoft-ds MIDO-LAP-01:1145
ESTABLISHED
TCP mido-pdc-01:1026 mido-pdc-01.MIDO-EDV.LAN:1086
ESTABLISHED
TCP mido-pdc-01:1026 mido-pdc-01.MIDO-EDV.LAN:1184
ESTABLISHED
TCP mido-pdc-01:1084 mido-pdc-01.MIDO-EDV.LAN:ldap
ESTABLISHED
TCP mido-pdc-01:1086 mido-pdc-01.MIDO-EDV.LAN:1026
ESTABLISHED
TCP mido-pdc-01:1164 mido-pdc-01.MIDO-EDV.LAN:ldap
CLOSE_WAIT
TCP mido-pdc-01:1184 mido-pdc-01.MIDO-EDV.LAN:1026
ESTABLISHED
TCP mido-pdc-01:1470 mido-pdc-01.MIDO-EDV.LAN:ldap
CLOSE_WAIT
TCP mido-pdc-01:1494 MIDO-LAP-01:1088
ESTABLISHED
TCP mido-pdc-01:1521 mido-pdc-01.MIDO-EDV.LAN:2074
LISTENING
TCP mido-pdc-01:1526 mido-pdc-01.MIDO-EDV.LAN:51318
LISTENING
TCP mido-pdc-01:1786 12-217-31-140.client.mchsi.com:6881
ESTABLISHED
TCP mido-pdc-01:1788
adsl-69-210-196-76.dsl.milwwi.ameritech.net:6864 ESTABLISHED
TCP mido-pdc-01:1798 218.111.202.173:6882
ESTABLISHED
TCP mido-pdc-01:1799 dsl-80-46-189-197.access.uk.tiscali.com:6884
ESTABLISHED
TCP mido-pdc-01:1800 AC88AED8.ipt.aol.com:6879
ESTABLISHED
TCP mido-pdc-01:1801 c-24-1-200-144.client.com:6881
ESTABLISHED
TCP mido-pdc-01:1802 pcp02169475pcs.maysld01.nj.comcast.net:43153
ESTABLISHED
TCP mido-pdc-01:1803 ppp190-117.lns1.bne1.internode.on.net:49157
ESTABLISHED
TCP mido-pdc-01:1809 sorbpunk.plus.com:49155
ESTABLISHED
TCP mido-pdc-01:1818 d235-215-149.home1.cgocable.net:47626
ESTABLISHED
TCP mido-pdc-01:1819 220-245-96-234.tpgi.com.au:6881
ESTABLISHED
TCP mido-pdc-01:1820 c-24-15-166-199.client.com:12372
ESTABLISHED
TCP mido-pdc-01:1822
modemcable104.108-201-24.mc.videotron.ca:6881 ESTABLISHED
TCP mido-pdc-01:1829 CPE00e018351453-CM0f205995:36865
ESTABLISHED
TCP mido-pdc-01:1833 12-220-81-171.client.insightBB.com:40265
ESTABLISHED
TCP mido-pdc-01:1838 dsl-217-155-39-162.zen.co.uk:6821
ESTABLISHED
TCP mido-pdc-01:1840 cm224.sigma231.maxonline.com.sg:50124
ESTABLISHED
TCP mido-pdc-01:1841 user-0ccsj79.cable.mindspring.com:47015
ESTABLISHED
TCP mido-pdc-01:1843 AC80E80B.ipt.aol.com:6909
ESTABLISHED
TCP mido-pdc-01:1846 69-166-226-85.anhmca.adelphia.net:49152
ESTABLISHED
TCP mido-pdc-01:1848 209.161.230.7:6881
ESTABLISHED
TCP mido-pdc-01:1852
80-192-177-66.cable.ubr03.blac.blueyonder.co.uk:6881 ESTABLISHED
TCP mido-pdc-01:1853
adsl-068-209-158-191.sip.shv.bellsouth.net:10000 ESTABLISHED
TCP mido-pdc-01:1857 port-212-202-77-89.dynamic.qsc.de:30709
ESTABLISHED
TCP mido-pdc-01:1861 12-222-55-151.client.insightBB.com:6881
ESTABLISHED
TCP mido-pdc-01:1889 mido-pdc-01.MIDO-EDV.LAN:epmap
TIME_WAIT
TCP mido-pdc-01:1890 mido-pdc-01.MIDO-EDV.LAN:1111
TIME_WAIT
TCP mido-pdc-01:1924 mido-pdc-01.MIDO-EDV.LAN:epmap
TIME_WAIT
TCP mido-pdc-01:1925 mido-pdc-01.MIDO-EDV.LAN:1026
TIME_WAIT
TCP mido-pdc-01:1926 MIDO-LAP-01:netbios-ssn
TIME_WAIT
TCP mido-pdc-01:1928 mido-pdc-01.MIDO-EDV.LAN:ldap
TIME_WAIT
TCP mido-pdc-01:1934 mido-pdc-01.MIDO-EDV.LAN:epmap
TIME_WAIT
TCP mido-pdc-01:1935 mido-pdc-01.MIDO-EDV.LAN:1026
TIME_WAIT
TCP mido-pdc-01:1980 mido-pdc-01.MIDO-EDV.LAN:microsoft-ds
ESTABLISHED
TCP mido-pdc-01:2018 mido-pdc-01.MIDO-EDV.LAN:epmap
TIME_WAIT
TCP mido-pdc-01:2019 mido-pdc-01.MIDO-EDV.LAN:1026
TIME_WAIT
TCP mido-pdc-01:2020 mido-pdc-01.MIDO-EDV.LAN:51304
LISTENING
TCP mido-pdc-01:2020 MIDO-LAP-01:netbios-ssn
ESTABLISHED
TCP mido-pdc-01:2022 mido-pdc-01.MIDO-EDV.LAN:ldap
TIME_WAIT
TCP mido-pdc-01:2024 mido-pdc-01.MIDO-EDV.LAN:ldap
ESTABLISHED
TCP mido-pdc-01:2026 mido-pdc-01.MIDO-EDV.LAN:epmap
TIME_WAIT
TCP mido-pdc-01:2027 mido-pdc-01.MIDO-EDV.LAN:1026
TIME_WAIT
TCP mido-pdc-01:6881 c-24-11-226-114.client.com:3316
ESTABLISHED
TCP mido-pdc-01:6881 24-54-248-35.lmdaca.adelphia.net:1941
ESTABLISHED
TCP mido-pdc-01:6881 user-24-214-124-90.knology.net:33085
ESTABLISHED
TCP mido-pdc-01:6881 ip68-5-92-168.oc.oc.cox.net:60937
ESTABLISHED
TCP mido-pdc-01:6881 S0106000c6eac9a27.cg.shawcable.net:38743
ESTABLISHED
TCP mido-pdc-01:6881 ip68-224-254-206.lv.lv.cox.net:3507
ESTABLISHED
TCP mido-pdc-01:6881 S01060080c821589b.ss.shawcable.net:3870
ESTABLISHED
TCP mido-pdc-01:6881 cs70112104-77.austin.rr.com:1513
ESTABLISHED
TCP mido-pdc-01:6881 39-182.lctv-ubr2-blk1.cablelynx.com:63293
ESTABLISHED
UDP mido-pdc-01:echo *:*
UDP mido-pdc-01:discard *:*
UDP mido-pdc-01:daytime *:*
UDP mido-pdc-01:qotd *:*
UDP mido-pdc-01:chargen *:*
UDP mido-pdc-01:nameserver *:*
UDP mido-pdc-01:bootpc *:*
UDP mido-pdc-01:epmap *:*
UDP mido-pdc-01:microsoft-ds *:*
UDP mido-pdc-01:1028 *:*
UDP mido-pdc-01:1048 *:*
UDP mido-pdc-01:1053 *:*
UDP mido-pdc-01:1063 *:*
UDP mido-pdc-01:1066 *:*
UDP mido-pdc-01:1069 *:*
UDP mido-pdc-01:1076 *:*
UDP mido-pdc-01:1082 *:*
UDP mido-pdc-01:1083 *:*
UDP mido-pdc-01:1088 *:*
UDP mido-pdc-01:1110 *:*
UDP mido-pdc-01:1114 *:*
UDP mido-pdc-01:1121 *:*
UDP mido-pdc-01:1125 *:*
UDP mido-pdc-01:1140 *:*
UDP mido-pdc-01:1163 *:*
UDP mido-pdc-01:1505 *:*
UDP mido-pdc-01:1509 *:*
UDP mido-pdc-01:1604 *:*
UDP mido-pdc-01:1645 *:*
UDP mido-pdc-01:1646 *:*
UDP mido-pdc-01:l2tp *:*
UDP mido-pdc-01:radius *:*
UDP mido-pdc-01:radacct *:*
UDP mido-pdc-01:1883 *:*
UDP mido-pdc-01:1884 *:*
UDP mido-pdc-01:2021 *:*
UDP mido-pdc-01:3000 *:*
UDP mido-pdc-01:3456 *:*
UDP mido-pdc-01:domain *:*
UDP mido-pdc-01:1141 *:*
UDP mido-pdc-01:1142 *:*
UDP mido-pdc-01:1882 *:*
UDP mido-pdc-01:domain *:*
UDP mido-pdc-01:bootps *:*
UDP mido-pdc-01:bootpc *:*
UDP mido-pdc-01:kerberos *:*
UDP mido-pdc-01:ntp *:*
UDP mido-pdc-01:netbios-ns *:*
UDP mido-pdc-01:netbios-dgm *:*
UDP mido-pdc-01:389 *:*
UDP mido-pdc-01:kpasswd *:*
UDP mido-pdc-01:isakmp *:*
UDP mido-pdc-01:2535 *:*


IP Statistics

Packets Received = 128.151
Received Header Errors = 0
Received Address Errors = 5
Datagrams Forwarded = 0
Unknown Protocols Received = 0
Received Packets Discarded = 0
Received Packets Delivered = 128.139
Output Requests = 120.709
Routing Discards = 0
Discarded Output Packets = 0
Output Packet No Route = 0
Reassembly Required = 24
Reassembly Successful = 12
Reassembly Failures = 0
Datagrams successfully fragmented = 0
Datagrams failing fragmentation = 0
Fragments Created = 0
Forwarding = 1
Default TTL = 128
Reassembly timeout = 60


TCP Statistics

Active Opens = 678
Passive Opens = 290
Failed Connection Attempts = 46
Reset Connections = 41
Current Connections = 67
Received Segments = 124.909
Segment Sent = 117.295
Segment Retransmitted = 220
Retransmission Timeout Algorithm = vanj
Minimum Retransmission Timeout = 300
Maximum Retransmission Timeout = 240.000
Maximum Number of Connections = -1


UDP Statistics

Datagrams Received = 1.329
No Ports = 1.490
Receive Errors = 1
Datagrams Sent = 1.368


ICMP Statistics

Received Sent
Messages 908 908
Errors 0 0
Destination Unreachable 61 61
Time Exceeded 0 0
Parameter Problems 0 0
Source Quenchs 0 0
Redirects 0 0
Echos 418 418
Echo Replies 429 429
Timestamps 0 0
Timestamp Replies 0 0
Address Masks 0 0
Address Mask Replies 0 0


Bindings test. . . . . . . . . . . : Passed
Component Name : NDIS-Benutzermodus-E/A-Protokoll
Bind Name: Ndisuio
Binding Paths:
Owner of the binding path : NDIS-Benutzermodus-E/A-Protokoll
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: NDIS-Benutzermodus-E/A-Protokoll
Lower Component: Intel(R) PRO/100 VE Network Connection

Owner of the binding path : NDIS-Benutzermodus-E/A-Protokoll
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: NDIS-Benutzermodus-E/A-Protokoll
Lower Component: 3Com EtherLink XL 10/100-PCI-NIC (3C905-TX) #2


Component Name : Point to Point Tunneling-Protokoll (PPTP)
Bind Name: mspptp
Binding Paths:

Component Name : Layer 2-Tunnelingprotokoll
Bind Name: msl2tp
Binding Paths:

Component Name : RAS-NDIS-WAN-Treiber
Bind Name: NdisWan
Binding Paths:
Owner of the binding path : RAS-NDIS-WAN-Treiber
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswan
Upper Component: RAS-NDIS-WAN-Treiber
Lower Component: AVM ISDN-Controller FRITZ!Card-PCI #4

Owner of the binding path : RAS-NDIS-WAN-Treiber
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswan
Upper Component: RAS-NDIS-WAN-Treiber
Lower Component: AVM NDIS WAN CAPI-Treiber

Owner of the binding path : RAS-NDIS-WAN-Treiber
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiscowan
Upper Component: RAS-NDIS-WAN-Treiber
Lower Component: Parallelanschluss (direkt)

Owner of the binding path : RAS-NDIS-WAN-Treiber
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswan
Upper Component: RAS-NDIS-WAN-Treiber
Lower Component: WAN-Miniport (PPTP)

Owner of the binding path : RAS-NDIS-WAN-Treiber
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiscowan
Upper Component: RAS-NDIS-WAN-Treiber
Lower Component: WAN-Miniport (L2TP)

Owner of the binding path : RAS-NDIS-WAN-Treiber
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanasync
Upper Component: RAS-NDIS-WAN-Treiber
Lower Component: Asynchroner RAS-Adapter


Component Name : Nachrichtorientiertes TCP/IP-Protokoll (SMB-Sitzung)
Bind Name: NetbiosSmb
Binding Paths:

Component Name : Protokoll für WINS-Client (TCP/IP)
Bind Name: NetBT
Binding Paths:
Owner of the binding path : Protokoll für WINS-Client (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Protokoll für WINS-Client (TCP/IP)
Lower Component: Internetprotokoll (TCP/IP)
-Interface Name: ndis5
Upper Component: Internetprotokoll (TCP/IP)
Lower Component: Intel(R) PRO/100 VE Network Connection

Owner of the binding path : Protokoll für WINS-Client (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Protokoll für WINS-Client (TCP/IP)
Lower Component: Internetprotokoll (TCP/IP)
-Interface Name: ndis5
Upper Component: Internetprotokoll (TCP/IP)
Lower Component: 3Com EtherLink XL 10/100-PCI-NIC (3C905-TX) #2

Owner of the binding path : Protokoll für WINS-Client (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Protokoll für WINS-Client (TCP/IP)
Lower Component: Internetprotokoll (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internetprotokoll (TCP/IP)
Lower Component: WAN-Miniport (IP)


Component Name : Internetprotokoll (TCP/IP)
Bind Name: Tcpip
Binding Paths:
Owner of the binding path : Internetprotokoll (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Internetprotokoll (TCP/IP)
Lower Component: Intel(R) PRO/100 VE Network Connection

Owner of the binding path : Internetprotokoll (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Internetprotokoll (TCP/IP)
Lower Component: 3Com EtherLink XL 10/100-PCI-NIC (3C905-TX) #2

Owner of the binding path : Internetprotokoll (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanip
Upper Component: Internetprotokoll (TCP/IP)
Lower Component: WAN-Miniport (IP)


Component Name : Client für Microsoft-Netzwerke
Bind Name: LanmanWorkstation
Binding Paths:
Owner of the binding path : Client für Microsoft-Netzwerke
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Client für Microsoft-Netzwerke
Lower Component: Nachrichtorientiertes TCP/IP-Protokoll
(SMB-Sitzung)

Owner of the binding path : Client für Microsoft-Netzwerke
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client für Microsoft-Netzwerke
Lower Component: Protokoll für WINS-Client (TCP/IP)
-Interface Name: tdi
Upper Component: Protokoll für WINS-Client (TCP/IP)
Lower Component: Internetprotokoll (TCP/IP)
-Interface Name: ndis5
Upper Component: Internetprotokoll (TCP/IP)
Lower Component: Intel(R) PRO/100 VE Network Connection

Owner of the binding path : Client für Microsoft-Netzwerke
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client für Microsoft-Netzwerke
Lower Component: Protokoll für WINS-Client (TCP/IP)
-Interface Name: tdi
Upper Component: Protokoll für WINS-Client (TCP/IP)
Lower Component: Internetprotokoll (TCP/IP)
-Interface Name: ndis5
Upper Component: Internetprotokoll (TCP/IP)
Lower Component: 3Com EtherLink XL 10/100-PCI-NIC (3C905-TX) #2

Owner of the binding path : Client für Microsoft-Netzwerke
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client für Microsoft-Netzwerke
Lower Component: Protokoll für WINS-Client (TCP/IP)
-Interface Name: tdi
Upper Component: Protokoll für WINS-Client (TCP/IP)
Lower Component: Internetprotokoll (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internetprotokoll (TCP/IP)
Lower Component: WAN-Miniport (IP)


Component Name : Drahtloskonfiguration
Bind Name: wzcsvc
Binding Paths:

Component Name : QoS-Paketplaner
Bind Name: PSched
Binding Paths:
Owner of the binding path : QoS-Paketplaner
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: QoS-Paketplaner
Lower Component: Intel(R) PRO/100 VE Network Connection

Owner of the binding path : QoS-Paketplaner
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: QoS-Paketplaner
Lower Component: 3Com EtherLink XL 10/100-PCI-NIC (3C905-TX) #2

Owner of the binding path : QoS-Paketplaner
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanip
Upper Component: QoS-Paketplaner
Lower Component: WAN-Miniport (IP)


Component Name : DHCP-Server
Bind Name: DHCPServer
Binding Paths:

Component Name : Steelhead
Bind Name: RemoteAccess
Binding Paths:

Component Name : DFÜ-Server
Bind Name: msrassrv
Binding Paths:

Component Name : RAS-Verbindungsverwaltung
Bind Name: RasMan
Binding Paths:

Component Name : DFÜ-Client
Bind Name: msrascli
Binding Paths:

Component Name : Datei- und Druckerfreigabe für Microsoft-Netzwerke
Bind Name: LanmanServer
Binding Paths:
Owner of the binding path : Datei- und Druckerfreigabe für
Microsoft-Netzwerke
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Datei- und Druckerfreigabe für
Microsoft-Netzwerke
Lower Component: Nachrichtorientiertes TCP/IP-Protokoll
(SMB-Sitzung)

Owner of the binding path : Datei- und Druckerfreigabe für
Microsoft-Netzwerke
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Datei- und Druckerfreigabe für
Microsoft-Netzwerke
Lower Component: Protokoll für WINS-Client (TCP/IP)
-Interface Name: tdi
Upper Component: Protokoll für WINS-Client (TCP/IP)
Lower Component: Internetprotokoll (TCP/IP)
-Interface Name: ndis5
Upper Component: Internetprotokoll (TCP/IP)
Lower Component: Intel(R) PRO/100 VE Network Connection

Owner of the binding path : Datei- und Druckerfreigabe für
Microsoft-Netzwerke
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Datei- und Druckerfreigabe für
Microsoft-Netzwerke
Lower Component: Protokoll für WINS-Client (TCP/IP)
-Interface Name: tdi
Upper Component: Protokoll für WINS-Client (TCP/IP)
Lower Component: Internetprotokoll (TCP/IP)
-Interface Name: ndis5
Upper Component: Internetprotokoll (TCP/IP)
Lower Component: 3Com EtherLink XL 10/100-PCI-NIC (3C905-TX) #2

Owner of the binding path : Datei- und Druckerfreigabe für
Microsoft-Netzwerke
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Datei- und Druckerfreigabe für
Microsoft-Netzwerke
Lower Component: Protokoll für WINS-Client (TCP/IP)
-Interface Name: tdi
Upper Component: Protokoll für WINS-Client (TCP/IP)
Lower Component: Internetprotokoll (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internetprotokoll (TCP/IP)
Lower Component: WAN-Miniport (IP)


Component Name : NetBIOS-Schnittstelle
Bind Name: NetBIOS
Binding Paths:
Owner of the binding path : NetBIOS-Schnittstelle
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS-Schnittstelle
Lower Component: Protokoll für WINS-Client (TCP/IP)
-Interface Name: tdi
Upper Component: Protokoll für WINS-Client (TCP/IP)
Lower Component: Internetprotokoll (TCP/IP)
-Interface Name: ndis5
Upper Component: Internetprotokoll (TCP/IP)
Lower Component: Intel(R) PRO/100 VE Network Connection

Owner of the binding path : NetBIOS-Schnittstelle
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS-Schnittstelle
Lower Component: Protokoll für WINS-Client (TCP/IP)
-Interface Name: tdi
Upper Component: Protokoll für WINS-Client (TCP/IP)
Lower Component: Internetprotokoll (TCP/IP)
-Interface Name: ndis5
Upper Component: Internetprotokoll (TCP/IP)
Lower Component: 3Com EtherLink XL 10/100-PCI-NIC (3C905-TX) #2

Owner of the binding path : NetBIOS-Schnittstelle
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS-Schnittstelle
Lower Component: Protokoll für WINS-Client (TCP/IP)
-Interface Name: tdi
Upper Component: Protokoll für WINS-Client (TCP/IP)
Lower Component: Internetprotokoll (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internetprotokoll (TCP/IP)
Lower Component: WAN-Miniport (IP)


Component Name : QoS RSVP
Bind Name: RSVP
Binding Paths:

Component Name : Standardpaketklassifizierung
Bind Name: Gpc
Binding Paths:

Component Name : AVM ISDN-Controller FRITZ!Card-PCI #4
Bind Name: {18450590-23F7-4659-A820-05D3698A873B}
Binding Paths:

Component Name : AVM NDIS WAN CAPI-Treiber
Bind Name: {9AA6EE09-2311-4214-A191-E4CC71F5650C}
Binding Paths:

Component Name : Intel(R) PRO/100 VE Network Connection
Bind Name: {624E378E-5224-4119-B297-890DE704251D}
Binding Paths:

Component Name : 3Com EtherLink XL 10/100-PCI-NIC (3C905-TX) #2
Bind Name: {0B7AE966-AD6C-435A-874C-7DB3383728AB}
Binding Paths:

Component Name : WAN-Miniport (IP)
Bind Name: NdisWanIp
Binding Paths:

Component Name : Parallelanschluss (direkt)
Bind Name: {DD66C6F1-7AA0-4E52-945B-B73051EDB428}
Binding Paths:

Component Name : WAN-Miniport (PPTP)
Bind Name: {B0713803-B84B-4CA5-A369-2445865E9FC1}
Binding Paths:

Component Name : WAN-Miniport (L2TP)
Bind Name: {2D334E02-125A-4BAD-A318-68BB7EC98F24}
Binding Paths:

Component Name : Asynchroner RAS-Adapter
Bind Name: {47D94540-6CB2-4A34-9F4C-7BF6A6DC079C}
Binding Paths:



WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Passed
IPSec policy service is active, but no policy is assigned.

IPSec Statistics

Oakley Main Modes : 0
Oakley Quick Modes : 0
Active Associations : 0
Soft Associations : 0
Authenticated Bytes Sent : 0
Authenticated Bytes Received : 0
Confidential Bytes Sent : 0
Confidential Bytes Received : 0
Offloaded Bytes Sent : 0
Offloaded Bytes Received : 0
ReKeys : 0

Authentication Failures : 0
Negotiation Failures : 0
Packets not decrypted : 0
Packets not authenticated : 0
Invalid Cookies Rcvd : 0
Acquire fail : 0
Receive fail : 0
Send fail : 0
GetSpiFail : 0
KeyAddFail : 0
KeyUpdateFail : 0

Active Acquire : 1
Active Rcv : 0
Active Send : 0
Total Acquire : 0
TotalGetSpi : 0
TotalKeyAdd : 0
TotalKeyUpdate : 0
Inactive Associations : 0
Dead Associations : 0
Pending Keys : 0
Key Flushes : 0
Key Additions : 0
Key Deletes : 0

Phase 1 offers count is 4
OFFER #1:
PFS : No, Encryption : 3DES, Hash : SHA1, Group : Medium (2)
Quickmodes per MainMode : 0, Lifetime Seconds : 28800
OFFER #2:
PFS : No, Encryption : 3DES, Hash : MD5, Group : Medium (2)
Quickmodes per MainMode : 0, Lifetime Seconds : 28800
OFFER #3:
PFS : No, Encryption : DES, Hash : SHA1, Group : Low (1)
Quickmodes per MainMode : 0, Lifetime Seconds : 28800
OFFER #4:
PFS : No, Encryption : DES, Hash : MD5, Group : Low (1)
Quickmodes per MainMode : 0, Lifetime Seconds : 28800

Current Phase 1 SAs:
No SAs.


Current Phase 2 SAs:
No SAs.




The command completed successfully
 
C

Count Blackula

I somehow cant run dcdiag. Trying to do so results in error "procedureentry
"dsismangledDnW" not found in dll ntdsapi.dll". Tried to reinstall Sp4 and
dcdiag but no success..
 
K

Kevin D. Goodknecht Sr. [MVP]

Is the DHCP Client service running?
The DHCP client service is a required service whether the machine is a DHCP
client or not.
 
K

Kevin D. Goodknecht Sr. [MVP]

In Count Blackula <[email protected]> commented
Then Kevin replied below:
Hello Count,
You have verified that "Allow dynamic updates" is set to "Yes"?
The ipconfig registration is in the zone, it is all the Netlogon
registrations that are missing. It is reported that in some cases you can
add this registry entry to fix this.
Key: HKLM\Systems\CurrentControlSet\Services\Netlogon\Parameters
Value: DnsUpdateOnAllAdapters (DWORD)
to 1.

Give that a try, if it doesn't work you'll have to call MSPSS or I can
remote in to see what I can find.

DNS test . . . . . . . . . . . . . : Failed
Interface {0B7AE966-AD6C-435A-874C-7DB3383728AB}
DNS Domain:
DNS Servers: 192.168.150.21
IP Address: 192.168.150.21
Expected registration with PDN (primary DNS
domain name): Hostname:
mido-pdc-01.MIDO-EDV.LAN. Authoritative zone:
MIDO-EDV.LAN. Primary DNS server:
mido-pdc-01.MIDO-EDV.LAN 192.168.150.21
Authoritative NS:192.168.150.21 Verify DNS
registration: Name: mido-pdc-01.MIDO-EDV.LAN
Expected IP: 192.168.150.21
Server 192.168.150.21: NO_ERROR
The DNS registration for mido-pdc-01.MIDO-EDV.LAN is
correct on all DNS servers
Check the DNS registration for DCs entries on DNS server
'192.168.150.21' Query for DC DNS entry MIDO-EDV.LAN. on
DNS server 192.168.150.21 failed. DNS Error code:
0x0000251D
Query for DC DNS entry _ldap._tcp.MIDO-EDV.LAN. on DNS
server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry
_ldap._tcp.Standardname-des-ersten-Standorts._sites.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry
_ldap._tcp.pdc._msdcs.MIDO-EDV.LAN. on DNS server
192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry _ldap._tcp.gc._msdcs.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry
_ldap._tcp.Standardname-des-ersten-Standorts._sites.gc._msdcs.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry
_ldap._tcp.9d5f4c63-b31c-4866-a90e-e9b8cdc9ef95.domains._msdcs.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry gc._msdcs.MIDO-EDV.LAN. on DNS
server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry
29d41657-b087-46c7-87c4-2c1bd658c063._msdcs.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry
_kerberos._tcp.dc._msdcs.MIDO-EDV.LAN. on DNS server
192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry
_kerberos._tcp.Standardname-des-ersten-Standorts._sites.dc._msdcs.MIDO-EDV.L
AN. on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry _ldap._tcp.dc._msdcs.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry
_ldap._tcp.Standardname-des-ersten-Standorts._sites.dc._msdcs.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry _kerberos._tcp.MIDO-EDV.LAN. on
DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry
_kerberos._tcp.Standardname-des-ersten-Standorts._sites.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry _gc._tcp.MIDO-EDV.LAN. on DNS
server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry
_gc._tcp.Standardname-des-ersten-Standorts._sites.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry _kerberos._udp.MIDO-EDV.LAN. on
DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry _kpasswd._tcp.MIDO-EDV.LAN. on DNS
server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry _kpasswd._udp.MIDO-EDV.LAN. on DNS
server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
[WARNING] The DNS entries for this DC are not
registered correctly on DNS server '192.168.150.21'.
Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this
DC registered.
Click to expand...
 
C

Count Blackula

Tataaa! Problem solved! I just added the key and restarted netlogon and
voila. Strange thing is, there is a entry "update" with value 0 in the key.
I now have to see if this solves my primary problem, adding a BDC but ill
keep you informed.
I really appreciate your efforts. Thank you very much.

Greetings,

Milenko


Kevin D. Goodknecht Sr. said:
In Count Blackula <[email protected]> commented
Then Kevin replied below:
Hello Count,
You have verified that "Allow dynamic updates" is set to "Yes"?
The ipconfig registration is in the zone, it is all the Netlogon
registrations that are missing. It is reported that in some cases you can
add this registry entry to fix this.
Key: HKLM\Systems\CurrentControlSet\Services\Netlogon\Parameters
Value: DnsUpdateOnAllAdapters (DWORD)
to 1.

Give that a try, if it doesn't work you'll have to call MSPSS or I can
remote in to see what I can find.

DNS test . . . . . . . . . . . . . : Failed
Interface {0B7AE966-AD6C-435A-874C-7DB3383728AB}
DNS Domain:
DNS Servers: 192.168.150.21
IP Address: 192.168.150.21
Expected registration with PDN (primary DNS
domain name): Hostname:
mido-pdc-01.MIDO-EDV.LAN. Authoritative zone:
MIDO-EDV.LAN. Primary DNS server:
mido-pdc-01.MIDO-EDV.LAN 192.168.150.21
Authoritative NS:192.168.150.21 Verify DNS
registration: Name: mido-pdc-01.MIDO-EDV.LAN
Expected IP: 192.168.150.21
Server 192.168.150.21: NO_ERROR
The DNS registration for mido-pdc-01.MIDO-EDV.LAN is
correct on all DNS servers
Check the DNS registration for DCs entries on DNS server
'192.168.150.21' Query for DC DNS entry MIDO-EDV.LAN. on
DNS server 192.168.150.21 failed. DNS Error code:
0x0000251D
Query for DC DNS entry _ldap._tcp.MIDO-EDV.LAN. on DNS
server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry
_ldap._tcp.Standardname-des-ersten-Standorts._sites.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry
_ldap._tcp.pdc._msdcs.MIDO-EDV.LAN. on DNS server
192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry _ldap._tcp.gc._msdcs.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry
Click to expand...
_ldap._tcp.Standardname-des-ersten-Standorts._sites.gc._msdcs.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry
Click to expand...
_ldap._tcp.9d5f4c63-b31c-4866-a90e-e9b8cdc9ef95.domains._msdcs.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry gc._msdcs.MIDO-EDV.LAN. on DNS
server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry
29d41657-b087-46c7-87c4-2c1bd658c063._msdcs.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry
_kerberos._tcp.dc._msdcs.MIDO-EDV.LAN. on DNS server
192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry
Click to expand...
_kerberos._tcp.Standardname-des-ersten-Standorts._sites.dc._msdcs.MIDO-EDV.L
AN. on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry _ldap._tcp.dc._msdcs.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry
Click to expand...
_ldap._tcp.Standardname-des-ersten-Standorts._sites.dc._msdcs.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry _kerberos._tcp.MIDO-EDV.LAN. on
DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry
_kerberos._tcp.Standardname-des-ersten-Standorts._sites.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry _gc._tcp.MIDO-EDV.LAN. on DNS
server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry
_gc._tcp.Standardname-des-ersten-Standorts._sites.MIDO-EDV.LAN.
on DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry _kerberos._udp.MIDO-EDV.LAN. on
DNS server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry _kpasswd._tcp.MIDO-EDV.LAN. on DNS
server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
Query for DC DNS entry _kpasswd._udp.MIDO-EDV.LAN. on DNS
server 192.168.150.21 failed.
DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not
exist on DNS server)
[WARNING] The DNS entries for this DC are not
registered correctly on DNS server '192.168.150.21'.
Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this
DC registered.
Click to expand...
Click to expand...
 
K

Kevin D. Goodknecht Sr. [MVP]

In
Count Blackula said:
Tataaa! Problem solved! I just added the key and
restarted netlogon and voila. Strange thing is, there is
a entry "update" with value 0 in the key.
Click to expand...

That splains it then, a value of 0 disables netlogon registrations.
Glad I was able to help.
 
C

Count Blackula

O.k BDC is working! But something interesting:

After i started netlogon again i received permanent netlogon-errors after a
while. But this time it was id 5775. It is in german and quite complex but
its roughly about not being able to unregister DNS entries because the host
was unknown or not responding. Researching this error id i found a article
in a german MSCE forum solving that problem and explaining the (possible)
cause that matches my situation. I must apologize for not mentioning, that i
recently dcpromo´d and promoted my server again as a pdc for a new domain
name ( domain.de --> domain.lan ) because my AD was corrupted. I think thats
what happened to me too:

Source NETLOGON
Type Error
Description Deregistration of the DNS record
'_ldap._tcp.gc._msdcs.ALTDOMAIN.net. 600 IN SRV 0 100 3268
kant.ALTDOMAIN.net.' failed with the following error: DNS bad key.

As per Microsoft: "In general, these error messages are logged because the
Netlogon service does not receive a "success" message from the DNS server
that owns the zones of the records that are being registered. ". See the
links below for more info.

Recently I saw this event during the process of which I removed an Active
Directory domain from a server and recreated a new Active Directory domain
on the same server. The DCPROMO and Active Directory setup wizards had no
problems but it appeared that the NETLOGON service was still referencing the
old domain name resource records for DNS.

I found that the NETLOGON service uses the following 2 files; NETLOGON.DNS &
NETLOGON.DNB. These files did in fact contain resource record information on
the previous domain name. Here''s a set of steps to take care of the
problem.
1. Stop the NETLOGON service.
2. Copy out NETLOGON.DNS and NETLOGON.DNB from %SystemRoot%\System32\Config
to a hold directory in case they might be needed.
3. Delete NETLOGON.DNS and NETLOGON.DNB from the %SytemRoot%\System32\Config
directory.
4. Restart the NETLOGON service. NETLOGON.DNS and NETLOGON.DNB will be
recreated on the fly with the current AD domain DNS information.

After deleting these 2 files, my event-logs are 90% blue and 10% yellow
again :) ( no no red color in sight ! ).

Sorry for withholding that information. But maybe this will help somebody
else after all.



Greetings from Germany,



Milenko
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

DNS domain subfolders 1
Missing "_msdcs,_site" subfolder 3
SRV RR records missing? 2
Active Direcroty Integration in DNS - Looses Forward Zone :-0 7
missing _msdcs, _sites, _tcp, _udp 8
DNS set up incorrectly 1
Proper DNS configuration help 12
All DNS domain subdirectories missing 1

Top