![globalprotect connection failed no network connectivity globalprotect connection failed no network connectivity](https://i1.wp.com/www.gns3network.com/wp-content/uploads/2019/11/GlobalProtect-VPN-Configuration-1.png)
Use the error code and the error message on the DMS console. For native database errors related to the source or target database, refer to the resolution from the specific database documentation. Note: If any of these fields are specified with AWS Secrets Manager, then see Using secrets to access AWS Database Migration Service endpoints. Note: Don't specify a Database name for MySQL source or target. Set the ServerName to the DNS or IP of the on-premise database, or RDS endpoint.To resolve native database errors, confirm that the following endpoint configurations are set correctly: Run the following commands on the new EC2 instance to troubleshoot network connectivity: Confirm your Amazon EC2 instance has the same network configurations as the AWS DMS replication instance with the connectivity issues. To troubleshoot, create a new Amazon Elastic Compute Cloud (Amazon EC2) instance in the same VPC of the AWS DMS replication instance. If you still experience connectivity issues, then more troubleshooting might be needed. For information on using an on-premises name server to resolve endpoints using the Amazon Route 53 Resolver, see Using your own on-premises name server. If you require DNS resolution, then use the Amazon Route 53 Resolver. Confirm that the DNS configuration is set up correctly.Confirm that a firewall isn't blocking communication to the source or target database.Check with your network administrator to confirm the database allows incoming connections from the AWS DMS replication instance.If your target database is hosted on-premises, then confirm the following:
![globalprotect connection failed no network connectivity globalprotect connection failed no network connectivity](https://www.umass.edu/it/sites/default/files/2019/01/10/Screenshot_20181121-113603.png)
Run the describe-subnets command to determine the CIDR of each subnet:
![globalprotect connection failed no network connectivity globalprotect connection failed no network connectivity](https://www.consentfactory.com/wp-content/uploads/2020/12/globalProtect_skypeForBusiness.png)
In your replication instance, confirm your configuration includes the following: For more information, see Setting up a network for a replication instance. Depending on your use case and network infrastructure, connect your source or target database to a replication instance in public subnet or private subnet. Verify that connectivity can be established between the source or target database and the replication instance.