Can't join a domain

Discussion:

Can't join a domain

(too old to reply)

Kolchak

2007-07-18 12:18:01 UTC

Hi,

Been killing me all day, so begging for help :)

I have a machine I want to be a DC at a remote site, but DCPROMO is failing
with:

An Active Directory domain controller for the domain DOM could not be
contacted.

The domain name DOM might be a NetBIOS domain name. If this is the case,
verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the
following information can help you troubleshoot your DNS configuration.

DNS was successfully queried for the service location (SRV) resource record
used to locate a domain controller for domain DOM:

The query was for the SRV record for _ldap._tcp.dc._msdcs.DOM

The following domain controllers were identified by the query:

files1.DOM
files3.DOM

Common causes of this error include:

- Host (A) records that map the name of the domain controller to its IP
addresses are missing or contain incorrect addresses.

- Domain controllers registered in DNS are not connected to the network or
are not running.

This machine is using files1 and files3 as its DNS servers. Files1 and
files3 are both at HQ, I'm at the remote site. A VPN is setup and no ports

set q=srv
_ldap._tcp.dc._msdcs.DOM

Server: files3.DOM
Address: 10.1.1.3

_ldap._tcp.dc._msdcs.DOM SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = files3.DOM
_ldap._tcp.dc._msdcs.DOM SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = files1.DOM
files3.DOM internet address = 10.1.1.3
files1.DOM internet address = 10.1.1.1

So srv can be located. The same error happens when I try and add the machine
to the domain. Both existing DCs can be pinged, and an nmap of them both from
the remote site returns hundreds of open ports, with all the expected ones
marked opened. I am absolutely stumped - any ideas??? I've run DCDIAG on a
domain controller and everything is fine... please help :)

Cheers,
Karl

Paul Bergson [MVP-DS]

2007-07-18 12:52:51 UTC

Permalink

Are there any firewalls between the two boxes up and running? Forget about
doing a dcpromo until you figure out what why you can't join the domain.

Try running portqryui from the member server to the DC.
http://www.microsoft.com/downloads/details.aspx?familyid=8355e537-1ea6-4569-aabb-f248f4bd91d0&displaylang=en

Select the domains and trusts built in query
http://www.windowsecurity.com/articles/Mastering-PortQryexe-Part2.html
--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

Post by Kolchak
Hi,
Been killing me all day, so begging for help :)
I have a machine I want to be a DC at a remote site, but DCPROMO is failing
An Active Directory domain controller for the domain DOM could not be
contacted.
The domain name DOM might be a NetBIOS domain name. If this is the case,
verify that the domain name is properly registered with WINS.
If you are certain that the name is not a NetBIOS domain name, then the
following information can help you troubleshoot your DNS configuration.
DNS was successfully queried for the service location (SRV) resource record
The query was for the SRV record for _ldap._tcp.dc._msdcs.DOM
files1.DOM
files3.DOM
- Host (A) records that map the name of the domain controller to its IP
addresses are missing or contain incorrect addresses.
- Domain controllers registered in DNS are not connected to the network or
are not running.
This machine is using files1 and files3 as its DNS servers. Files1 and
files3 are both at HQ, I'm at the remote site. A VPN is setup and no ports

set q=srv
_ldap._tcp.dc._msdcs.DOM

Server: files3.DOM
Address: 10.1.1.3
priority = 0
weight = 100
port = 389
svr hostname = files3.DOM
priority = 0
weight = 100
port = 389
svr hostname = files1.DOM
files3.DOM internet address = 10.1.1.3
files1.DOM internet address = 10.1.1.1
So srv can be located. The same error happens when I try and add the machine
to the domain. Both existing DCs can be pinged, and an nmap of them both from
the remote site returns hundreds of open ports, with all the expected ones
marked opened. I am absolutely stumped - any ideas??? I've run DCDIAG on a
domain controller and everything is fine... please help :)
Cheers,
Karl

Kolchak

2007-07-19 00:36:01 UTC

Permalink

Hi Paul,

Many thanks for the tool, never heard of it but works a treat. Below is the
output, but (from what I believe) everything seems OK except for this bit:

Starting portqry.exe -n files3 -e 42 -p TCP ...

Querying target system called:

files3

Attempting to resolve name to IP address...

Name resolved to 10.1.1.3

querying...

TCP port 42 (nameserver service): NOT LISTENING
portqry.exe -n files3 -e 42 -p TCP exits with return code 0x00000001.

Name server on TCP port 42??? Never heard of it. DNS = 53. Any ideas? Many
thanks for all your help...

Here is the complete output...

=============================================

Starting portqry.exe -n files3 -e 135 -p TCP ...

