RPC SERVER UNAVAILABLE AND NAMESERVER PORT 42

I ran this command on my Domain COntroller server

dcdiag /e /v /f:c:\dcdiag.txt

all tests passed except for the ones below.

Starting test: DFSREvent

         The DFS Replication Event Log.
         The event log DFS Replication on server serverB.COMPANY.local could not be queried, error 0x6ba "The RPC server is unavailable."

         ......................... serverB failed test DFSREvent

      Starting test: SysVolCheck

         * The File Replication Service SYSVOL ready test
         File Replication Service's SYSVOL is ready
         ......................... serverB passed test SysVolCheck

      Starting test: KccEvent

         * The KCC Event log test
         The event log Directory Service on server serverB.COMPANY.local could not be queried, error 0x6ba "The RPC server is unavailable."

         ......................... serverB failed test KccEvent


------------portqry ui ------------------------------------------------------------------
I also ran the portqry tool and this is the output


....................

.....supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 6
forestFunctionality: 6
domainControllerFunctionality: 6


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

UDP port 389 is LISTENING

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

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


Querying target system called:

 serverb

Attempting to resolve name to IP address...

Name resolved to 10.X.X.X

querying...

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

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


Querying target system called:

 serverb

Attempting to resolve name to IP address...

Name resolved to 10.X.X.X

querying...

TCP port 3268 (msft-gc service): LISTENING

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

LDAP query response:


currentdate: 05/29/2015 17:41:41 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=company,DC=local
dsServiceName: CN=NTDS Settings,CN=serverb,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=company,DC=local
namingContexts: DC=company,DC=local
defaultNamingContext: DC=company,DC=local
schemaNamingContext: CN=Schema,CN=Configuration,DC=company,DC=local
configurationNamingContext: CN=Configuration,DC=company,DC=local
rootDomainNamingContext: DC=company,DC=local
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 35641
supportedSASLMechanisms: GSSAPI
dnsHostName: serverb.company.local
ldapServiceName: company.local:serverb$@company.LOCAL
serverName: CN=serverb,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=company,DC=local
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 6
forestFunctionality: 6
domainControllerFunctionality: 6


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

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


Querying target system called:

 serverb

Attempting to resolve name to IP address...

Name resolved to 10.X.X.X

querying...

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

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


Querying target system called:

 serverb

Attempting to resolve name to IP address...

Name resolved to 10.X.X.X

querying...

TCP port 53 (domain service): LISTENING

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

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


Querying target system called:

 serverb

Attempting to resolve name to IP address...

Name resolved to 10.X.X.X

querying...

TCP port 88 (kerberos service): LISTENING

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

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


Querying target system called:

 serverb

Attempting to resolve name to IP address...

Name resolved to 10.X.X.X

querying...

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

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


Querying target system called:

 serverb

Attempting to resolve name to IP address...


Name resolved to 10.X.X.X

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 000c299db6c5
UDP port: LISTENING
portqry.exe -n serverb -e 137 -p UDP exits with return code 0x00000000.
=============================================

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


Querying target system called:

 serverb

Attempting to resolve name to IP address...


Name resolved to 10.X.X.X

querying...

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

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


Querying target system called:

 serverb

Attempting to resolve name to IP address...

Name resolved to 10.X.X.X

querying...

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

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


Querying target system called:

 serverb

Attempting to resolve name to IP address...

Name resolved to 10.X.X.X

querying...

TCP port 42 (nameserver service): FILTERED
portqry.exe -n serverb -e 42 -p TCP exits with return code 0x00000002.

-----------------------------------------------------------------------------------------

The last error - port 42 TCP - is that something to be alarmed about.
DO i need to manually open port 42 both inbound and outbound on both the domain controllers

ENVIRONMENT
I have two domain controllers, windows 2012 r2.
no dfs name spaces

Running this command also shows no errors
repadmin /showrepl



Any help appreciated
3MusketeersAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

3MusketeersAuthor Commented:
additional dcdiag error info from serverB

Starting test: DFSREvent

         The DFS Replication Event Log.
         There are warning or error events within the last 24 hours after the SYSVOL has been shared.  Failing SYSVOL replication

         problems may cause Group Policy problems.
         A warning event occurred.  EventID: 0x80001396

            Time Generated: 05/28/2015   21:00:14

            Event String:

            The DFS Replication service is stopping communication with partner ServerA for replication group Domain System Volume due to an error. The service will retry the connection periodically.

             

            Additional Information:

            Error: 9036 (Paused for backup or restore)

            Connection ID: CFB381EA-F941-4AA2-8657-E66DD3EDC238

            Replication Group ID: 8A995679-5B82-42C9-B785-33677D4CD2AD
0
compdigit44Commented:
So you have two servers A and B and B is the one with the problems correct?

Any changes recently? Windows firewall on/off? AV software installed?

If nothing has changed you could demote the problem B server ... remove it  from AD cleanly then promote it again
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.