Solving The Problem Of Remote Access With Event ID 20070

PC running slow?

1. Download ASR Pro from the website

2. Install it on your computer

3. Run the scan to find any malware or virus that might be lurking in your system

Improve the speed of your computer today by downloading this software - it will fix your PC problems.

You may have come across an error message that says Event ID 20070 is remote access. There are several ways to solve this problem, and we will do it shortly.

This guide will help you troubleshoot issues that prevent Operations Manager agents from connecting to a management server in System Center 2012 Operations (OpsMgr Manager 2012) and later.

For more information about the agents selected by Operations Manager and how they interact with management companies, see agents and . communication between agents and management servers.

Initial product release: System Center 2012 Operations Manager
Original KB number: 10066

Check With The Health Department

Whenever you experience connectivity issues in Operations Manager, first verify that the Health Service is running without errors, both the client agent and the management server.To determine if a service has always been running, do the following:

1. Press Windows key + R.Die

2. In the Run box, type services.msc and press Enter carefully.

3. Locate the Microsoft Monitoring Agent service and double-click it toTo open its properties page.

   Note

   In System Center Operations 2012 Manager, each service is called System Center Management.

4. 

   In fact, make sure the startup type is set to Automatic.

5. Make sure the service is in the Started state. Otherwise, click Start.

Check Your Antivirus Exceptions

Once this health service is running, we need to make sure the Trojan horse exceptions are configured correctly. For the most up-to-date information on recommended antivirus exclusions for Operations Manager, see Antivirus exclusion recommendations, primarily related to Operations Manager).

Check For Network Problems

In Operations Manager, the agent computer must be fully prepared to successfully connect to a TCP 5723 connection on the management server. If that fails, you will probably end up with IDs 21016 and 21006 in the client agent.

In addition to TCP port 5723, the following ports must be enabled:

TCP and UDP 389 interface for LDAP

TCP and UDP port 88 for Kerberos and authentication cations

TCP UDP port 53 for Domain Name Service (DNS)

It’s also important to make sure that RPC communication within the network is working properly. RPC communication problems usually show up when they themselves send the agent directly from the management server. RPC communication issues sometimes cause client send to fail, as well as an error like the following:

The Operation Manager server failed to perform the specified surgical treatment on agent1.contoso.com.

Process: Agent installation
Account setup: contosoAgent_action
Error code: 800706BA
Error Description: The RPC server is probably unavailable

This error usually occurs when non-standard ephemeral ports are used, or when your ephemeral ports are blocked by a plan. For example, if non-standard long range RPC ports have been configured, the tiny network will show a successful connection to RPC port 135 and then test connectivity using a non-standard RPC port such as 15595. The following example is an example:< /p>

18748 TCP Agent TCP: Flags=CE….S., SrcPort=52457, DstPort=15595, PayloadLen=0, Seq=1704157139, Win=8192
eighteen750 ack=0, MS Agent TCP TCP:[SynReTransmit #18748] Flags=CE….S., SrcPort=52457, DstPort=15595, PayloadLen=0, Seq=1704157139, Ack=0,
18751 MS TCP Agent: [SynReTransmit tcp # 18748] Flags=……S., SrcPort=52457, PayloadLen=0, dstport=15595, Seq=1704157139, Ack=0, Win=8192

In this example, because the firewall is not configured to exclude ports for some non-standard ranges, some types of packets will be dropped and the corresponding error will not occur.

In Windows Vista and later, we may need high performance RPC ports 49152-65535. To check if this is your issue, run the following command to find out which high level RPC port range is configured:

netsh int ipv4 specifies a range of TCP dynamic ports

TCP dynamic port range
——————
Departure port: 49152
Number of ports. 16384

If you see a different source port, the problem may be that the firewall is not fully configured to allow traffic through all of these ports. You can change the configuration through the firewall or run the following command to install the supportDefault Premium Ports:

netsh int ipv4 pair dynamicport tcp start=49152 num=16383

You can also configure the dynamic range of RPC ports through the corresponding registry. For more information, see How to dynamically assign RPC ports to work with firewalls.

If everything seems to be set up correctly and my error persists, it may be due to one of the following conditions:

1. DCOM is restricted to a specific port. To check this, download dcomcnfg.exe, open My Computer > Properties > Default Protocols, make sure there are no user settings

2. wmi is configured to use the appropriate custom endpoint. To verify that customers have configured a static endpoint for WMI, troubleshoot dcomcnfg.exe, go to My Computer > DCOM Configuration > Windows Management and Instrumentation > Endpoint Properties > make sure the custom parameter is missing.

3. The agent machine is hosting the Exchange Server Client 2010 serveraccess. The Exchange Server 2010 Client Access service is changing the port range from 6005 to 65535. The range has been expanded to provide sufficient scaling for large scale deployments. Do not change these port values ​​without fully understanding the implications. More

For port and firewall requirements, see Firewalls. Minimum network connection requirements can also be found in speed only in the same article.

Check For Certificate Issues After Gateway Server

Operations Manager requires two-way authentication between client agents and management servers before changing information between them. To ensure the security of the authorization process, the process is encrypted. At this point, the agent and management server are in the same Active Directory domain, or in Active Directory domains that have a known relationship. They use the Kerberos v5 authentication mechanisms provided by Active Directory. If agents and management personnel are not on the same trust boundary, other mechanisms must be used.zma to meet the requirement of secure mutual authentication.

In Operations Manager, this is achieved through the use of X.509 certificates, each of which is issued to a computer. If agents control many computers, it can result in high administrative overhead for managing all of these certificates. In addition, if a firewall is installed between agents and management servers, multiple authorized endpoints must be well defined and managed according to firewall laws to allow communication between them.

Improve the speed of your computer today by downloading this software - it will fix your PC problems.

이벤트 ID 20070으로 원격 액세스의 일반적인 문제 해결
Resolviendo El Problema Del Acceso Lejano Con El ID De Evento 20070
Resolvendo O Problema De Acesso Remoto Com ID De Evento 20070
Lös Problemet Som Liknar Fjärråtkomst Med Händelse-ID 20070
Résoudre Le Problème De Tous Les Accès à Distance Avec L’ID D’événement 20070
Rozwiązywanie Obecnego Problemu Zdalnego Dostępu Za Pomocą Identyfikatora Zdarzenia 20070
Behebung Des Rückschlags Des Fernzugriffs Mit Ereignis-ID 20070
Решение проблемы удаленного доступа с идентификатором события 20070
Het Probleem Van Privétoegang Oplossen Met Gebeurtenis-ID 20070
Risolvere Il Problema Della Possibilità Di Accedere Da Remoto Con ID Evento 20070