Querying target system called:

files3

Attempting to resolve name to IP address...

Name resolved to 10.1.1.3

querying...

TCP port 135 (epmap service): LISTENING

Using ephemeral source port
Querying Endpoint Mapper Database...
Server's response:

UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncalrpc:[dhcpcsvc]

UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
ncalrpc:[W32TIME_ALT]

UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
ncacn_np:\\\\FILES3[\\PIPE\\W32TIME_ALT]

UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
ncacn_np:\\\\FILES3[\\pipe\\tapsrv]

UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
ncalrpc:[tapsrvlpc]

UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
ncalrpc:[unimdmsvc]

UUID: 50abc2a4-574d-40b3-9d66-ee4fd5fba076
ncacn_ip_tcp:10.1.1.3[1357]

UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncalrpc:[OLEB46E256106A348C6972E19CEB86D]

UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncacn_ip_tcp:10.1.1.3[1090]

UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncalrpc:[DHCPSERVERLPC]

UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncalrpc:[OLEB46E256106A348C6972E19CEB86D]

UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncacn_ip_tcp:10.1.1.3[1090]

UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncalrpc:[DHCPSERVERLPC]

UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncalrpc:[OLE912A611DF0B64360AA38DBFEC079]

UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncacn_ip_tcp:10.1.1.3[1078]

UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncalrpc:[LRPC0000070c.00000001]

UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncalrpc:[OLE912A611DF0B64360AA38DBFEC079]

UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncacn_ip_tcp:10.1.1.3[1078]

UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncalrpc:[LRPC0000070c.00000001]

UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncalrpc:[OLE912A611DF0B64360AA38DBFEC079]

UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncacn_ip_tcp:10.1.1.3[1078]

UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncalrpc:[LRPC0000070c.00000001]

UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000004b4.00000001]

UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000004b4.00000001]

UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000004b4.00000001]

UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000004b4.00000001]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_np:\\\\FILES3[\\PIPE\\lsass]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[audit]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[securityevent]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[protected_storage]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_np:\\\\FILES3[\\PIPE\\protected_storage]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[dsrole]

UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_ip_tcp:10.1.1.3[1025]

UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_np:\\\\FILES3[\\PIPE\\lsass]

UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[audit]

UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[securityevent]

UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[protected_storage]

UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_np:\\\\FILES3[\\PIPE\\protected_storage]

UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[dsrole]

UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_ip_tcp:10.1.1.3[1025]

UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_np:\\\\FILES3[\\PIPE\\lsass]

UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[audit]

UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[securityevent]

UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[protected_storage]

UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_np:\\\\FILES3[\\PIPE\\protected_storage]

UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[dsrole]

UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_ip_tcp:10.1.1.3[1025]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_np:\\\\FILES3[\\PIPE\\lsass]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[audit]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[securityevent]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[protected_storage]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_np:\\\\FILES3[\\PIPE\\protected_storage]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[dsrole]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_ip_tcp:10.1.1.3[1025]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[NTDS_LPC]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_http:10.1.1.3[1027]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_np:\\\\FILES3[\\PIPE\\lsass]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[audit]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[securityevent]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[protected_storage]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_np:\\\\FILES3[\\PIPE\\protected_storage]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[dsrole]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_ip_tcp:10.1.1.3[1025]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[NTDS_LPC]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_http:10.1.1.3[1027]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_np:\\\\FILES3[\\PIPE\\lsass]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[audit]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[securityevent]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[protected_storage]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_np:\\\\FILES3[\\PIPE\\protected_storage]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[dsrole]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_ip_tcp:10.1.1.3[1025]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[NTDS_LPC]

UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_http:10.1.1.3[1027]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_np:\\\\FILES3[\\PIPE\\lsass]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[audit]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[securityevent]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[protected_storage]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_np:\\\\FILES3[\\PIPE\\protected_storage]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[dsrole]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_ip_tcp:10.1.1.3[1025]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[NTDS_LPC]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_http:10.1.1.3[1027]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_np:\\\\FILES3[\\PIPE\\lsass]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[audit]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[securityevent]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[protected_storage]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_np:\\\\FILES3[\\PIPE\\protected_storage]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[dsrole]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_ip_tcp:10.1.1.3[1025]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[NTDS_LPC]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_http:10.1.1.3[1027]

UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[OLECC4E9A8ACA114C36BF4EF4C2FDC0]

UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncalrpc:[wzcsvc]

UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncalrpc:[OLE6649563968BD42C8B8CC25172C71]

UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncacn_np:\\\\FILES3[\\PIPE\\atsvc]

UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncalrpc:[wzcsvc]

UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncalrpc:[OLE6649563968BD42C8B8CC25172C71]

UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncacn_np:\\\\FILES3[\\PIPE\\atsvc]

UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncalrpc:[wzcsvc]

UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncalrpc:[OLE6649563968BD42C8B8CC25172C71]

UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncacn_np:\\\\FILES3[\\PIPE\\atsvc]

UUID: 4da1c422-943d-11d1-acae-00c04fc2aa3f
ncacn_ip_tcp:10.1.1.3[3405]

Total endpoints found: 103

==== End of RPC Endpoint Mapper query response ====
portqry.exe -n files3 -e 135 -p TCP exits with return code 0x00000000.
=============================================

Starting portqry.exe -n files3 -e 389 -p BOTH ...

Querying target system called:

files3

Attempting to resolve name to IP address...

Name resolved to 10.1.1.3

querying...

TCP port 389 (ldap service): LISTENING

Using ephemeral source port
Sending LDAP query to TCP port 389...

LDAP query response:

currentdate: 07/19/2007 00:15:17 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=DOM
dsServiceName: CN=NTDS
Settings,CN=FILES3,CN=Servers,CN=DOM-Melbourne,CN=Sites,CN=Configuration,DC=DOM
namingContexts: DC=DOM
defaultNamingContext: DC=DOM
schemaNamingContext: CN=Schema,CN=Configuration,DC=DOM
configurationNamingContext: CN=Configuration,DC=DOM
rootDomainNamingContext: DC=DOM
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 8108582
supportedSASLMechanisms: GSSAPI
dnsHostName: files3.DOM
ldapServiceName: DOM:files3$@DOM
serverName:
CN=FILES3,CN=Servers,CN=DOM-Melbourne,CN=Sites,CN=Configuration,DC=DOM
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 2
forestFunctionality: 0
domainControllerFunctionality: 2

======== End of LDAP query response ========

UDP port 389 (unknown service): LISTENING or FILTERED

Using ephemeral source port
Sending LDAP query to UDP port 389...

LDAP query response:

currentdate: 07/19/2007 00:15:21 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=DOM
dsServiceName: CN=NTDS
Settings,CN=FILES3,CN=Servers,CN=DOM-Melbourne,CN=Sites,CN=Configuration,DC=DOM
namingContexts: DC=DOM
defaultNamingContext: DC=DOM
schemaNamingContext: CN=Schema,CN=Configuration,DC=DOM
configurationNamingContext: CN=Configuration,DC=DOM
rootDomainNamingContext: DC=DOM
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 8108582
supportedSASLMechanisms: GSSAPI
dnsHostName: files3.DOM
ldapServiceName: DOM:files3$@DOM
serverName:
CN=FILES3,CN=Servers,CN=DOM-Melbourne,CN=Sites,CN=Configuration,DC=DOM
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 2
forestFunctionality: 0
domainControllerFunctionality: 2

======== End of LDAP query response ========

UDP port 389 is LISTENING

portqry.exe -n files3 -e 389 -p BOTH exits with return code 0x00000000.
=============================================

Starting portqry.exe -n files3 -e 636 -p TCP ...

Querying target system called:

files3

Attempting to resolve name to IP address...

Name resolved to 10.1.1.3

querying...

TCP port 636 (ldaps service): LISTENING
portqry.exe -n files3 -e 636 -p TCP exits with return code 0x00000000.
=============================================

Starting portqry.exe -n files3 -e 3268 -p TCP ...

Querying target system called:

files3

Attempting to resolve name to IP address...

Name resolved to 10.1.1.3

querying...

TCP port 3268 (msft-gc service): LISTENING

Using ephemeral source port
Sending LDAP query to TCP port 3268...

LDAP query response:

currentdate: 07/19/2007 00:15:23 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=DOM
dsServiceName: CN=NTDS
Settings,CN=FILES3,CN=Servers,CN=DOM-Melbourne,CN=Sites,CN=Configuration,DC=DOM
namingContexts: DC=DOM
defaultNamingContext: DC=DOM
schemaNamingContext: CN=Schema,CN=Configuration,DC=DOM
configurationNamingContext: CN=Configuration,DC=DOM
rootDomainNamingContext: DC=DOM
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 8108582
supportedSASLMechanisms: GSSAPI
dnsHostName: files3.DOM
ldapServiceName: DOM:files3$@DOM
serverName:
CN=FILES3,CN=Servers,CN=DOM-Melbourne,CN=Sites,CN=Configuration,DC=DOM
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 2
forestFunctionality: 0
domainControllerFunctionality: 2

