No endpoints found
Hi,
in the soamanager the webservice has an endpoint but anyway a I get this message
Web Service Navigator.
I am entering the WSDL URL of the Web service and on testing I get the message
No endpoints found for this Web service.
Pls. help me in this matter
Bye
Sw
check your URL... it need to have the correct port number, WSDL version etc..
http://<host_name>:<port_number>/sap/bc/soap/rfc
[Refer to this link>>|http://help.sap.com/saphelp_47x200/helpdata/en/2d/64d01de74911d6b2e400508b6b8a93/content.htm]
Similar Messages
-
Web Service Error - no service endpoints found
Hi,
I tried to create a web service deployable proxy project to consume an external third party web service url. There were no files generated for Logical Ports and Proxy Classes, though there are files generated for WSDL and SEIs. A further test on http://ip:port/index.html -> web service -> Enter the WSDL URL of the Web service -> No Service Endpoints Found, prove that something wrong with the url.
Any idea for me to check what goes wrong with the web service url? or could it due to firewall?In the meantime, there are also consuming my java-created web service using the test tool from http://www.soapclient.com/soaptest.html.
Error given as below, from the
wsse:InvalidSecurity0012BF1423AB0047000000350000065C00041741F13F5CDC : Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:EMMWSWsd'; Key name:'SoapRequestWrapper' key value:'sendMOtext'; 0012BF1423AB0047000000350000065C00041741F13F5CDC : Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:EMMWSWsd'; Key name:'SoapRequestWrapper' key value:'sendMOtext';
From my application log, error shown as below:
#1.5#0012BF1423AB0047000000360000065C00041741F13F5DA5#1151471894671#com.sap.security.core.server.ws.service.ServerSecurityProtocol#sap.com/AdapterWSTabEAR#com.sap.security.core.server.ws.service.ServerSecurityProtocol.handleRequest#J2EE_GUEST#230####800311f0066511dba3770012bf1423ab#SAPEngine_Application_Thread[impl:3]_5##0#0#Error#1#/System/Security/WS/SecurityProtocol#Java###An error occurred while processing the message security. Reason: . See trace entry .#3#com.sap.engine.interfaces.webservices.runtime.OperationNotFoundException#Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:EMMWSWsd'; Key name:'SoapRequestWrapper' key value:'sendMOtext'; #[no trace for com.sap.security.core.server.ws.service.ServerSecurityProtocol (severity above PATH)]#
#1.5#0012BF1423AB0049000000370000065C00041741F475BD3F#1151471948578#com.sap.security.core.server.ws.service.ServerSecurityProtocol#sap.com/AdapterWSTabEAR#com.sap.security.core.server.ws.service.ServerSecurityProtocol.handleRequest#J2EE_GUEST#230####a024a020066511db954d0012bf1423ab#SAPEngine_Application_Thread[impl:3]_9##0#0#Error#1#/System/Security/WS/SecurityProtocol#Java###An error occurred while processing the message security. Reason: . See trace entry .#3#com.sap.engine.interfaces.webservices.runtime.OperationNotFoundException#Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:EMMWSWsd'; Key name:'SoapRequestWrapper' key value:'sendMOtext'; #[no trace for com.sap.security.core.server.ws.service.ServerSecurityProtocol (severity above PATH)]#
Anyone has any idea what's the rootcause of all the incompatibility? -
No endpoints found for interface
Hi All,
I have the following scenario: RFC in the backend system (ECC 6.0 SP09 no EhP's) and PI 7.1 as an Integration Broker.
I have imported the RFC into Enterprise Services Repository and done the necessary tasks to configure an Enterprise Service.
After that I have published the Interface to the Services Registry, Testing the Interface in WSNavigator is working fine.
I have imported the Enterprise Service into Web Dynpro as a model and when running the Web Dynpro application I am receiving the following error:
com.sap.esi.esp.service.server.query.discovery.ExtendedServiceException: no endpoints found for interface TreeInformationQuery_Out
defaultTrace:
Caused by: com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for web service mass config parameters service reference ID 'TreeInformationQuery_Out_FICSIT_BASIC' and application name 'demo.sap.com/ficsit~tree'. Check mass configuration has been done properly.
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:522)
Any idea's?
Regards,
RidouanHi Sergei,
My backend system is ECC 6.0 SP9 (no EhP's) and therefore I can't use the trx SOAMANAGER.
I have imported an RFC from the ECC system into the PI 7.1 Enterprise Services Repository (Builder) and then published the Service (from Sender Agreement) into Services Registry also on the PI 7.1 system.
Testing the service in WS Navigator is working fine, I can see an endpoint here.
Also testing the WSDL with third-party application is working fine.
JAVA Web Dynpro is given me the error: no endpoints found for interface...
Thanks again.
Regards,
Ridouan -
Error. in WS Navigator - no endpoints found for interface
Dear Friends,
I have created a new Enterprise Service Interface and implemented in ABAP. After the implementation I used SOAMANAGER to create the endpoint and publish the service using WSPUBLISH to Service Registry. When I tested this service from SOA Management application(SOAMANAGER), the endpoint is working very good, but when I am testing this service from Service Registry, it is now showing any endpoint in the 'Enter Input Parameters' Step. Also when I am trying to search the Service by using 'Search by Logical Destination', it shows the Service and when I select it, it shows an error message, "no endpoints found for interface (<namespace>/document)<Service Interface Name>_Document".
If some one knows about this issue, please advice me to do next steps.
Also I am planning to call this service from Visual Composer, I have configured the two logical destinations over there, also the service registry, even though, when i am searching the service, it shows an error like "Could not complete search".
Please advice me for the above issue also.
Thanks in advance
VipindasHi,
If you have configured and tested from SOAMANAGER (which opens WSnavigator) then it is configured correctly. May be you are using wrong WSDL address.
Copy url of wsdl from SOAMANGER test screen and use it directly in WSnavigator for testing.
Regarding publishing of service WSPUBLISH should be able to publish correct service into service registry, but if for any reason it is not working then you can "publish" it directly from service registry by using publish option and provide url of wsdl from above option.
If for any reason VC is unable to search service registry then create destination template for your every service by providing WSDL and use it in VC.
Regards,
Gourav -
Webservice: No endpoints found
Hi gurus!
I'm not sure on witch forum to post this thread... so here goes...
I'm trying to create a webservice for an RFC function module (ZBAPI_HELLO_WORLD). I've already tried some manuals like http://help.sap.com/saphelp_nw70/helpdata/EN/0d/2eac5a56d7e345853fe9c935954ff1/content.htm, step by step, apparently everything works fine.
I go to SOAMANAGER, Web Service Administrator, select the service, verify that the endpoint is created, and everything seems OK.
However, I go to WSNAVIGATOR, enter the webservice (http://sapdes.bel.com.ve:8000/sap/bc/srt/rfc/sap/ZBAPIHELLOWORLD?sap-client=200&wsdl=1.1), but when I try to test it, I get the following error: No endpoints found for this Web service
I've tried deleting it and creating it again, and again, but so far nothing works, still the same error...
Am I missing something? some step I haven't seen?
Basically I'm using transactions SE37 to create the WS, and SOAMANAGER to test it, nothing more...
Appreciate any help!
JesusHi... I'm working on ECC 6.0, so transactions WSADMIN and WSCONFIG are not available, instead I use transaction SOAMANAGER.
I checked note 1113162, but my system already has the SP level where the note was distributed, so it's already applied. -
Webservcie: No endpoints found
Hi gurus!
I'm new to WebServices....
I'm trying to create a webservice for an RFC function module (ZBAPI_HELLO_WORLD). I've already tried some manuals like http://help.sap.com/saphelp_nw70/helpdata/EN/0d/2eac5a56d7e345853fe9c935954ff1/content.htm, step by step, apparently everything works fine.
I go to SOAMANAGER, Web Service Administrator, select the service, verify that the endpoint is created, and everything seems OK.
However, I go to WSNAVIGATOR, enter the webservice (http://sapdes.bel.com.ve:8000/sap/bc/srt/rfc/sap/ZBAPIHELLOWORLD?sap-client=200&wsdl=1.1), but when I try to test it, I get the following error: No endpoints found for this Web service
I've tried deleting it and creating it again, and again, but so far nothing works, still the same error...
Am I missing something? some step I haven't seen?
Basically I'm using transactions SE37 to create the WS, and SOAMANAGER to test it, nothing more...
Appreciate any help!
Jesuscheck your URL... it need to have the correct port number, WSDL version etc..
http://<host_name>:<port_number>/sap/bc/soap/rfc
[Refer to this link>>|http://help.sap.com/saphelp_47x200/helpdata/en/2d/64d01de74911d6b2e400508b6b8a93/content.htm] -
Service Registry: why do i need two bindings (wsdlDeployment and endPoint)
based on the technical note of Clemens Utschig "Enabling a Dynamic, Reusable SOA with Oracle BPEL Process Manager and Oracle Service Registry" i have one question:
why do i need two bindings (wsdlDeployment and endPoint) in my service in the service registry. if i only define the wsdlDeployment if get this messages:
<2006-12-07 09:39:02,559> <FATAL> <default.collaxa.cube.ws> no endpoint found - nothing to adjust
<2006-12-07 09:39:02,559> <WARN> <default.collaxa.cube.ws> Could not lookup base endpoint!
the problem of defining two bindings is that the url to my partner is redundant.Hi Clemens,
The UDDI Version 3.0.2 Specification (http://www.uddi.org/pubs/uddi_v3.htm) say this:
B.1.2 Using the "wsdlDeployment" value
Instead of directly providing the network address in the accessPoint, it is occasionally useful or necessary to provide this information through indirect means. One common scenario for such a behavior is when the accessPoint is embedded within a WSDL file. In such a scenario, the UDDI accessPoint contains the address of the WSDL file, and the client then must retrieve the WSDL file and extract the end point address from the WSDL file itself.
In this case, decorating the UDDI accessPoint with a useType="wsdlDeployment" is appropriate. A sample of such behavior is as follows:
<bindingTemplate bindingKey="uddi:example.org:catalog">
<description xml:lang="en">
Browse catalog Web service
</description>
<accessPoint useType="wsdlDeployment">
http://www.example.org/CatalogWebService/catalog.wsdl
</accessPoint>
<categoryBag>
<keyedReference keyName="uddi-org:types:wsdl"
keyValue="wsdlDeployment"
tModelKey="uddi:uddi.org:categorization:types"/>
</categoryBag>
</bindingTemplate>In the example above, a client would be able to parse the result of the bindingTemplate and determine the end point of the Web service within the WSDL file discovered in the accessPoint element. Note that the bindingTemplate has also been categorized with the "wsdlDeployment" value from the uddi.org:categorization:types scheme so that it can be discovered through a find_binding API call.
1) This means for me that providing one binding with useType=wsdlDeployment should be enough.
2) Sadly the "Business Service Control" of the Service Registry (Publish new WSDL service) does not create the correct structure needed by the bpel-engine. The "Publish new WSDL service" wizard just creates one service with one binding with useType=other (http). So if i want to reuse this published service from bpel (as a service consumer) i have to switch to the "Service Registry Admin Control" and create a second binding with useType=wsdlDeployment. But i don't want the developers to get inside the "Service Registry Admin Control"! They should only work with the "Business Service Control".
All this makes the usage of the service-registry very unhandy and reduce the acceptance for developers because of unnecessary manual steps and broken security principles.
My wish for this issue is that the "Publish new WSDL service" inside the "Business Service Control" of the Service Registry would additionlly create this needed binding with useType=wsdlDeployment.
Best Regards,
Harald Reinmueller -
ADPrep Migration from Windows Server 2003 to 2012 Foundation Server fails with error 0x80004005
Hi all,
Having a problem the forums and Google have been unsuccessful in helping me with. Server is Windows 2003 R2, migrating to Windows Server 2012 foundation. Have tried the AD Migration on the new 2012 Foundation server both as a standalone server
and a domain server member before running the migration. I get the following error:
ADPrep execution failed --> System.ComponentModel.Win32Exception (0x80004005): A device attached to the system is not functioning
I've checked the ADprep logs and have found the following:
[2013/01/22:11:15:01.000]
Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=abd97102-88dd-4013-a009-0e2c2f967ff6,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local.
[2013/01/22:11:15:01.001]
LDAP API ldap_search_s() finished, return code is 0x0
[2013/01/22:11:15:01.001]
Adprep checked to verify whether operation cn=abd97102-88dd-4013-a009-0e2c2f967ff6,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local has completed.
[Status/Consequence]
The operation GUID already exists so Adprep did not attempt to rerun this operation but is continuing.
[2013/01/22:11:15:01.001]
Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=134428a8-0043-48a6-bcda-63310d9ec4dd,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local.
[2013/01/22:11:15:01.001]
LDAP API ldap_search_s() finished, return code is 0x20
[2013/01/22:11:15:01.001]
Adprep verified the state of operation cn=134428a8-0043-48a6-bcda-63310d9ec4dd,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local.
[Status/Consequence]
The operation has not run or is not currently running. It will be run next.
[2013/01/22:11:15:01.021]
Adprep was unable to complete because the call back function failed.
[Status/Consequence]
Error message: Unable to access the computer "SERVER.apl.local". The network path was not found.
(0x80070035).
[User Action]
Check the log file ADPrep.log, in the C:\Windows\debug\adprep\logs\20130122111500 directory for more information.
DSID Info:
DSID: 0x1811132a
winerror = 0x1f
NT BUILD: 9200
NT BUILD: 16384
[2013/01/22:11:15:01.021]
Adprep was unable to update forest information.
[Status/Consequence]
Adprep requires access to existing forest-wide information from the schema master in order to complete this operation.
[User Action]
Check the log file, ADPrep.log, in the C:\Windows\debug\adprep\logs\20130122111500 directory for more information.
We did have AVAST Antivirus installed on the server but this was removed. Any idea's?
Jason.
Consultant | Nerd | Visionary. http://www.ethertech.com.au/ | http://www.deeperstates.com.auHi Biswajit et. al., thanks for your help thus far, it is greatly appreciated...
Unfortunately I had already disabled the NIC's on both hosts. They currently remain disabled. I've just tried turning off IPv6 as well and no luck.
PortQry came back fine (I think) :)
=============================================
Starting portqry.exe -n server.apl.local -e 135 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.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: f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7 Isolation Communication Endpoint
ncalrpc:[LRPC00001d40.00000001]
UUID: f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7 Isolation Communication Endpoint
ncalrpc:[LRPC00001448.00000001]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[OLE4EF57D32A0DB45F9A64653468D7C]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000012ac.00000001]
UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
ncacn_np:\\\\SERVER[\\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: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
ncalrpc:[W32TIME_ALT]
UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
ncacn_np:\\\\SERVER[\\PIPE\\W32TIME_ALT]
UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncalrpc:[OLE7C4E3B9B79D8492CBA384F149E08]
UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncacn_ip_tcp:10.0.0.3[1111]
UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncalrpc:[DHCPSERVERLPC]
UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncalrpc:[OLE7C4E3B9B79D8492CBA384F149E08]
UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncacn_ip_tcp:10.0.0.3[1111]
UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncalrpc:[DHCPSERVERLPC]
UUID: 3d267954-eeb7-11d1-b94e-00c04fa3080d
ncalrpc:[LRPC00000480.00000001]
UUID: 3d267954-eeb7-11d1-b94e-00c04fa3080d
ncacn_np:\\\\SERVER[\\pipe\\HydraLsPipe]
UUID: 3d267954-eeb7-11d1-b94e-00c04fa3080d
ncacn_ip_tcp:10.0.0.3[1092]
UUID: 12d4b7c8-77d5-11d1-8c24-00c04fa3080d
ncalrpc:[LRPC00000480.00000001]
UUID: 12d4b7c8-77d5-11d1-8c24-00c04fa3080d
ncacn_np:\\\\SERVER[\\pipe\\HydraLsPipe]
UUID: 12d4b7c8-77d5-11d1-8c24-00c04fa3080d
ncacn_ip_tcp:10.0.0.3[1092]
UUID: 493c451c-155c-11d3-a314-00c04fb16103
ncalrpc:[LRPC00000480.00000001]
UUID: 493c451c-155c-11d3-a314-00c04fb16103
ncacn_np:\\\\SERVER[\\pipe\\HydraLsPipe]
UUID: 493c451c-155c-11d3-a314-00c04fb16103
ncacn_ip_tcp:10.0.0.3[1092]
UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe
ncalrpc:[OLE43978C47C6F54B5499302BAB2F50]
UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe
ncacn_ip_tcp:10.0.0.3[1090]
UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe
ncalrpc:[LRPC00001060.00000001]
UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe
ncacn_np:\\\\SERVER[\\pipe\\WinsPipe]
UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45
ncalrpc:[OLE43978C47C6F54B5499302BAB2F50]
UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45
ncacn_ip_tcp:10.0.0.3[1090]
UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45
ncalrpc:[LRPC00001060.00000001]
UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45
ncacn_np:\\\\SERVER[\\pipe\\WinsPipe]
UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncalrpc:[OLE92F283EA5C2F497093CE6A52B7D8]
UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncacn_ip_tcp:10.0.0.3[1067]
UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncalrpc:[LRPC00000d10.00000001]
UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncalrpc:[OLE92F283EA5C2F497093CE6A52B7D8]
UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncacn_ip_tcp:10.0.0.3[1067]
UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncalrpc:[LRPC00000d10.00000001]
UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncalrpc:[OLE92F283EA5C2F497093CE6A52B7D8]
UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncacn_ip_tcp:10.0.0.3[1067]
UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncalrpc:[LRPC00000d10.00000001]
UUID: 50abc2a4-574d-40b3-9d66-ee4fd5fba076
ncacn_ip_tcp:10.0.0.3[1048]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000004d4.00000001]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:10.0.0.3[1032]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000004d4.00000001]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:10.0.0.3[1032]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000004d4.00000001]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:10.0.0.3[1032]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000004d4.00000001]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:10.0.0.3[1032]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_np:\\\\SERVER[\\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:\\\\SERVER[\\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.0.0.3[1026]
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.0.0.3[1027]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_np:\\\\SERVER[\\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:\\\\SERVER[\\PIPE\\protected_storage]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[dsrole]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_ip_tcp:10.0.0.3[1026]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[NTDS_LPC]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_http:10.0.0.3[1027]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_np:\\\\SERVER[\\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:\\\\SERVER[\\PIPE\\protected_storage]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[dsrole]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_ip_tcp:10.0.0.3[1026]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[NTDS_LPC]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_http:10.0.0.3[1027]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_np:\\\\SERVER[\\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:\\\\SERVER[\\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.0.0.3[1026]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[NTDS_LPC]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_http:10.0.0.3[1027]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_np:\\\\SERVER[\\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:\\\\SERVER[\\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.0.0.3[1026]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[NTDS_LPC]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_http:10.0.0.3[1027]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_np:\\\\SERVER[\\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:\\\\SERVER[\\PIPE\\protected_storage]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[dsrole]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_ip_tcp:10.0.0.3[1026]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[NTDS_LPC]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_http:10.0.0.3[1027]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_np:\\\\SERVER[\\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:\\\\SERVER[\\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.0.0.3[1026]
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.0.0.3[1027]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[OLE8B33809919104CE5B44970B01637]
UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncalrpc:[wzcsvc]
UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncalrpc:[OLE396AE4FBEFCC4DD2B44D0F0A3691]
UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncacn_np:\\\\SERVER[\\PIPE\\atsvc]
UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncalrpc:[wzcsvc]
UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncalrpc:[OLE396AE4FBEFCC4DD2B44D0F0A3691]
UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncacn_np:\\\\SERVER[\\PIPE\\atsvc]
UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncalrpc:[wzcsvc]
UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncalrpc:[OLE396AE4FBEFCC4DD2B44D0F0A3691]
UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncacn_np:\\\\SERVER[\\PIPE\\atsvc]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncalrpc:[DNSResolver]
Total endpoints found: 125
==== End of RPC Endpoint Mapper query response ====
portqry.exe -n server.apl.local -e 135 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 389 -p BOTH ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 389 (ldap service): LISTENING
Using ephemeral source port
Sending LDAP query to TCP port 389...
LDAP query response:
currentdate: 01/28/2013 14:11:54 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=apl,DC=local
dsServiceName: CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
namingContexts: DC=apl,DC=local
defaultNamingContext: DC=apl,DC=local
schemaNamingContext: CN=Schema,CN=Configuration,DC=apl,DC=local
configurationNamingContext: CN=Configuration,DC=apl,DC=local
rootDomainNamingContext: DC=apl,DC=local
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 1310788
supportedSASLMechanisms: GSSAPI
dnsHostName: SERVER.apl.local
ldapServiceName: apl.local:[email protected]
serverName: CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 2
forestFunctionality: 2
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: 01/28/2013 14:11:57 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=apl,DC=local
dsServiceName: CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
namingContexts: DC=apl,DC=local
defaultNamingContext: DC=apl,DC=local
schemaNamingContext: CN=Schema,CN=Configuration,DC=apl,DC=local
configurationNamingContext: CN=Configuration,DC=apl,DC=local
rootDomainNamingContext: DC=apl,DC=local
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 1310788
supportedSASLMechanisms: GSSAPI
dnsHostName: SERVER.apl.local
ldapServiceName: apl.local:[email protected]
serverName: CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 2
forestFunctionality: 2
domainControllerFunctionality: 2
======== End of LDAP query response ========
UDP port 389 is LISTENING
portqry.exe -n server.apl.local -e 389 -p BOTH exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 636 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 636 (ldaps service): LISTENING
portqry.exe -n server.apl.local -e 636 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 3268 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 3268 (msft-gc service): LISTENING
Using ephemeral source port
Sending LDAP query to TCP port 3268...
LDAP query response:
currentdate: 01/28/2013 14:11:57 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=apl,DC=local
dsServiceName: CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
namingContexts: DC=apl,DC=local
defaultNamingContext: DC=apl,DC=local
schemaNamingContext: CN=Schema,CN=Configuration,DC=apl,DC=local
configurationNamingContext: CN=Configuration,DC=apl,DC=local
rootDomainNamingContext: DC=apl,DC=local
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 1310788
supportedSASLMechanisms: GSSAPI
dnsHostName: SERVER.apl.local
ldapServiceName: apl.local:[email protected]
serverName: CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 2
forestFunctionality: 2
domainControllerFunctionality: 2
======== End of LDAP query response ========
portqry.exe -n server.apl.local -e 3268 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 3269 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 3269 (msft-gc-ssl service): LISTENING
portqry.exe -n server.apl.local -e 3269 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 53 -p BOTH ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 53 (domain service): LISTENING
UDP port 53 (domain service): LISTENING
portqry.exe -n server.apl.local -e 53 -p BOTH exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 88 -p BOTH ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 88 (kerberos service): LISTENING
UDP port 88 (kerberos service): LISTENING or FILTERED
portqry.exe -n server.apl.local -e 88 -p BOTH exits with return code 0x00000002.
=============================================
Starting portqry.exe -n server.apl.local -e 445 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 445 (microsoft-ds service): LISTENING
portqry.exe -n server.apl.local -e 445 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 137 -p UDP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.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 000423c733ec
UDP port: LISTENING
portqry.exe -n server.apl.local -e 137 -p UDP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 138 -p UDP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
UDP port 138 (netbios-dgm service): LISTENING or FILTERED
portqry.exe -n server.apl.local -e 138 -p UDP exits with return code 0x00000002.
=============================================
Starting portqry.exe -n server.apl.local -e 139 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 139 (netbios-ssn service): LISTENING
portqry.exe -n server.apl.local -e 139 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 42 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 42 (nameserver service): LISTENING
portqry.exe -n server.apl.local -e 42 -p TCP exits with return code 0x00000000.
Jason.
Consultant | Nerd | Visionary. http://www.ethertech.com.au/ | http://www.deeperstates.com.au -
Domain Controllers not replicating
Hi All
Domain name: abc.com
DC1 - Windows Server 2003 R2 (Physical Server) - 192.168.1.1
DC2 - Windows Server 2012 (Virtual Machine) - 192.168.1.2
Somehow DC1 doesn't replicated to DC2.
netdom query fsmo's result:
Schema master DC1.abc.COM
Domain naming master DC1.abc.COM
PDC DC1.abc.COM
RID pool manager DC1.abc.COM
Infrastructure master DC1.abc.COM
The command completed successfully.
I run dcdiag in DC1:
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site\DC1
Starting test: Connectivity
The host bd9e6e75-ec75-4c6b-be1b-ebef58146bbe._msdcs.abc.COM could not b
e resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(bd9e6e75-ec75-4c6b-be1b-ebef58146bbe._msdcs.abc.COM) couldn't be
resolved, the server name (DC1.abc.COM) resolved to the IP address
(192.168.1.1) and was pingable. Check that the IP address is
registered correctly with the DNS server.
......................... DC1 failed test Connectivity
Doing primary tests
Testing server: Default-First-Site\DC1
Skipping all tests, because server DC1 is
not responding to directory service requests
Running partition tests on : TAPI3Directory
Starting test: CrossRefValidation
......................... TAPI3Directory passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... TAPI3Directory passed test CheckSDRefDom
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : abc
Starting test: CrossRefValidation
......................... abc passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... abc passed test CheckSDRefDom
Running enterprise tests on : abc.COM
Starting test: Intersite
......................... abc.COM passed test Intersite
Starting test: FsmoCheck
......................... abc.COM passed test FsmoCheck
But funny thing is I able to ping DC1 name from DC2 and workstations:
C:\Users\User>ping dc1
Pinging dc1.abc.com [192.168.1.1] with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=128
Reply from 192.168.1.1: bytes=32 time<1ms TTL=128
Reply from 192.168.1.1: bytes=32 time<1ms TTL=128
Reply from 192.168.1.1: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
I also run repadmin on DC1,
Result:
C:\>repadmin /showrepl /all /verbose
repadmin running command /showrepl against server localhost
Default-First-Site\DC1
DC Options: IS_GC
Site Options: (none)
DC object GUID: bd9e6e75-ec75-4c6b-be1b-ebef58146bbe
DC invocationID: bd9e6e75-ec75-4c6b-be1b-ebef58146bbe
==== INBOUND NEIGHBORS ======================================
DC=ABC,DC=COM
Default-First-Site\DC2 via RPC
DC object GUID: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c
Address: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c._msdcs.ABC.COM
DC invocationID: 7b99d5b5-1757-4533-9976-907907e99eff
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
USNs: 2190434/OU, 2190434/PU
Last attempt @ 2014-05-21 15:14:40 failed, result 1753 (0x6d9):
There are no more endpoints available from the endpoint mapper.
1400 consecutive failure(s).
Last success @ 2014-05-20 15:38:26.
CN=Configuration,DC=ABC,DC=COM
Default-First-Site\DC2 via RPC
DC object GUID: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c
Address: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c._msdcs.ABC.COM
DC invocationID: 7b99d5b5-1757-4533-9976-907907e99eff
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
USNs: 2180668/OU, 2180668/PU
Last attempt @ 2014-05-21 14:54:49 failed, result 1753 (0x6d9):
There are no more endpoints available from the endpoint mapper.
118 consecutive failure(s).
Last success @ 2014-05-17 00:54:43.
CN=Schema,CN=Configuration,DC=ABC,DC=COM
Default-First-Site\DC2 via RPC
DC object GUID: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c
Address: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c._msdcs.ABC.COM
DC invocationID: 7b99d5b5-1757-4533-9976-907907e99eff
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
USNs: 2110088/OU, 2110088/PU
Last attempt @ 2014-05-21 14:55:15 failed, result 1753 (0x6d9):
There are no more endpoints available from the endpoint mapper.
110 consecutive failure(s).
Last success @ 2014-05-17 00:54:43.
DC=DomainDnsZones,DC=ABC,DC=COM
Default-First-Site\DC2 via RPC
DC object GUID: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c
Address: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c._msdcs.ABC.COM
DC invocationID: 7b99d5b5-1757-4533-9976-907907e99eff
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
USNs: 2190524/OU, 2190524/PU
Last attempt @ 2014-05-21 14:54:24 failed, result 1256 (0x4e8):
The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
32 consecutive failure(s).
Last success @ 2014-05-20 15:38:27.
DC=ForestDnsZones,DC=ABC,DC=COM
Default-First-Site\DC2 via RPC
DC object GUID: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c
Address: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c._msdcs.ABC.COM
DC invocationID: 7b99d5b5-1757-4533-9976-907907e99eff
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
USNs: 2106507/OU, 2106507/PU
Last attempt @ 2014-05-21 14:54:24 failed, result 1256 (0x4e8):
The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
507 consecutive failure(s).
Last success @ 2014-04-30 16:48:21.
==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============
CN=Configuration,DC=ABC,DC=COM
Default-First-Site\DC2 via RPC
DC object GUID: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c
Address: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c._msdcs.ABC.COM
WRITEABLE
Last attempt @ (never) was successful.
CN=Schema,CN=Configuration,DC=ABC,DC=COM
Default-First-Site\DC2 via RPC
DC object GUID: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c
Address: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c._msdcs.ABC.COM
WRITEABLE
Last attempt @ 2014-05-17 00:55:01 was successful.
DC=DomainDnsZones,DC=ABC,DC=COM
Default-First-Site\DC2 via RPC
DC object GUID: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c
Address: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c._msdcs.ABC.COM
WRITEABLE
Last attempt @ (never) was successful.
DC=ForestDnsZones,DC=ABC,DC=COM
Default-First-Site\DC2 via RPC
DC object GUID: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c
Address: 2bdd0be7-3dfa-4158-b8bd-c54124226e6c._msdcs.ABC.COM
WRITEABLE
Last attempt @ (never) was successful.
==== KCC CONNECTION OBJECTS ============================================
Connection --
Connection name : 2e2755c0-c2b1-484b-a0b2-489926271fd4
Server DNS name : DC1.ABC.COM
Server DN name : CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Sit
e,CN=Sites,CN=Configuration,DC=ABC,DC=COM
Source: Default-First-Site\DC2
******* 1382 CONSECUTIVE FAILURES since 2014-05-20 15:38:27
Last error: 1256 (0x4e8):
The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
TransportType: intrasite RPC
options: isGenerated
ReplicatesNC: DC=ABC,DC=COM
Reason: StaleServersTopology
Replica link has been added.
ReplicatesNC: DC=DomainDnsZones,DC=ABC,DC=COM
Reason: StaleServersTopology
Replica link has been added.
ReplicatesNC: CN=Schema,CN=Configuration,DC=ABC,DC=COM
Reason: StaleServersTopology
Replica link has been added.
ReplicatesNC: DC=ForestDnsZones,DC=ABC,DC=COM
Reason: StaleServersTopology
Replica link has been added.
ReplicatesNC: CN=Configuration,DC=ABC,DC=COM
Reason: StaleServersTopology
Replica link has been added.
enabledConnection: whenChanged: 20140520094554.0Z
whenCreated: 20131005064554.0Z
Schedule:
day: 0123456789ab0123456789ab
Sun: 111111111111111111111111
Mon: 111111111111111111111111
Tue: 111111111111111111111111
Wed: 111111111111111111111111
Thu: 111111111111111111111111
Fri: 111111111111111111111111
Sat: 111111111111111111111111
1 connections found.
Partition Replication Schedule Loading:
00 01 02 03 04 05 06
07 08 09
10 11
0 1 2 3 0 1 2 3 0 1 2 3 0 1 2 3 0 1 2 3 0 1 2 3 0 1 2 3 0 1 2 3 0 1 2 3 0 1 2 3
0 1 2 3 0 1 2 3
Sun: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
Sun: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
Mon: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
Mon: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
Tue: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
Tue: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
Wed: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
Wed: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
Thu: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
Thu: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
Fri: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
Fri: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
Sat: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
Sat: 0500000005000000050000000500000005000000050000000500000005000000050
00000050000000500000005000000
Any suggestion, thanks.Hi Paul
Info from DC1:
Starting portqry.exe -n 192.168.1.2 -e 135 -p TCP ...
Querying target system called:
192.168.1.2
Attempting to resolve IP address to a name...
IP address resolved to dc2.abc.com
querying...
TCP port 135 (epmap service): LISTENING
Using ephemeral source port
Querying Endpoint Mapper Database...
Server's response:
UUID: d95afe70-a6d5-4259-822e-2c84da1ddb0d
ncacn_ip_tcp:192.168.1.2[49152]
UUID: b2507c30-b126-494a-92ac-ee32b6eeb039
ncalrpc:[OLE563182CEF478C3A14653D062D772]
UUID: b2507c30-b126-494a-92ac-ee32b6eeb039
ncalrpc:[LRPC-fd920cc2d92f99660e]
UUID: 76f226c3-ec14-4325-8a99-6a46348418af
ncalrpc:[WMsgKRpc013EEBBB3]
UUID: 76f226c3-ec14-4325-8a99-6a46348418af
ncalrpc:[WMsgKRpc094591E2]
UUID: 12e65dd8-887f-41ef-91bf-8d816c42c2e7 Secure Desktop LRPC interface
ncalrpc:[WMsgKRpc094591E2]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC-718e5b08ea729d2926]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC-718e5b08ea729d2926]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC-718e5b08ea729d2926]
UUID: f763c91c-2ab1-47fa-868f-7de7efd42194 VM Allow-List Provider RPC
ncalrpc:[OLEED37CE9CBAC28EC99D9933545A44]
UUID: f763c91c-2ab1-47fa-868f-7de7efd42194 VM Allow-List Provider RPC
ncalrpc:[RdvVmAllowListRpc]
UUID: 50abc2a4-574d-40b3-9d66-ee4fd5fba076
ncacn_ip_tcp:192.168.1.2[56001]
UUID: 367abb81-9844-35f1-ad32-98f038001003
ncacn_ip_tcp:192.168.1.2[55992]
UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncalrpc:[OLE8547DF8F5A8A2691524B9BE9E7E1]
UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncacn_ip_tcp:192.168.1.2[55982]
UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncalrpc:[OLE8547DF8F5A8A2691524B9BE9E7E1]
UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncacn_ip_tcp:192.168.1.2[55982]
UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncalrpc:[OLE4F01D4F32CF4FF20E30658C178A4]
UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncacn_ip_tcp:192.168.1.2[55965]
UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncalrpc:[LRPC-6465a69e9cd02a03ea]
UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncalrpc:[OLE4F01D4F32CF4FF20E30658C178A4]
UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncacn_ip_tcp:192.168.1.2[55965]
UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncalrpc:[LRPC-6465a69e9cd02a03ea]
UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncalrpc:[OLE4F01D4F32CF4FF20E30658C178A4]
UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncacn_ip_tcp:192.168.1.2[55965]
UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncalrpc:[LRPC-6465a69e9cd02a03ea]
UUID: 0b6edbfa-4a24-4fc6-8a23-942b1eca65d1 Spooler function endpoint
ncalrpc:[spoolss]
UUID: ae33069b-a2a8-46ee-a235-ddfd339be281 Spooler base remote object endpoint
ncalrpc:[spoolss]
UUID: 4a452661-8290-4b36-8fbe-7f4093a94978 Spooler function endpoint
ncalrpc:[spoolss]
UUID: f2c9b409-c1c9-4100-8639-d8ab1486694a Witness Client Upcall Server
ncalrpc:[DNSResolver]
UUID: f2c9b409-c1c9-4100-8639-d8ab1486694a Witness Client Upcall Server
ncalrpc:[LRPC-e04435e83bae933e86]
UUID: eb081a0d-10ee-478a-a1dd-50995283e7a8 Witness Client Test Interface
ncalrpc:[DNSResolver]
UUID: eb081a0d-10ee-478a-a1dd-50995283e7a8 Witness Client Test Interface
ncalrpc:[LRPC-e04435e83bae933e86]
UUID: 7f1343fe-50a9-4927-a778-0c5859517bac DfsDs service
ncalrpc:[DNSResolver]
UUID: 7f1343fe-50a9-4927-a778-0c5859517bac DfsDs service
ncalrpc:[LRPC-e04435e83bae933e86]
UUID: 7f1343fe-50a9-4927-a778-0c5859517bac DfsDs service
ncacn_np:\\\\DC2[\\PIPE\\wkssvc]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncacn_np:\\\\DC2[\\pipe\\lsass]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[audit]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[securityevent]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[LSARPC_ENDPOINT]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[lsacap]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[LSA_EAS_ENDPOINT]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[lsapolicylookup]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[lsasspirpc]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[protected_storage]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[SidKey Local End Point]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[samss lpc]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[OLED28048DC13D14B9EE9E902CF0222]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_np:\\\\DC2[\\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:[LSARPC_ENDPOINT]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[lsacap]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[LSA_EAS_ENDPOINT]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[lsapolicylookup]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[lsasspirpc]
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
ncalrpc:[SidKey Local End Point]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[samss lpc]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[OLED28048DC13D14B9EE9E902CF0222]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_ip_tcp:192.168.1.2[49156]
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:192.168.1.2[49157]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_np:\\\\DC2[\\pipe\\b8d41bc7af954a5b]
UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_np:\\\\DC2[\\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:[LSARPC_ENDPOINT]
UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[lsacap]
UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[LSA_EAS_ENDPOINT]
UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[lsapolicylookup]
UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[lsasspirpc]
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
ncalrpc:[SidKey Local End Point]
UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[samss lpc]
UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[OLED28048DC13D14B9EE9E902CF0222]
UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_ip_tcp:192.168.1.2[49156]
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:192.168.1.2[49157]
UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_np:\\\\DC2[\\pipe\\b8d41bc7af954a5b]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_np:\\\\DC2[\\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:[LSARPC_ENDPOINT]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[lsacap]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[LSA_EAS_ENDPOINT]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[lsapolicylookup]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[lsasspirpc]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[protected_storage]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[SidKey Local End Point]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[samss lpc]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[OLED28048DC13D14B9EE9E902CF0222]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_ip_tcp:192.168.1.2[49156]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[NTDS_LPC]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_http:192.168.1.2[49157]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_np:\\\\DC2[\\pipe\\b8d41bc7af954a5b]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_np:\\\\DC2[\\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:[LSARPC_ENDPOINT]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[lsacap]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[LSA_EAS_ENDPOINT]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[lsapolicylookup]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[lsasspirpc]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[protected_storage]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[SidKey Local End Point]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[samss lpc]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[OLED28048DC13D14B9EE9E902CF0222]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_ip_tcp:192.168.1.2[49156]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[NTDS_LPC]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_http:192.168.1.2[49157]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_np:\\\\DC2[\\pipe\\b8d41bc7af954a5b]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_ip_tcp:192.168.1.2[49158]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_np:\\\\DC2[\\pipe\\lsass]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[audit]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[securityevent]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[LSARPC_ENDPOINT]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[lsacap]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[LSA_EAS_ENDPOINT]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[lsapolicylookup]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[lsasspirpc]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[protected_storage]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[SidKey Local End Point]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[samss lpc]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[OLED28048DC13D14B9EE9E902CF0222]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_ip_tcp:192.168.1.2[49156]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[NTDS_LPC]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_http:192.168.1.2[49157]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_np:\\\\DC2[\\pipe\\b8d41bc7af954a5b]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_ip_tcp:192.168.1.2[49158]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[NETLOGON_LRPC]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_np:\\\\DC2[\\pipe\\lsass]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[audit]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[securityevent]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[LSARPC_ENDPOINT]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[lsacap]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[LSA_EAS_ENDPOINT]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[lsapolicylookup]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[lsasspirpc]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[protected_storage]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[SidKey Local End Point]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[samss lpc]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[OLED28048DC13D14B9EE9E902CF0222]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_ip_tcp:192.168.1.2[49156]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[NTDS_LPC]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_http:192.168.1.2[49157]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_np:\\\\DC2[\\pipe\\b8d41bc7af954a5b]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_ip_tcp:192.168.1.2[49158]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncalrpc:[NETLOGON_LRPC]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_np:\\\\DC2[\\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:[LSARPC_ENDPOINT]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[lsacap]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[LSA_EAS_ENDPOINT]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[lsapolicylookup]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[lsasspirpc]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[protected_storage]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[SidKey Local End Point]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[samss lpc]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[OLED28048DC13D14B9EE9E902CF0222]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_ip_tcp:192.168.1.2[49156]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[NTDS_LPC]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_http:192.168.1.2[49157]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_np:\\\\DC2[\\pipe\\b8d41bc7af954a5b]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_ip_tcp:192.168.1.2[49158]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[NETLOGON_LRPC]
UUID: dd490425-5325-4565-b774-7e27d6c09c24 Base Firewall Engine API
ncalrpc:[LRPC-4270f9981254faa91d]
UUID: 7f9d11bf-7fb9-436b-a812-b2d50c5d4c03 Fw APIs
ncalrpc:[LRPC-4270f9981254faa91d]
UUID: 7f9d11bf-7fb9-436b-a812-b2d50c5d4c03 Fw APIs
ncalrpc:[LRPC-d35d2bd87814618631]
UUID: f47433c3-3e9d-4157-aad4-83aa1f5c2d4c Fw APIs
ncalrpc:[LRPC-4270f9981254faa91d]
UUID: f47433c3-3e9d-4157-aad4-83aa1f5c2d4c Fw APIs
ncalrpc:[LRPC-d35d2bd87814618631]
UUID: 2fb92682-6599-42dc-ae13-bd2ca89bd11c Fw APIs
ncalrpc:[LRPC-4270f9981254faa91d]
UUID: 2fb92682-6599-42dc-ae13-bd2ca89bd11c Fw APIs
ncalrpc:[LRPC-d35d2bd87814618631]
UUID: 7ea70bcf-48af-4f6a-8968-6a440754d5fa NSI server endpoint
ncalrpc:[OLEA9AB9FCCA745604305A49AF0A69C]
UUID: 7ea70bcf-48af-4f6a-8968-6a440754d5fa NSI server endpoint
ncalrpc:[LRPC-a135c3326e5cbba3aa]
UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
ncalrpc:[OLEA9AB9FCCA745604305A49AF0A69C]
UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
ncalrpc:[LRPC-a135c3326e5cbba3aa]
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:\\\\DC2[\\PIPE\\W32TIME_ALT]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[IUserProfile2]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[IUserProfile2]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[senssvc]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[IUserProfile2]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[senssvc]
UUID: 2eb08e3e-639f-4fba-97b1-14f878961076 Group Policy RPC Interface
ncalrpc:[LRPC-182e6d1994fef1b6b4]
UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncalrpc:[IUserProfile2]
UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]
UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncalrpc:[senssvc]
UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncalrpc:[IUserProfile2]
UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]
UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncalrpc:[senssvc]
UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncacn_np:\\\\DC2[\\PIPE\\atsvc]
UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncalrpc:[IUserProfile2]
UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]
UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncalrpc:[senssvc]
UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncacn_np:\\\\DC2[\\PIPE\\atsvc]
UUID: 86d35949-83c9-4044-b424-db363231fd0c
ncalrpc:[IUserProfile2]
UUID: 86d35949-83c9-4044-b424-db363231fd0c
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]
UUID: 86d35949-83c9-4044-b424-db363231fd0c
ncalrpc:[senssvc]
UUID: 86d35949-83c9-4044-b424-db363231fd0c
ncacn_np:\\\\DC2[\\PIPE\\atsvc]
UUID: 86d35949-83c9-4044-b424-db363231fd0c
ncacn_ip_tcp:192.168.1.2[49154]
UUID: 3a9ef155-691d-4449-8d05-09ad57031823
ncalrpc:[IUserProfile2]
UUID: 3a9ef155-691d-4449-8d05-09ad57031823
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]
UUID: 3a9ef155-691d-4449-8d05-09ad57031823
ncalrpc:[senssvc]
UUID: 3a9ef155-691d-4449-8d05-09ad57031823
ncacn_np:\\\\DC2[\\PIPE\\atsvc]
UUID: 3a9ef155-691d-4449-8d05-09ad57031823
ncacn_ip_tcp:192.168.1.2[49154]
UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service
ncalrpc:[IUserProfile2]
UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]
UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service
ncalrpc:[senssvc]
UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service
ncacn_np:\\\\DC2[\\PIPE\\atsvc]
UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service
ncacn_ip_tcp:192.168.1.2[49154]
UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service
ncalrpc:[IUserProfile2]
UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]
UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service
ncalrpc:[senssvc]
UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service
ncacn_np:\\\\DC2[\\PIPE\\atsvc]
UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service
ncacn_ip_tcp:192.168.1.2[49154]
UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint
ncalrpc:[IUserProfile2]
UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]
UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint
ncalrpc:[senssvc]
UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint
ncacn_np:\\\\DC2[\\PIPE\\atsvc]
UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint
ncacn_ip_tcp:192.168.1.2[49154]
UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint
ncacn_np:\\\\DC2[\\PIPE\\srvsvc]
UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint
ncalrpc:[IUserProfile2]
UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]
UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint
ncalrpc:[senssvc]
UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint
ncacn_np:\\\\DC2[\\PIPE\\atsvc]
UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint
ncacn_ip_tcp:192.168.1.2[49154]
UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint
ncacn_np:\\\\DC2[\\PIPE\\srvsvc]
UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint
ncalrpc:[IUserProfile2]
UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]
UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint
ncalrpc:[senssvc]
UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint
ncacn_np:\\\\DC2[\\PIPE\\atsvc]
UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint
ncacn_ip_tcp:192.168.1.2[49154]
UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint
ncacn_np:\\\\DC2[\\PIPE\\srvsvc]
UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs
ncalrpc:[IUserProfile2]
UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]
UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs
ncalrpc:[senssvc]
UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs
ncacn_np:\\\\DC2[\\PIPE\\atsvc]
UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs
ncacn_ip_tcp:192.168.1.2[49154]
UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs
ncacn_np:\\\\DC2[\\PIPE\\srvsvc]
UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncalrpc:[IUserProfile2]
UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]
UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncalrpc:[senssvc]
UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncacn_np:\\\\DC2[\\PIPE\\atsvc]
UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncacn_ip_tcp:192.168.1.2[49154]
UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncacn_np:\\\\DC2[\\PIPE\\srvsvc]
UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncalrpc:[LRPC-d52bb987e6751941da]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[IUserProfile2]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[OLEF68E3C474DF50EBF13CB4B050548]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[senssvc]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncacn_np:\\\\DC2[\\PIPE\\atsvc]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncacn_ip_tcp:192.168.1.2[49154]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncacn_np:\\\\DC2[\\PIPE\\srvsvc]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[LRPC-d52bb987e6751941da]
UUID: f6beaff7-1e19-4fbb-9f8f-b89e2018337c Event log TCPIP
ncalrpc:[eventlog]
UUID: f6beaff7-1e19-4fbb-9f8f-b89e2018337c Event log TCPIP
ncacn_np:\\\\DC2[\\pipe\\eventlog]
UUID: f6beaff7-1e19-4fbb-9f8f-b89e2018337c Event log TCPIP
ncacn_ip_tcp:192.168.1.2[49153]
UUID: 30adc50c-5cbc-46ce-9a0e-91914789e23c NRP server endpoint
ncalrpc:[eventlog]
UUID: 30adc50c-5cbc-46ce-9a0e-91914789e23c NRP server endpoint
ncacn_np:\\\\DC2[\\pipe\\eventlog]
UUID: 30adc50c-5cbc-46ce-9a0e-91914789e23c NRP server endpoint
ncacn_ip_tcp:192.168.1.2[49153]
UUID: 30adc50c-5cbc-46ce-9a0e-91914789e23c NRP server endpoint
ncalrpc:[LRPC-78d564bf393b9716a5]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncalrpc:[eventlog]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncacn_np:\\\\DC2[\\pipe\\eventlog]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncacn_ip_tcp:192.168.1.2[49153]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncalrpc:[LRPC-78d564bf393b9716a5]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncalrpc:[dhcpcsvc]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint
ncalrpc:[eventlog]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint
ncacn_np:\\\\DC2[\\pipe\\eventlog]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint
ncacn_ip_tcp:192.168.1.2[49153]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint
ncalrpc:[LRPC-78d564bf393b9716a5]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint
ncalrpc:[dhcpcsvc]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint
ncalrpc:[dhcpcsvc6]
UUID: 4bec6bb8-b5c2-4b6f-b2c1-5da5cf92d0d9
ncalrpc:[umpo]
UUID: 4bec6bb8-b5c2-4b6f-b2c1-5da5cf92d0d9
ncalrpc:[actkernel]
UUID: 085b0334-e454-4d91-9b8c-4134f9e793f3
ncalrpc:[umpo]
UUID: 085b0334-e454-4d91-9b8c-4134f9e793f3
ncalrpc:[actkernel]
UUID: 8782d3b9-ebbd-4644-a3d8-e8725381919b
ncalrpc:[umpo]
UUID: 8782d3b9-ebbd-4644-a3d8-e8725381919b
ncalrpc:[actkernel]
UUID: 3b338d89-6cfa-44b8-847e-531531bc9992
ncalrpc:[umpo]
UUID: 3b338d89-6cfa-44b8-847e-531531bc9992
ncalrpc:[actkernel]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[umpo]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[actkernel]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncalrpc:[LRPC-5e4b119e2215d21906]
UUID: 2d98a740-581d-41b9-aa0d-a88b9d5ce938
ncalrpc:[umpo]
UUID: 2d98a740-581d-41b9-aa0d-a88b9d5ce938
ncalrpc:[actkernel]
UUID: 2d98a740-581d-41b9-aa0d-a88b9d5ce938
ncalrpc:[LRPC-5e4b119e2215d21906]
UUID: 2d98a740-581d-41b9-aa0d-a88b9d5ce938
ncalrpc:[LSMApi]
UUID: 2d98a740-581d-41b9-aa0d-a88b9d5ce938
ncacn_np:\\\\DC2[\\pipe\\LSM_API_service]
UUID: 8bfc3be1-6def-4e2d-af74-7c47cd0ade4a
ncalrpc:[umpo]
UUID: 8bfc3be1-6def-4e2d-af74-7c47cd0ade4a
ncalrpc:[actkernel]
UUID: 8bfc3be1-6def-4e2d-af74-7c47cd0ade4a
ncalrpc:[LRPC-5e4b119e2215d21906]
UUID: 8bfc3be1-6def-4e2d-af74-7c47cd0ade4a
ncalrpc:[LSMApi]
UUID: 8bfc3be1-6def-4e2d-af74-7c47cd0ade4a
ncacn_np:\\\\DC2[\\pipe\\LSM_API_service]
UUID: 1b37ca91-76b1-4f5e-a3c7-2abfc61f2bb0
ncalrpc:[umpo]
UUID: 1b37ca91-76b1-4f5e-a3c7-2abfc61f2bb0
ncalrpc:[actkernel]
UUID: 1b37ca91-76b1-4f5e-a3c7-2abfc61f2bb0
ncalrpc:[LRPC-5e4b119e2215d21906]
UUID: 1b37ca91-76b1-4f5e-a3c7-2abfc61f2bb0
ncalrpc:[LSMApi]
UUID: 1b37ca91-76b1-4f5e-a3c7-2abfc61f2bb0
ncacn_np:\\\\DC2[\\pipe\\LSM_API_service]
UUID: c605f9fb-f0a3-4e2a-a073-73560f8d9e3e
ncalrpc:[umpo]
UUID: c605f9fb-f0a3-4e2a-a073-73560f8d9e3e
ncalrpc:[actkernel]
UUID: c605f9fb-f0a3-4e2a-a073-73560f8d9e3e
ncalrpc:[LRPC-5e4b119e2215d21906]
UUID: c605f9fb-f0a3-4e2a-a073-73560f8d9e3e
ncalrpc:[LSMApi]
UUID: c605f9fb-f0a3-4e2a-a073-73560f8d9e3e
ncacn_np:\\\\DC2[\\pipe\\LSM_API_service]
UUID: 0d3e2735-cea0-4ecc-a9e2-41a2d81aed4e
ncalrpc:[umpo]
UUID: 0d3e2735-cea0-4ecc-a9e2-41a2d81aed4e
ncalrpc:[actkernel]
UUID: 0d3e2735-cea0-4ecc-a9e2-41a2d81aed4e
ncalrpc:[LRPC-5e4b119e2215d21906]
UUID: 0d3e2735-cea0-4ecc-a9e2-41a2d81aed4e
ncalrpc:[LSMApi]
UUID: 0d3e2735-cea0-4ecc-a9e2-41a2d81aed4e
ncacn_np:\\\\DC2[\\pipe\\LSM_API_service]
UUID: 76f226c3-ec14-4325-8a99-6a46348418af
ncalrpc:[WMsgKRpc04A550]
UUID: 76f226c3-ec14-4325-8a99-6a46348418af
ncacn_np:\\\\DC2[\\PIPE\\InitShutdown]
UUID: 76f226c3-ec14-4325-8a99-6a46348418af
ncalrpc:[WindowsShutdown]
UUID: d95afe70-a6d5-4259-822e-2c84da1ddb0d
ncalrpc:[WMsgKRpc04A550]
UUID: d95afe70-a6d5-4259-822e-2c84da1ddb0d
ncacn_np:\\\\DC2[\\PIPE\\InitShutdown]
UUID: d95afe70-a6d5-4259-822e-2c84da1ddb0d
ncalrpc:[WindowsShutdown]
Total endpoints found: 317
==== End of RPC Endpoint Mapper query response ====
portqry.exe -n 192.168.1.2 -e 135 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n 192.168.1.2 -e 389 -p BOTH ...
Querying target system called:
192.168.1.2
Attempting to resolve IP address to a name...
IP address resolved to DC2.ABC.COM
querying...
TCP port 389 (ldap service): FILTERED
UDP port 389 (unknown service): LISTENING or FILTERED
Using ephemeral source port
Sending LDAP query to UDP port 389...
LDAP query to port 389 failed
Server did not respond to LDAP query
portqry.exe -n 192.168.1.2 -e 389 -p BOTH exits with return code 0x00000001.
=============================================
Starting portqry.exe -n 192.168.1.2 -e 636 -p TCP ...
Querying target system called:
192.168.1.2
Attempting to resolve IP address to a name...
IP address resolved to DC2.ABC.COM
querying...
TCP port 636 (ldaps service): FILTERED
portqry.exe -n 192 -
USB device (Logitech QuickCam Messenger) stopped working (SOLVED)
Hey there,
I have a logitech quickcam messenger, which used to work perfectly 2 days ago. I updated my system yesterday and this morning, but I tried the cam again only now, and neither cheese nor webcamstudio work anymore (it never worked in skype since I moved from Mint to Arch a few weeks ago, but that was easily (and better) addressed by starting cheese and then using desktop sharing in Skype)
The webcam is recognized
sammy@Cosmic-Bandito ~$ lsusb
Bus 001 Device 007: ID 046d:08da Logitech, Inc. QuickCam Messanger
Bus 001 Device 006: ID 056a:00d4 Wacom Co., Ltd
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB [Hama]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 046d:c513 Logitech, Inc. MX3000 Cordless Desktop Receiver
Bus 002 Device 002: ID 046d:c51a Logitech, Inc. MX Revolution/G7 Cordless Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
/dev/video and /dev/video0 are created.
cheese only shows a black window and spits out :
sammy@Cosmic-Bandito ~/Videos/Webcam$ cheese
libv4l2: error turning on stream: Input/output error
webcamstudio hangs when I try to start the preview and its output is :
libv4l2: error turning on stream: Input/output error
USB Camera (046d:08da) Error: BaseSrc: [v4l2src0],5, Error starting streaming on device '/dev/video0'.
EDIT: that's the output of dmesg when I reconnect the webcam (after having disconnected it obviously) :
[ 2216.282753] hub 1-1:1.0: state 7 ports 4 chg 0000 evt 0010
[ 2216.283231] hub 1-1:1.0: port 4, status 0101, change 0001, 12 Mb/s
[ 2216.387861] hub 1-1:1.0: debounce: port 4: total 100ms stable 100ms status 0x101
[ 2216.450867] usb 1-1.4: new full speed USB device using ehci_hcd and address 11
[ 2216.462234] hub 1-1:1.0: port 4 not reset yet, waiting 10ms
[ 2216.537006] usb 1-1.4: ep0 maxpacket = 8
[ 2216.538992] usb 1-1.4: skipped 4 descriptors after interface
[ 2216.538994] usb 1-1.4: skipped 2 descriptors after interface
[ 2216.538996] usb 1-1.4: skipped 1 descriptor after endpoint
[ 2216.538998] usb 1-1.4: skipped 2 descriptors after interface
[ 2216.539000] usb 1-1.4: skipped 1 descriptor after endpoint
[ 2216.539006] usb 1-1.4: udev 11, busnum 1, minor = 10
[ 2216.539008] usb 1-1.4: New USB device found, idVendor=046d, idProduct=08da
[ 2216.539010] usb 1-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2216.539081] usb 1-1.4: usb_probe_device
[ 2216.539084] usb 1-1.4: configuration #1 chosen from 1 choice
[ 2216.539364] usb 1-1.4: adding 1-1.4:1.0 (config #1, interface 0)
[ 2216.539400] zc3xx 1-1.4:1.0: usb_probe_interface
[ 2216.539402] zc3xx 1-1.4:1.0: usb_probe_interface - got id
[ 2216.539404] gspca: probing 046d:08da
[ 2217.384009] zc3xx: probe 2wr ov vga 0x0000
[ 2217.407008] zc3xx: probe sensor -> 0011
[ 2217.407010] zc3xx: Find Sensor HV7131R(c)
[ 2217.407304] input: zc3xx as /devices/pci0000:00/0000:00:0b.1/usb1/1-1/1-1.4/input/input14
[ 2217.407372] gspca: video0 created
[ 2217.407374] gspca: found int in endpoint: 0x82, buffer_len=8, interval=10
[ 2217.407381] usb 1-1.4: link qh8-0601/f6f9e240 start 5 [1/2 us]
[ 2217.407401] usb 1-1.4: adding 1-1.4:1.1 (config #1, interface 1)
[ 2217.407438] zc3xx 1-1.4:1.1: usb_probe_interface
[ 2217.407441] zc3xx 1-1.4:1.1: usb_probe_interface - got id
[ 2217.407443] gspca: probing 046d:08da
[ 2217.407455] snd-usb-audio 1-1.4:1.1: usb_probe_interface
[ 2217.407458] snd-usb-audio 1-1.4:1.1: usb_probe_interface - got id
[ 2217.410813] usb 1-1.4: adding 1-1.4:1.2 (config #1, interface 2)
[ 2217.410855] drivers/usb/core/inode.c: creating file '011'
EDIT 2: Just tried the webcam on another computer, and it works there. so it's not the hardware
any ideas? I'm pretty desperate, as this is the only way for me to keep in touch with my kids at the moment
Last edited by SammyF (2010-05-28 20:44:15)SOLVED : really stupid problem, but well... I'll completement my post and leave it for anybody who might hit the same problem :
dmesg looked like this when after I started cheese :
[ 3815.848011] usb 1-1.4: unlink qh8-3008/ec236980 start 0 [1/2 us]
[ 3815.848995] gspca: found int in endpoint: 0x82, buffer_len=8, interval=10
[ 3815.849001] usb 1-1.4: link qh8-0601/f6848ec0 start 1 [1/2 us]
[ 3816.696230] zc3xx: probe 2wr ov vga 0x0000
[ 3816.917369] ehci_hcd 0000:00:0b.1: iso sched full f0049c00 (now 652 max 2700)
[ 3816.917377] gspca: bandwidth not wide enough - trying again
[ 3816.938010] gspca: no transfer endpoint found
The (not so obvious) solution was to connect the webcam directly to the computer and not through a USB hub. I have no idea why it used to work and suddenly stopped, but it works again now.
sorry to take up your time, in case I did.
Last edited by SammyF (2010-05-28 20:44:56) -
Hello together!
Since qc-usb was replaced with gspca I have troubles with my Webcam. It's a Quickcam Web (more precisely: LEGO cam) 046d:0850 and it used to work with qc-usb. It's also listed as a supported one in the gspca files.
It is correctly recognized when plugged in:
usb 2-1: new full speed USB device using ohci_hcd and address 3
usb 2-1: configuration #1 chosen from 1 choice
Linux video capture interface: v2.00
gspca: main v2.7.0 registered
STV06xx: Probing for a stv06xx device
gspca: probing 046d:0850
STV06xx: Configuring camera
STV06xx: vv6410 sensor detected
STV06xx: Initializing camera
gspca: probe ok
STV06xx: Probing for a stv06xx device
gspca: probing 046d:0850
STV06xx: Probing for a stv06xx device
gspca: probing 046d:0850
usbcore: registered new interface driver STV06xx
STV06xx: registered
usbcore: registered new interface driver snd-usb-audio
When I try to cat from the video device I get this:
cat: /dev/video: Input/output error
dmesg now reports:
gspca: usb_submit_urb alt 1 err -28
gspca: no transfer endpoint found
Other applications (mplayer, amsn, etc.) behave similar.
My first tests on a 2.6.29 kernel months ago resulted in a Kernel Panic, with 2.6.32 it's not working "only"...
Regards,
SvenThank you very much. Your link (and another google search which taught me about guvcview) helped me.
After I unplugged my USB keyboard and mouse (two different devices) from my computer (no hub!) the cam started to work (note: I'm using a laptop). I'm very surprised by this behavior.
Now I need to find a solution for this bandwidth problem, because without full keyboard and mouse chatting is not very comfortable (and that's the sole purpose of this cam)
EDIT: Well... unplugging one of the two devices (keyboard, mouse) seems to be sufficient... perhaps I should learn to live without a real mouse (that's easier than without a real keyboard)
Regards,
Sven
Last edited by PascalDragon (2009-12-31 17:18:02) -
BPM Simple Sample Application Error!!!
hi,
i have some problems with the bpm simple sample applications on our local sap nw ce system (7.1 ehp1 sp0)?
on the esworkplace i have download the *.sca file and have import this file into my nwds.
i following the simple sample documentation an define and configure the ERP and ERP_META Destinations on the nwds and our local sap nw ce system.
also i do the future steps which was described (service registry, proxy settings, ...).
on page 16 of the simple sample documetation is defined which Sofware Component has dependencies to other SC´s.
the SC "BPEM_BUILDT" depends on the SC "ESMP_BUILDT" and "COMP_BUILDT", the SC "COMP_BUILT" doesnt exist on my nwds (7.1 ehp1 sp0).
has everybody any idea why the SC "COMP_BUILT" not exist on my nwds???
still this absent SC i can deploy the bpm simple sample successful to our sap nw ce system.
now i do the post deployment steps for the bpm samples.
after this i call the simple sample application on my sap nw ce portal and can execute the "Initiate Equipment Phase In Process".
now i can see a new entry on my uwl, i open the uwl task.
at step 1, 2, 3 i change no data an click next, after step 3 (create equipment) i get the following error:
com.sap.esi.esp.service.server.query.discovery.ExtendedServiceException: no endpoints found for interface <br>
IndividualMaterialERPCreateRequestConfirmation_In_V1 <br>
<br>
detailed error message: <br>
com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WS metadata <br>
destination 'ERP_META' and WS interface 'IndividualMaterialERPCreateRequestConfirmation_In_V1'. One possible reason is that
Caused by: com.sap.esi.esp.service.server.query.discovery.ExtendedServiceException: no endpoints found for interface
IndividualMaterialERPCreateRequestConfirmation_In_V1
at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImplSoa.getEndpointConfigurations(DestinationsHelperImplSoa.java:1184)
at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImplSoa.getWSDLUrl(DestinationsHelperImplSoa.java:847)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.getWSDLUrl(GenericServiceFactory.java:547)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:377)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:230)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:195)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:529)
... 82 more
after this error i test the endpoint manually. i call the service registry (sr.esworkplace.sap.com) an search the service:
IndividualMaterialERPCreateRequestConfirmation_In_V1
now i test the endpoint with the following data:
MaintenancePlanningPlantID: 0001
WorkCentreID: TECH.SER
CategoryCode: M
the return is the following:
TypeID:005(PLM_SE_EAM_SC)
SeverityCode:1
Note:Individual Material 000000000010006703 is created
i think the return from the service was successful.
i hope somebody can help me!!!
thanks,
FabianHi Arafat,
the destinations for the services are already configured::
at destination template management > destination templates the following is defined:
- Tab: General
Destination Name: ERP
Destination Type: Service Registry
System: ABAP
System Name: HU2
Hostname: iwdf2379
Installation Nr.: 0120003411
Client: 800
- Tab: Security
Authentication: HTTP Authentication, User ID/Password (Basic)
User ID: <es workplace user (suser)>
pw: ******
and
- Tab: General
Destination Name: ERP_META
Destination Type: Service Registry
System: ABAP
System Name: HU2
Hostname: iwdf2379
Installation Nr.: 0120003411
Client: 800
- Tab: Security
Authentication: HTTP Authentication, User ID/Password (Basic)
User ID: <es workplace user (suser)>
pw: ******
also i have configured the same destination on my nwds.
i think this is correct?
futher ideas, why this doesnt work?
thanks,
fabian -
Problem with FILE TO EMAIL Scenario
Hello ALL,
I am working on FILE--->XI--> Email scenario, done with designing and configuration part.I try to post a sample test file, File adapter is not picking up the file from the directory and throwing exception in Adpater Framework Window. I see following exception in Adapter monitoring window.. I am not able to figure it out where it went wrong..Any suggestions are gretly helpful.
Last message processing started 14:38:34 2005-08-08, Error: Module exception com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: Failed to call the endpoint found
last retry interval started 14:38:34 2005-08-08
length 30,000 secs
Thanks ,
Prakash.Hi,
There is feature to test the Configuration settings in Integration Directory.
Tools--> Test Configuration.
Here you need to specifry the Sender and Receiver details.
In Payload, --> copy it from RWB or SXMB_MONI with sender payload,
execute the scenario( Downward arrow Icon).
It will give you all details and log if there is anything missing in the scenario.
Thanks
Swarup -
PO7.31 and BPM: Using Operation Mapping within BPM
Hello everyone!
I am facing an issue while trying the import/execute an Operation Mapping within a BPM. Have a PO 7.31SP07 installation (NWDS also on 7.31 SP07), and the process already have some working interface calls to PI, however still having issue while trying to execute the Operation Mapping:
1. After deploying the process, going to NWA -> SOA tab -> Application and Scenario Communication -> Application Communication -> select the process -> check the "localhost"/WS group for "Local System". The "Processing State" shows the error below:
Configuration for service group [localhost] failed. Error details:
[No endpoints found. Check if the service is configured and if its
endpoints are available in the . Service:
[{http://fusionconsultoria.com.br/sales_order_create}fusionconsultoria_salesord_om_SalesOrderSplit_ServicePortType]
Assigned Provider: [Local System]
Service Group: [localhost]
Service Group application: [fusionconsultoria/salesord]
Service Reference application: [fusionconsultoria/salesord]
2. During runtime, when trying to execute the OM automated step, on log viewer:
Error during SCA Processing
[EXCEPTION]
com.sap.engine.interfaces.sca.config.exception.ESBConfigurationException:
Could not process message for operation om_SalesOrderSplit_Service in
web service plugin module.
at com.sap.engine.services.sca.plugins.ws.WebServiceImplementationInstance.accept(WebServiceImplementationInstance.java:223)
at com.sap.engine.services.sca.das.SCADASImpl.invokeReference(SCADASImpl.java:314)
Caused by: com.sap.esi.esp.lib.mm.config.exceptions.ObjectNotExistsException:
Configuration not found for application:
fusionconsultoria/salesord,serviceRefId:{http://www.sap.com}salesord_fusionconsultoria~salesord~BPMcomponent_29768b4e-f59a-4ba3-a2ff-dee594b01ecf_WS.
Please check the configuration details from the NWA. You may have not
assigned the Service Group to a Provider System, or the generation of
the configuration has failed.
3. Carried out the steps from the referenced links below. They are quite similar to each other, however still facing the issue:
Reuse PI Operation Mapping as a service in SAP NetWeaver BPM
Using Operation Mappings (PI) in a BPM Process - Process Orchestration - SAP Library
Using NetWeaver PI’s Mapping in NetWeaver BPM
- Marked as "local provider" and WS;
4. Tried deleting, creating the automated step aswell reimporting the Operation Mapping.
5. Already reviewed the input/output mapping of the automated activity;
6. On ESR, the mapping works correctly.
7. Tried changing the outbound and inbound Service interfaces for the OM from stateless to stateless XI3.0, as well from synchronous to asynchronous.
At this moment I've completely ran out of ideas. Appreciate if anyone could give any insights, since I am running out of time with this project!
Thanks in advance to all and
Best regards,
Lucas SantosHi Lucus
I'm facing the same type of problem.
Why would re-creating the BPM fix this issue ?. I fear I would spend all this effort for nothing.
What does your operation mapping wsdl:service > soap:address look like ? What does your NWA BPM application Communication Configuration look like now - before you had that red light - like I have now.
The WSDL that is generated from the imported Operation Mapping : what end point is expected here. My wsdl:service > soap:address location has a port of 50500 - which does not even exist!. How can it work Does this get automatically deployed onto the Service Registry?.
I have built and deployed this but I get a run time error when it executes the operation mapping. A technical error during invocation: Could not invoke service reference name.
I have seen in the deployed BPM's Application Configuration against the Consumed Service Groups an error against the associated service group
Configuration for service
group [SG_localhost] failed. Error details: [No endpoints found. Check if the service is configured and if its endpoints are available in the . Service
It almost seems that it wants me to publish the end point on the service registry - no idea how....but I none of the blogs and post indicate that I need to fiddle with this at all.
I have this question in SDN too if you care to take a look. -
Hi,
Every now and again the sound disappears from my laptop.
Sometimes it's all the sounds / beeps, other times I can hear the beeps when I press the buttons at the top of the keyboard (Dolby, Media Center etc).
I've downloaded the sound driver for the machine (realtek hd audio), sometimes it fixes it, but most times it doesn't.
When all the sounds disappear and I click the 'Dolby' button at the top of the keyboard I receive the following error "No audio end points".
I've looked in device manager when there is no sound, but nothing irregular appears.
Any ideas ?
Thanks
JamesI have the same problem with my X305-Q705.
I had some problems with sound skipping, and decided to go to the Toshiba website and install sound drivers.
After I installed Microsoft HD Audio drivers from the Toshiba website, Dolby no longer works.
I cannot start it from Start>Programs>Dolby or from the Hotbar touchbuttons on the keyboard.
Also, I realized the built in Webcam is still installed, but the MIC is not registering as a Recording device anymore.
The error given is "No valid audio endpoints found" with the Dolby icon on the taskbar.
Hopefully someone can find a fix soon. :)
Maybe you are looking for
-
Need a list of all services, processes and servers
Hi experts, i'm totally new to this but i need a list of all services, processes and servers. Is there a easy way to get them? I try to create a tool where you are able to virtually shutdown servers and then you can see what happends to the services
-
Hi, I am looking for a User Exit that will enable me to update the fields of the conditions table KONV, while entering materials during the process of a Sales Order in VA01 or VA02. Thanks, Amit Shur
-
Change public template BBPSC06 (Error in system; shopping cart cannot be pr
Hi, I am in SRM_SERVER 5 (SRM 4) SP 14. I have dome my standard templates without problems, but when I try to change I get this error when I go to transaction BBPSC06 (with same user). Error in system; shopping cart cannot be processed further does a
-
Can I make a 1 pixel burn tool?
If I use a pencil, I can draw one pixel at a time. However, if I switch to the Dodge or Burn tools, even selecting 1 pixel width, it still is soft. One click effects 8 pixels. How can I truly harden the tool to only darken 1 pixel at a time? Thanks
-
I need to download music from someone else pc that I downloaded from internet
I need to upload some audio files i downloaded in some one elses PC and the PC doesn't recognises my iphone even if it has itunes installed and I have connected to my account how can i donload those files into my iphone?