INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Compare two client attempts and identify where DNS, TCP or authentication first fails.

Prerequisite

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.

Stages of a database connection
Stages of a database connection1: Clients — Compare DNS — DNS lookup. 2: DNS lookup — Check both directions — Network path. 3: Network path — Verify the business read — Database123ClientsDNS lookupNetwork pathDatabaseStages of a database connection1: Clients — Compare DNS — DNS lookup. 2: DNS lookup — Check both directions — Network path. 3: Network path — Verify the business read — Database123ClientsDNS lookupNetwork pathDatabase
  1. Clients → DNS lookupCompare DNS
  2. DNS lookup → Network pathCheck both directions
  3. 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

Fictional authorized tests from two VPCs with the same endpoint and database.
AttemptObservationNext check
A DNSExpected IPCheck TCP
A TCPUnreachableSubnet route table, SG and NACL
B TCP and TLSSuccessfulCheck database authentication
B databaseNo access to target DBCheck 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.

A gets the expected address but cannot connect over TCP. What next?
Read the answer and reason

Answer: Check A’s route and network controls · The DNS step matched the expectation.

B successfully negotiates TLS but lacks database access. What next?
Read the answer and reason

Answer: Check the grant on the target database · Check the database identity and effective permission.

Does reachable in the model mean the business operation passes?
Read the answer and reason

Answer: Verify the connection and a database read · It describes reachability under a network model.

Check, then explain in your own words

  1. Use the same name and time window.
  2. Compare DNS, TCP, TLS and database evidence.
  3. 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.