======== End of LDAP query response ========
portqry.exe -n files3 -e 3268 -p TCP exits with return code 0x00000000.
=============================================

Starting portqry.exe -n files3 -e 3269 -p TCP ...

Querying target system called:

files3

Attempting to resolve name to IP address...

Name resolved to 10.1.1.3

querying...

TCP port 3269 (msft-gc-ssl service): LISTENING
portqry.exe -n files3 -e 3269 -p TCP exits with return code 0x00000000.
=============================================

Starting portqry.exe -n files3 -e 53 -p BOTH ...

Querying target system called:

files3

Attempting to resolve name to IP address...

Name resolved to 10.1.1.3

querying...

TCP port 53 (domain service): LISTENING

UDP port 53 (domain service): LISTENING
portqry.exe -n files3 -e 53 -p BOTH exits with return code 0x00000000.
=============================================

Starting portqry.exe -n files3 -e 88 -p BOTH ...

Querying target system called:

files3

Attempting to resolve name to IP address...

Name resolved to 10.1.1.3

querying...

TCP port 88 (kerberos service): LISTENING

UDP port 88 (kerberos service): LISTENING or FILTERED
portqry.exe -n files3 -e 88 -p BOTH exits with return code 0x00000002.
=============================================

Starting portqry.exe -n files3 -e 445 -p TCP ...

Querying target system called:

files3

Attempting to resolve name to IP address...

Name resolved to 10.1.1.3

querying...

TCP port 445 (microsoft-ds service): LISTENING
portqry.exe -n files3 -e 445 -p TCP exits with return code 0x00000000.
=============================================

Starting portqry.exe -n files3 -e 137 -p UDP ...

Querying target system called:

files3

Attempting to resolve name to IP address...

Name resolved to 10.1.1.3

querying...

UDP port 137 (netbios-ns service): LISTENING or FILTERED

Using ephemeral source port
Attempting NETBIOS adapter status query to UDP port 137...

Server's response: MAC address 001485f46acc
UDP port: LISTENING
portqry.exe -n files3 -e 137 -p UDP exits with return code 0x00000000.
=============================================

Starting portqry.exe -n files3 -e 138 -p UDP ...

Querying target system called:

files3

Attempting to resolve name to IP address...

Name resolved to 10.1.1.3

querying...

UDP port 138 (netbios-dgm service): LISTENING or FILTERED
portqry.exe -n files3 -e 138 -p UDP exits with return code 0x00000002.
=============================================

Starting portqry.exe -n files3 -e 139 -p TCP ...

Querying target system called:

files3

Attempting to resolve name to IP address...

Name resolved to 10.1.1.3

querying...

TCP port 139 (netbios-ssn service): LISTENING
portqry.exe -n files3 -e 139 -p TCP exits with return code 0x00000000.
=============================================

Starting portqry.exe -n files3 -e 42 -p TCP ...

Querying target system called:

files3

Attempting to resolve name to IP address...

Name resolved to 10.1.1.3

querying...

TCP port 42 (nameserver service): NOT LISTENING
portqry.exe -n files3 -e 42 -p TCP exits with return code 0x00000001.

Post by Paul Bergson [MVP-DS]
Are there any firewalls between the two boxes up and running? Forget about
doing a dcpromo until you figure out what why you can't join the domain.
Try running portqryui from the member server to the DC.
http://www.microsoft.com/downloads/details.aspx?familyid=8355e537-1ea6-4569-aabb-f248f4bd91d0&displaylang=en
Select the domains and trusts built in query
http://www.windowsecurity.com/articles/Mastering-PortQryexe-Part2.html
--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

set q=srv
_ldap._tcp.dc._msdcs.DOM

Paul Bergson [MVP-DS]

2007-07-20 12:37:37 UTC

Permalink

Provide the following from the DC's, DNS server and the member server

Open up a command prompt and type in ipconfig /all
--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

