Topic lessonTopic: SQL Server connectivity and AWS network operations
Troubleshooting SQL Server across VPCs: DNS, network paths and database authentication
The same database name can resolve or connect differently for different clients. Compare two client attempts and identify where DNS, TCP or authentication first fails.
Compare two client attempts and identify where DNS, TCP or authentication first fails.
This exercise uses fictional evidence and makes no changes in a live environment.
Run comparable checks from both clients
Reachability Analyzer models the network configuration. Actual packets, TLS and SQL Server permissions need separate evidence.
- Clients → DNS lookupCompare DNS
- DNS lookup → Network pathCheck both directions
- Network path → DatabaseVerify the business read
- Clients
- Reporter A and reporter B
- DNS lookup
- Same database endpoint name
- Network path
- Evidence of TCP connectivity
- Database
- Authentication and read result
Assign each client’s failure to the right stage
| Attempt | Observation | Next check |
|---|---|---|
| A DNS | Expected IP | Check TCP |
| A TCP | Unreachable | Subnet route table, SG and NACL |
| B TCP and TLS | Successful | Check database authentication |
| B database | No access to target DB | Check login and database authorization |
A reachability result from a configuration model does not prove a working connection or successful operation. Investigate the first failed stage for each client.
Document evidence for the failure point
Use the configuration model appropriately. Fix the source, target and port. Record what the analysis does not cover.
Check both network directions. Security groups and network ACLs have different roles. Check the subnet ACL for both inbound and outbound traffic.
Retest without loosening authentication. Use an authorized read against the intended database with the appropriate identity.
Check your decision
Choose an option to see the result and explanation.
Check, then explain in your own words
- Use the same name and time window.
- Compare DNS, TCP, TLS and database evidence.
- Record the first failed stage for each client.
Check your understanding: Can every client use the same remediation?
Match the action to the failing stage and evidence for each client.
One database can have different client paths and permissions.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
- How Reachability Analyzer worksChecked:
Scope and conditionsScope of modeled network reachability versus actual traffic.
Used in this lessonRun comparable checks from both clients Assign each client’s failure to the right stage Document evidence for the failure point
- Network ACL basicsChecked:
Scope and conditionsSubnet controls on inbound and outbound traffic.
Used in this lessonRun comparable checks from both clients Document evidence for the failure point