Post by Kolchak
Hi Paul,
Many thanks for the tool, never heard of it but works a treat. Below is the
Starting portqry.exe -n files3 -e 42 -p TCP ...
files3
Attempting to resolve name to IP address...
Name resolved to 10.1.1.3
querying...
TCP port 42 (nameserver service): NOT LISTENING
portqry.exe -n files3 -e 42 -p TCP exits with return code 0x00000001.
Name server on TCP port 42??? Never heard of it. DNS = 53. Any ideas? Many
thanks for all your help...
Here is the complete output...
=============================================
Starting portqry.exe -n files3 -e 135 -p TCP ...
files3
Attempting to resolve name to IP address...
Name resolved to 10.1.1.3
querying...
TCP port 135 (epmap service): LISTENING
Using ephemeral source port
Querying Endpoint Mapper Database...
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncalrpc:[dhcpcsvc]
UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
ncalrpc:[W32TIME_ALT]
UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
ncacn_np:\\\\FILES3[\\PIPE\\W32TIME_ALT]
UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
ncacn_np:\\\\FILES3[\\pipe\\tapsrv]
UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
ncalrpc:[tapsrvlpc]
UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
ncalrpc:[unimdmsvc]
UUID: 50abc2a4-574d-40b3-9d66-ee4fd5fba076
ncacn_ip_tcp:10.1.1.3[1357]
UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncalrpc:[OLEB46E256106A348C6972E19CEB86D]
UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncacn_ip_tcp:10.1.1.3[1090]
UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncalrpc:[DHCPSERVERLPC]
UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncalrpc:[OLEB46E256106A348C6972E19CEB86D]
UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncacn_ip_tcp:10.1.1.3[1090]
UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncalrpc:[DHCPSERVERLPC]
UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncalrpc:[OLE912A611DF0B64360AA38DBFEC079]
UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncacn_ip_tcp:10.1.1.3[1078]
UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncalrpc:[LRPC0000070c.00000001]
UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncalrpc:[OLE912A611DF0B64360AA38DBFEC079]
UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncacn_ip_tcp:10.1.1.3[1078]
UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncalrpc:[LRPC0000070c.00000001]
UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncalrpc:[OLE912A611DF0B64360AA38DBFEC079]
UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncacn_ip_tcp:10.1.1.3[1078]
UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncalrpc:[LRPC0000070c.00000001]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000004b4.00000001]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000004b4.00000001]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000004b4.00000001]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000004b4.00000001]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_np:\\\\FILES3[\\PIPE\\lsass]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[audit]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[securityevent]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[protected_storage]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_np:\\\\FILES3[\\PIPE\\protected_storage]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[dsrole]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_ip_tcp:10.1.1.3[1025]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_np:\\\\FILES3[\\PIPE\\lsass]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[audit]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[securityevent]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[protected_storage]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_np:\\\\FILES3[\\PIPE\\protected_storage]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[dsrole]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_ip_tcp:10.1.1.3[1025]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_np:\\\\FILES3[\\PIPE\\lsass]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[audit]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[securityevent]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[protected_storage]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_np:\\\\FILES3[\\PIPE\\protected_storage]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[dsrole]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_ip_tcp:10.1.1.3[1025]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_np:\\\\FILES3[\\PIPE\\lsass]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[audit]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[securityevent]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[protected_storage]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_np:\\\\FILES3[\\PIPE\\protected_storage]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[dsrole]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_ip_tcp:10.1.1.3[1025]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[NTDS_LPC]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_http:10.1.1.3[1027]
UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_np:\\\\FILES3[\\PIPE\\lsass]
UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[audit]
UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[securityevent]
UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[protected_storage]
UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_np:\\\\FILES3[\\PIPE\\protected_storage]
UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[dsrole]
UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_ip_tcp:10.1.1.3[1025]
UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[NTDS_LPC]
UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_http:10.1.1.3[1027]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_np:\\\\FILES3[\\PIPE\\lsass]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[audit]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[securityevent]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[protected_storage]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_np:\\\\FILES3[\\PIPE\\protected_storage]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[dsrole]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_ip_tcp:10.1.1.3[1025]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[NTDS_LPC]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_http:10.1.1.3[1027]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_np:\\\\FILES3[\\PIPE\\lsass]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[audit]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[securityevent]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[protected_storage]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_np:\\\\FILES3[\\PIPE\\protected_storage]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[dsrole]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_ip_tcp:10.1.1.3[1025]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[NTDS_LPC]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_http:10.1.1.3[1027]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_np:\\\\FILES3[\\PIPE\\lsass]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[audit]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[securityevent]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[protected_storage]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_np:\\\\FILES3[\\PIPE\\protected_storage]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[dsrole]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_ip_tcp:10.1.1.3[1025]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[NTDS_LPC]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_http:10.1.1.3[1027]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[OLECC4E9A8ACA114C36BF4EF4C2FDC0]
UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncalrpc:[wzcsvc]
UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncalrpc:[OLE6649563968BD42C8B8CC25172C71]
UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncacn_np:\\\\FILES3[\\PIPE\\atsvc]
UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncalrpc:[wzcsvc]
UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncalrpc:[OLE6649563968BD42C8B8CC25172C71]
UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncacn_np:\\\\FILES3[\\PIPE\\atsvc]
UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncalrpc:[wzcsvc]
UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncalrpc:[OLE6649563968BD42C8B8CC25172C71]
UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncacn_np:\\\\FILES3[\\PIPE\\atsvc]
UUID: 4da1c422-943d-11d1-acae-00c04fc2aa3f
ncacn_ip_tcp:10.1.1.3[3405]
Total endpoints found: 103
==== End of RPC Endpoint Mapper query response ====
portqry.exe -n files3 -e 135 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n files3 -e 389 -p BOTH ...
files3
Attempting to resolve name to IP address...
Name resolved to 10.1.1.3
querying...
TCP port 389 (ldap service): LISTENING
Using ephemeral source port
Sending LDAP query to TCP port 389...
currentdate: 07/19/2007 00:15:17 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=DOM
dsServiceName: CN=NTDS
Settings,CN=FILES3,CN=Servers,CN=DOM-Melbourne,CN=Sites,CN=Configuration,DC=DOM
namingContexts: DC=DOM
defaultNamingContext: DC=DOM
schemaNamingContext: CN=Schema,CN=Configuration,DC=DOM
configurationNamingContext: CN=Configuration,DC=DOM
rootDomainNamingContext: DC=DOM
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 8108582
supportedSASLMechanisms: GSSAPI
dnsHostName: files3.DOM
CN=FILES3,CN=Servers,CN=DOM-Melbourne,CN=Sites,CN=Configuration,DC=DOM
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 2
forestFunctionality: 0
domainControllerFunctionality: 2
======== End of LDAP query response ========
UDP port 389 (unknown service): LISTENING or FILTERED
Using ephemeral source port
Sending LDAP query to UDP port 389...
currentdate: 07/19/2007 00:15:21 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=DOM
dsServiceName: CN=NTDS
Settings,CN=FILES3,CN=Servers,CN=DOM-Melbourne,CN=Sites,CN=Configuration,DC=DOM
namingContexts: DC=DOM
defaultNamingContext: DC=DOM
schemaNamingContext: CN=Schema,CN=Configuration,DC=DOM
configurationNamingContext: CN=Configuration,DC=DOM
rootDomainNamingContext: DC=DOM
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 8108582
supportedSASLMechanisms: GSSAPI
dnsHostName: files3.DOM
CN=FILES3,CN=Servers,CN=DOM-Melbourne,CN=Sites,CN=Configuration,DC=DOM
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 2
forestFunctionality: 0
domainControllerFunctionality: 2
======== End of LDAP query response ========
UDP port 389 is LISTENING
portqry.exe -n files3 -e 389 -p BOTH exits with return code 0x00000000.
=============================================
Starting portqry.exe -n files3 -e 636 -p TCP ...
files3
Attempting to resolve name to IP address...
Name resolved to 10.1.1.3
querying...
TCP port 636 (ldaps service): LISTENING
portqry.exe -n files3 -e 636 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n files3 -e 3268 -p TCP ...
files3
Attempting to resolve name to IP address...
Name resolved to 10.1.1.3
querying...
TCP port 3268 (msft-gc service): LISTENING
Using ephemeral source port
Sending LDAP query to TCP port 3268...
currentdate: 07/19/2007 00:15:23 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=DOM
dsServiceName: CN=NTDS
Settings,CN=FILES3,CN=Servers,CN=DOM-Melbourne,CN=Sites,CN=Configuration,DC=DOM
namingContexts: DC=DOM
defaultNamingContext: DC=DOM
schemaNamingContext: CN=Schema,CN=Configuration,DC=DOM
configurationNamingContext: CN=Configuration,DC=DOM
rootDomainNamingContext: DC=DOM
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 8108582
supportedSASLMechanisms: GSSAPI
dnsHostName: files3.DOM
CN=FILES3,CN=Servers,CN=DOM-Melbourne,CN=Sites,CN=Configuration,DC=DOM
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 2
forestFunctionality: 0
domainControllerFunctionality: 2
======== End of LDAP query response ========
portqry.exe -n files3 -e 3268 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n files3 -e 3269 -p TCP ...
files3
Attempting to resolve name to IP address...
Name resolved to 10.1.1.3
querying...
TCP port 3269 (msft-gc-ssl service): LISTENING
portqry.exe -n files3 -e 3269 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n files3 -e 53 -p BOTH ...
files3
Attempting to resolve name to IP address...
Name resolved to 10.1.1.3
querying...
TCP port 53 (domain service): LISTENING
UDP port 53 (domain service): LISTENING
portqry.exe -n files3 -e 53 -p BOTH exits with return code 0x00000000.
=============================================
Starting portqry.exe -n files3 -e 88 -p BOTH ...
files3
Attempting to resolve name to IP address...
Name resolved to 10.1.1.3
querying...
TCP port 88 (kerberos service): LISTENING
UDP port 88 (kerberos service): LISTENING or FILTERED
portqry.exe -n files3 -e 88 -p BOTH exits with return code 0x00000002.
=============================================
Starting portqry.exe -n files3 -e 445 -p TCP ...
files3
Attempting to resolve name to IP address...
Name resolved to 10.1.1.3
querying...
TCP port 445 (microsoft-ds service): LISTENING
portqry.exe -n files3 -e 445 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n files3 -e 137 -p UDP ...
files3
Attempting to resolve name to IP address...
Name resolved to 10.1.1.3
querying...
UDP port 137 (netbios-ns service): LISTENING or FILTERED
Using ephemeral source port
Attempting NETBIOS adapter status query to UDP port 137...
Server's response: MAC address 001485f46acc
UDP port: LISTENING
portqry.exe -n files3 -e 137 -p UDP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n files3 -e 138 -p UDP ...
files3
Attempting to resolve name to IP address...
Name resolved to 10.1.1.3
querying...
UDP port 138 (netbios-dgm service): LISTENING or FILTERED
portqry.exe -n files3 -e 138 -p UDP exits with return code 0x00000002.
=============================================
Starting portqry.exe -n files3 -e 139 -p TCP ...
files3
Attempting to resolve name to IP address...
Name resolved to 10.1.1.3
querying...
TCP port 139 (netbios-ssn service): LISTENING
portqry.exe -n files3 -e 139 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n files3 -e 42 -p TCP ...
files3
Attempting to resolve name to IP address...
Name resolved to 10.1.1.3
querying...
TCP port 42 (nameserver service): NOT LISTENING
portqry.exe -n files3 -e 42 -p TCP exits with return code 0x00000001.

set q=srv
_ldap._tcp.dc._msdcs.DOM

Server: files3.DOM
Address: 10.1.1.3
priority = 0
weight = 100
port = 389
svr hostname = files3.DOM
priority = 0
weight = 100
port = 389
svr hostname = files1.DOM
files3.DOM internet address = 10.1.1.3
files1.DOM internet address = 10.1.1.1
So srv can be located. The same error happens when I try and add the machine
to the domain. Both existing DCs can be pinged, and an nmap of them
both
from
the remote site returns hundreds of open ports, with all the expected ones
marked opened. I am absolutely stumped - any ideas??? I've run DCDIAG on a
domain controller and everything is fine... please help :)
Cheers,
Karl

jwd

2007-07-18 13:08:04 UTC

Permalink

Is this a new domain? I hope so. You are using a single label DNS domain
name. This will cause you endless problems.

If it is new start again!

Best Regards
Joe Dunn MCSE

set q=srv
_ldap._tcp.dc._msdcs.DOM

Kolchak

2007-07-19 00:22:01 UTC

Permalink

Its a VERY old domain (10 years) so can't start fresh. Is it possible to
rename domains??? Read somewhere you could, may be time to do that :)

Cheers,
Karl

Post by jwd
Is this a new domain? I hope so. You are using a single label DNS domain
name. This will cause you endless problems.
If it is new start again!
Best Regards
Joe Dunn MCSE

set q=srv
_ldap._tcp.dc._msdcs.DOM

jwd

2007-07-19 07:22:00 UTC

Permalink

Renaming domains is only possible in Windows 2003. I presume your
forest/domain is windows 2000.

I know this is no use for your current problem but I would seriously
consider planning for a new forest in the not too distant future. Was it an
upgrade from NT to 2000 when 2000 was released?

Post by Kolchak
Its a VERY old domain (10 years) so can't start fresh. Is it possible to
rename domains??? Read somewhere you could, may be time to do that :)
Cheers,
Karl

Post by jwd
Is this a new domain? I hope so. You are using a single label DNS domain
name. This will cause you endless problems.
If it is new start again!
Best Regards
Joe Dunn MCSE

set q=srv
_ldap._tcp.dc._msdcs.DOM

Kolchak

2007-07-19 07:52:04 UTC

Permalink

Hey there,

Nup - this is a Win 2k3 domain - driving me nuts! Any advice on renaming 2k3
domain???

Still no joy all day (another 8 hours!). Ran dcdiag and got the following:

D:\Shares\Users\me\x86>dcdiag /test:dcpromo /DnsDomain:DOM /ReplicaDC
Starting test: DcPromo
The DNS configuration is sufficient to allow this computer to be
promoted
as a replica domain controller in the DOM domain.

Messages logged below this line indicate whether this domain controller
will be able to dynamically register DNS records required for the
location of this DC by other devices on the network. If any
misconfiguration is detected, it might prevent dynamic DNS registration
of some records, but does not prevent successful completion of the
Active
Directory Installation Wizard. However, we recommend fixing the reported
problems now, unless you plan to manually update the DNS database.

This domain controller cannot register domain controller Locator DNS
records. This is because it cannot locate a DNS server authoritative for
the zone DOM. This is due to one of the following:

1. One or more DNS servers involved in the name resolution of the DOM
name are not responding or contain incorrect delegation of the DNS
zones;
or

2. The DNS server that this computer is configured with contains
incorrect root hints.

The list of such DNS servers might include the DNS servers with which
this computer is configured for name resolution and the DNS servers
responsible for the following zones: DOM

Verify the correctness of the specified domain name and contact your
network/DNS administrator to fix the problem.

You can also manually add the records specified in the
%systemroot%\system32\config\netlogon.dns file.

......................... sh-files1 failed test DcPromo

Post by jwd
Renaming domains is only possible in Windows 2003. I presume your
forest/domain is windows 2000.
I know this is no use for your current problem but I would seriously
consider planning for a new forest in the not too distant future. Was it an
upgrade from NT to 2000 when 2000 was released?

Post by Kolchak
Its a VERY old domain (10 years) so can't start fresh. Is it possible to
rename domains??? Read somewhere you could, may be time to do that :)
Cheers,
Karl

Post by jwd
Is this a new domain? I hope so. You are using a single label DNS domain
name. This will cause you endless problems.
If it is new start again!
Best Regards
Joe Dunn MCSE

set q=srv
_ldap._tcp.dc._msdcs.DOM

jwd

2007-07-19 14:58:01 UTC

Permalink

See this link regarding renaming a domain. I am not saying this is the only
solution to your problem and renaming a domain is not by any means an easy
operation and must only be undertaken after detailed planning and thorough
understanding of the consequences.

http://technet.microsoft.com/en-us/windowsserver/bb405948.aspx

Also here is a link about single label domain names. You will see that the
main problems with single label domains are DNS resolution and dynamic
updates of service records. This is the likely cause of your errors.

http://support.microsoft.com/kb/300684

Best Regards
Joe Dunn MCSE

Post by Kolchak
Hey there,
Nup - this is a Win 2k3 domain - driving me nuts! Any advice on renaming 2k3
domain???
D:\Shares\Users\me\x86>dcdiag /test:dcpromo /DnsDomain:DOM /ReplicaDC
Starting test: DcPromo
The DNS configuration is sufficient to allow this computer to be
promoted
as a replica domain controller in the DOM domain.
Messages logged below this line indicate whether this domain controller
will be able to dynamically register DNS records required for the
location of this DC by other devices on the network. If any
misconfiguration is detected, it might prevent dynamic DNS registration
of some records, but does not prevent successful completion of the
Active
Directory Installation Wizard. However, we recommend fixing the reported
problems now, unless you plan to manually update the DNS database.
This domain controller cannot register domain controller Locator DNS
records. This is because it cannot locate a DNS server authoritative for
1. One or more DNS servers involved in the name resolution of the DOM
name are not responding or contain incorrect delegation of the DNS
zones;
or
2. The DNS server that this computer is configured with contains
incorrect root hints.
The list of such DNS servers might include the DNS servers with which
this computer is configured for name resolution and the DNS servers
responsible for the following zones: DOM
Verify the correctness of the specified domain name and contact your
network/DNS administrator to fix the problem.
You can also manually add the records specified in the
%systemroot%\system32\config\netlogon.dns file.
......................... sh-files1 failed test DcPromo

Post by Kolchak
Its a VERY old domain (10 years) so can't start fresh. Is it possible to
rename domains??? Read somewhere you could, may be time to do that :)
Cheers,
Karl

Post by jwd
Is this a new domain? I hope so. You are using a single label DNS domain
name. This will cause you endless problems.
If it is new start again!
Best Regards
Joe Dunn MCSE

set q=srv
_ldap._tcp.dc._msdcs.DOM

Jorge Silva

2007-07-18 14:15:01 UTC

Permalink

Hi
Adding additonal references:
Active Directory in Networks Segmented by Firewalls

http://www.microsoft.com/downloads/details.aspx?FamilyID=c2ef3846-43f0-4caf-9767-a9166368434e&DisplayLang=en

Active Directory Replication over Firewalls

http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/activedirectory/deploy/confeat/adrepfir.mspx
--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

set q=srv
_ldap._tcp.dc._msdcs.DOM