Ping, DNS and TCP establish different facts
A company share will not open. Is the failure in name resolution, routing or user authorization? CMD and PowerShell tools help when they answer those questions in order. Start with addressing and DNS, then routes and the service port. Successful ping establishes neither TCP access nor SMB permission. Preserve evidence before running release/renew or a stack reset on a server.
Example: an inaccessible server share
An application cannot reach files01.corp.example.com over SMB. Test DNS and TCP/445 from its subnet. Record resolved names/addresses to separate wrong DNS from firewall failure.
Use the name, address, interface and service port together to isolate a failure. The examples form a fictional branch: client 192.0.2.10/24, gateway 192.0.2.1, DNS 192.0.2.53 and file server files01.corp.example.com at 198.51.100.20. These documentation addresses are not public test services. Substitute authorized endpoints before running probes.
All output excerpts below are illustrative, abbreviated and not measurements from a tested production network. Probe results depend on routes, firewall policy, permissions and the selected host. Read each command card independently; do not paste the entire article as a script.
CMD and PowerShell on the affected host
Examples target Windows 11 and Windows Server 2022/2025 with x64 Windows PowerShell 5.1. Run CMD and PowerShell blocks in their respective shells.
These tools require no extra compute allocation. Run checks through the affected client’s actual path.
Status reads usually need standard privileges. Route/firewall changes require elevation. Replace sample domains/IPs with actual targets.
Windows modules and other PowerShell platforms
The example NetTCPIP/SMB cmdlets are Windows-specific. PowerShell on Linux does not provide the same modules. CMD diagnostics remain useful, while configuration-reset commands do not belong at the start of investigation.
The scope is serviced Windows 11 builds and Windows Server 2016, 2019, 2022 and 2025 with built-in console utilities; PowerShell examples use Windows PowerShell 5.1 and the Windows NetTCPIP module. Microsoft command applicability also lists Windows 10, but command availability is not lifecycle support: regular Windows 10 servicing ended on October 14, 2025; LTSC/ESU eligibility is separate. Check the exact edition/build lifecycle before deployment.
CMD examples are Windows executables, not PowerShell cmdlets. In PowerShell use ping.exe and hostname.exe when you need the executable rather than a possible alias. Test-NetConnection cannot run directly in CMD. net use mappings belong to the current logon/elevation context: diagnose from the affected user session. Use net help use and net help view on the target build because their online syntax pages are legacy references.
Investigation through share authorization
Follow the request in stages: the client resolves the name, selects an outgoing route and interface, and reaches the TCP listener. Only then does SMB evaluate identity and share/NTFS permissions. Each failed stage needs its own tool and action; do not extend the first stage's result to the whole path.
Protect diagnostic reports
Reports disclose hostnames and internal networks. Restrict access. Wi-Fi exports with key=clear expose secrets. Avoid passwords in net use/command lines and do not disable firewalls to investigate.
Address, route and port commands
ipconfig: establish the local addressing baseline
Display IPv4/IPv6, mask and gateway before testing a remote service. A helpdesk operator uses this to identify the active adapter and a wrong branch subnet.
CMD syntax: ipconfig
ipconfigIllustrative output excerpt; actual values vary.
Ethernet adapter Ethernet:
IPv4 Address . . . . . . . . . . : 192.0.2.10
Subnet Mask . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . : 192.0.2.1Compare mask and gateway with IPAM, not another adapter such as a VPN. Media disconnected points to link/adapter state. A 169.254.x.x address commonly means DHCP was unavailable; it is not a usable routed branch address by itself.
Read-only; normal user privileges suffice. Redact internal addressing before sharing. Inspect Get-NetIPConfiguration separately for structured PowerShell output.
ipconfig /all: DHCP and resolver evidence
Inspect adapter identity, DNS suffix, DHCP status, DNS servers and lease information. Use it when one office resolves a name differently from another.
CMD syntax: ipconfig /all
ipconfig /allIllustrative output excerpt; actual values vary.
Host Name . . . . . . . . . . . . : BRANCH-PC01
DHCP Enabled. . . . . . . . . . . : Yes
Physical Address. . . . . . . . . : 02-00-5E-10-00-10
DHCP Server . . . . . . . . . . . : 192.0.2.54
DNS Servers . . . . . . . . . . . : 192.0.2.53DHCP Server supplied the lease; DNS Servers answer name queries. They need not be the same host. DHCP Enabled: No means renewal is not the fix for that static interface. Unexpected suffix/resolver suggests DHCP scope, VPN or local configuration drift.
Read-only; no elevation normally needed. This report exposes MAC, domain and lease details. Preserve it before any reset.
ipconfig /flushdns: discard stale local DNS cache
Clear cached positive and negative resolver entries only after recording them. Use it following a confirmed DNS correction when this client still uses an old answer.
CMD syntax: ipconfig /displaydns; ipconfig /flushdns (run separately)
ipconfig /displaydns
ipconfig /flushdnsIllustrative output excerpt; actual values vary.
Successfully flushed the DNS Resolver Cache.A successful flushdns message confirms only that the local cache was cleared. Nslookup queries the DNS server directly and does not display the Windows resolver cache. Compare local cache, the configured DNS server's reply and application behavior before and after; a browser or application cache may still hold an older answer.
MODIFIES local cache; use an elevated CMD for the clear operation. If elevation is requested, reopen as Administrator instead of disabling DNS Client. No route or DNS-server setting is changed.
ipconfig /release: deliberately relinquish DHCP
Release the IPv4 DHCP lease on one explicitly named adapter for a controlled DHCP test. It is not a first-line connectivity diagnostic.
CMD syntax: ipconfig /release "adapter name"
ipconfig /release "Ethernet"Illustrative output excerpt; actual values vary.
Ethernet adapter Ethernet:
Default Gateway . . . . . . . . :Expect the DHCP-assigned IPv4/gateway to disappear; the exact remaining fields vary. Disconnected or statically configured adapters cannot release a usable DHCP lease. The error about an adapter not being in a permissible state requires checking link and DHCP status.
DISRUPTIVE; use elevated CMD with console access and a change window. It can terminate RDP/SSH, monitoring and application sessions. Omitting the adapter targets all eligible adapters. Do not run it on a static-address server.
ipconfig /renew: request DHCP configuration
Renew/request IPv4 DHCP configuration on the named adapter. Use after repairing DHCP reachability or during the approved lease test.
CMD syntax: ipconfig /renew "adapter name"
ipconfig /renew "Ethernet"
ipconfig /allIllustrative output excerpt; actual values vary.
IPv4 Address . . . . . . . . . . : 192.0.2.10
Default Gateway . . . . . . . . : 192.0.2.1Compare the assigned subnet, resolver and lease with the intended DHCP scope. A timeout reaching DHCP calls for link/VLAN, relay, scope exhaustion and server checks. Renewal does not guarantee the old address returns and does not apply to static configuration.
MODIFIES addressing; elevated CMD and independent console recommended. Ensure the DHCP path works before release. If renewal fails, use the recorded configuration and console recovery; do not invent a static IP outside IPAM.
ping: finite ICMP reachability and latency probes
Send a bounded number of echo requests to the gateway, then the target IP. Use the same source host and time interval when comparing a branch latency incident.
CMD syntax: ping /n count /w timeout-ms target
ping /n 4 /w 1000 192.0.2.1
ping /n 4 /w 1000 198.51.100.20Illustrative output excerpt; actual values vary.
Reply from 198.51.100.20: bytes=32 time=12ms TTL=124
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)Time shows round-trip latency and Lost counts unanswered echoes. TTL is the remaining value in the reply packet and cannot reliably identify the operating system. Request timed out may result from ICMP filtering; for Destination host unreachable, inspect the reporting address. Even complete ping success establishes neither TCP/445 access nor an SMB login.
Probe traffic, no configuration change; standard user. Avoid unbounded /t, large floods or unauthorized external targets. Do not use a few replies as a throughput benchmark.
tracert: locate the responding routed hops
Trace the routed path without reverse-DNS delays. A network team compares the first hop with the intended branch gateway and a known-good trace.
CMD syntax: tracert /d /h maximum-hops /w timeout-ms target
tracert /d /h 15 /w 1000 198.51.100.20Illustrative output excerpt; actual values vary.
1 1 ms 1 ms 1 ms 192.0.2.1
2 * * * Request timed out.
3 12 ms 12 ms 13 ms 198.51.100.20Each row is a TTL hop and three probe round-trip times. A silent middle hop followed by a reachable destination is not proof of packet forwarding failure. Different routes can reflect ECMP; trace does not expose the return path or necessarily the TCP service path.
Probe only; standard user. Timeout indicates missing ICMP response, not automatically a failed router. Share topology output through approved channels.
pathping: sample loss over a routed path
Combine hop discovery with repeated ICMP statistics for intermittent loss. Run during the incident and compare endpoint loss with downstream hops.
CMD syntax: pathping /n /q queries /p period-ms target
pathping /n /q 20 /p 250 198.51.100.20Illustrative output excerpt; actual values vary.
Hop RTT Lost/Sent = Pct Address
1 1ms 0/20 = 0% 192.0.2.1
3 12ms 1/20 = 5% 198.51.100.20This abbreviated teaching table omits the separate Source-to-Here and This-Node/Link columns in actual output. They distinguish cumulative loss from node/link sampling. Loss at one router that does not continue downstream commonly reflects control-plane rate limiting. Twenty samples are weak evidence; confirm with longer authorized samples and application telemetry.
No configuration change; standard user. It takes longer than tracert and generates repeated probes. A nonresponding target or ACL can invalidate loss interpretation; never declare an SLA breach from this alone.
nslookup: question a specific DNS resolver
Resolve a record through the configured or explicitly selected DNS server. Compare an affected branch resolver with the approved authoritative/resolver path.
CMD syntax: nslookup [-type=record-type] name [dns-server]
nslookup -type=A files01.corp.example.com 192.0.2.53Illustrative output excerpt; actual values vary.
Server: dns01.corp.example.com
Address: 192.0.2.53
Name: files01.corp.example.com
Address: 198.51.100.20In nslookup output, the initial Address identifies the DNS server; the record's Address is the resolved destination. NXDOMAIN means this resolver considers the name nonexistent, while timeout means no timely reply arrived. Server: Unknown can simply mean the DNS server lacks a PTR record. Check the exact FQDN and A/AAAA records, then test TCP separately.
Query only; standard user. Use only organizationally approved resolvers; sending private names to public DNS leaks information. It does not clear caches or alter resolver configuration.
netstat -ano: listeners and owning process IDs
List listeners and connections with numeric addresses and PIDs. Run on the file server to identify whether TCP/445 has a local listener, or on the client to inspect its current connections.
CMD syntax: netstat -ano
netstat -ano
tasklist /fi "PID eq 4"Illustrative output excerpt; actual values vary.
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4Local Address is the bind endpoint, Foreign Address the peer and PID the owner in this snapshot. LISTENING differs from ESTABLISHED; SYN_SENT suggests pending TCP establishment. A localhost-only bind cannot serve remote clients. UDP lines have no TCP state. The sample PID 4 is illustrative; inspect the actual owner.
Read-only; normal user for -ano, process details may require elevation. Do not kill a process solely from its port number. Do not assume an open listener is reachable through a firewall.
arp -a: inspect IPv4 neighbor mappings
Inspect the local IPv4 neighbor cache when a gateway is unreachable or an address appears duplicated. It maps neighbors on the local link, not every remote server.
CMD syntax: arp -a [IPv4-address] [-N local-interface-IPv4]
ping /n 1 192.0.2.1
arp -a 192.0.2.1Illustrative output excerpt; actual values vary.
Interface: 192.0.2.10 --- 0xc
Internet Address Physical Address Type
192.0.2.1 02-00-5e-10-00-01 dynamicInterface selects the local adapter cache; Type distinguishes dynamic/static entries. A routed server normally uses the gateway MAC. Missing entries can mean no traffic, wrong VLAN or unanswered ARP. A changing MAC requires switch/IPAM checks and may be legitimate HA behavior; it is not proof of spoofing by itself. IPv6 uses neighbor discovery instead.
arp -a is read-only and normally unprivileged. Avoid arp -d or static arp -s during evidence capture; these modify the cache and need elevated access. Do not clear all entries to mask an unresolved duplicate IP.
route print: read the routing decision inputs
Inspect IPv4 routes and interface indexes before adding anything. Use it to identify a VPN route overriding the intended branch path.
CMD syntax: route print [-4|-6]
route print -4Illustrative output excerpt; actual values vary.
Interface List
12...02 00 5e 10 00 10 ......Ethernet
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.0.2.1 192.0.2.10 25The default route is 0.0.0.0/0. More-specific prefixes win before metric comparison; route and interface metrics affect selection among comparable routes. Multiple interfaces are normal. Validate the actual destination with PowerShell route diagnostics rather than deleting every extra default route.
Read-only; standard user. route /f clears routes and is not a diagnostic alternative. Record the interface index before any scoped route change.
route add: a controlled temporary route
Add one nonpersistent IPv4 lab route to test an approved alternative path. Gateway must be reachable on the selected interface.
CMD syntax: route add destination mask netmask gateway metric cost if interface-index
route add 203.0.113.0 mask 255.255.255.0 192.0.2.1 metric 20 if 12
route print 203.0.113.*Illustrative output excerpt; actual values vary.
OK!Confirm the route is present and run the same endpoint test. OK only confirms acceptance of the entry, not that the next hop forwards packets. Access denied requires elevation; an invalid interface or off-link gateway requires correcting the recorded topology. Index 12 is a placeholder from this fictional interface list.
MODIFIES routing; elevated CMD, console and approved change required. Do not use /p until persistence is explicitly required. The accompanying route delete card is rollback for this exact new entry; never replace an existing production route without recording it.
route delete: remove only the added test entry
Undo the previous temporary lab route after its test. Match destination, mask, gateway and interface to avoid removing a different route.
CMD syntax: route delete destination mask netmask gateway if interface-index
route delete 203.0.113.0 mask 255.255.255.0 192.0.2.1 if 12
route print -4Illustrative output excerpt; actual values vary.
OK!The test route should be absent afterward; repeat the original connectivity test. Element not found can mean it was never added, already removed or the selector differs. Do not broaden the selector to a wildcard to force success.
MODIFIES routing and requires elevated CMD. Removing a route used for remote administration can terminate your session. Keep the exact previous route for rollback if this was an approved production removal.
getmac: correlate adapter identity with the switch
Display MAC addresses and verbose interface names for inventory or switch-port correlation. Use the active adapter rather than assuming the first row is Ethernet.
CMD syntax: getmac /v /fo list
getmac /v /fo listIllustrative output excerpt; actual values vary.
Connection Name: Ethernet
Network Adapter: Example Ethernet Adapter
Physical Address: 02-00-5E-10-00-10Connection Name maps to the Windows adapter, Physical Address to its current MAC. Disconnected, VPN and virtual adapters may also appear. An unexpected MAC may reflect virtualization or randomized Wi-Fi addressing; reconcile with authorized inventory.
Local read-only query; normal user. Do not use remote /p plaintext credentials or treat MAC identity as authentication. Protect hardware identifiers in exported reports.
hostname: confirm which computer is being tested
Print the local host name to prevent collecting evidence from the wrong RDP session. Compare with the asset and incident record.
CMD syntax: hostname
hostnameIllustrative output excerpt; actual values vary.
BRANCH-PC01The name is not an IP address or proof that DNS is correct. Compare ipconfig /all DNS suffix and nslookup for the registered FQDN. A tool-not-found error calls for checking the command shell, system directory and policy.
Read-only; normal user. hostname does not rename the computer or join a domain. Do not confuse a short host name with a unique fleet-wide identity.
netsh: read interface and firewall state safely
Use the specific show context to inspect IPv4 configuration and firewall profiles. This helps diagnose an unexpected local profile while preserving evidence.
CMD syntax: netsh interface ipv4 show config; netsh advfirewall show allprofiles (separate commands)
netsh interface ipv4 show config
netsh advfirewall show allprofilesIllustrative output excerpt; actual values vary.
Configuration for interface "Ethernet"
DHCP enabled: Yes
Domain Profile Settings:
State ONInspect address/default gateway and the active domain/private/public profile with the system networking UI or PowerShell as needed. State ON means firewall enabled, not that a particular flow is denied. A context not found can mean missing feature/build differences; use netsh ? and context help.
These show commands are read-only; start as a normal user, elevate only if access policy requires it. netsh int ip reset, winsock reset and advfirewall reset are separate disruptive changes, potentially requiring restart and loss of settings. Do not disable all profiles or export Wi-Fi keys to clear a diagnostic failure.
net use: test authorized SMB access and remove the test mapping
First list current SMB mappings; then, only for an approved share and unused drive letter, create a temporary mapping in the affected user session. This tests authentication/share access beyond TCP connectivity.
CMD syntax: net use; net use drive: \\server\share * /user:DOMAIN\user /persistent:no; net use drive: /delete (separately)
net use
net use Z: \\files01.corp.example.com\Operations * /user:CORP\ops.user /persistent:no
dir Z:
net use Z: /deleteIllustrative output excerpt; actual values vary.
Status Local Remote
OK Z: \\files01.corp.example.com\OperationsThe asterisk prompts for the password; do not put the password in a command, script or ticket. OK confirms mapping, while dir checks permitted enumeration, not write permission. Error 5 suggests authorization; 53 network/name path; 67 share name; 1219 conflicting credentials to the same server. Review existing sessions before disconnecting only the approved conflicting mapping.
net use alone is read-only. Mapping/deletion MODIFIES this user session; normal user usually suffices, with valid share/NTFS rights. Deletion can interrupt open files. Do not run net use * /delete, store credentials with /savecred or switch to IP merely to bypass an identity problem. Never enable SMB1 as a repair.
net view: enumerate the named server’s shares
Request the resources shared by a known server after DNS and TCP/445 succeed. Use explicit server selection rather than network-wide browsing as a health test.
CMD syntax: net view \\server [ /all ]
net view \\files01.corp.example.comIllustrative output excerpt; actual values vary.
Share name Type Remark
Operations Disk Operations filesShare name is the UNC share component and Type is the resource kind. Enumeration permissions may differ from access to a known share. Error 5 requires identity/authorization checks; 53 suggests name/path/service checks. A failed browse list does not justify enabling obsolete Computer Browser or SMB1 services.
Read-only request; normal user with server enumeration rights. Output can disclose share names; do not enumerate servers outside authorized scope. It neither maps a drive nor tests application write operations.
Test-NetConnection: PowerShell TCP and route diagnostics
Purpose: test one TCP service port or diagnose route selection. Use Windows PowerShell 5.1, not CMD. Syntax: Test-NetConnection -ComputerName host -Port number -InformationLevel Detailed; route diagnosis is a separate parameter set and cannot be combined with -Port.
$Target = 'files01.corp.example.com'
Resolve-DnsName $Target -Type A
Test-NetConnection -ComputerName $Target -Port 445 -InformationLevel Detailed
Test-NetConnection -ComputerName '198.51.100.20' -DiagnoseRouting -InformationLevel Detailed
Get-NetIPConfiguration
Get-SmbConnectionIllustrative TCP output excerpt; route diagnostics return different fields.
ComputerName : files01.corp.example.com
RemoteAddress : 198.51.100.20
RemotePort : 445
InterfaceAlias : Ethernet
SourceAddress : 192.0.2.10
TcpTestSucceeded : TrueRemoteAddress is the actual resolved target; SourceAddress and InterfaceAlias reveal the selected source/VPN path. TcpTestSucceeded tests TCP establishment, not SMB authorization or TLS/application health. False may mean timeout, rejection, no listener or wrong route; compare with server listener and firewall logs. The route parameter set reports SelectedNetRoute and selected source. DNS resolution warnings call for resolver checks before interpreting a port failure.
Read-only probes; standard user normally suffices. Confirm Get-Command Test-NetConnection and Get-Module -ListAvailable NetTCPIP when unavailable. Installing generic PowerShell on another OS does not supply this Windows module. Query only permitted endpoints and do not interpret a successful port probe as permission to access a share.
Capture evidence without changing the network
Run this separate PowerShell block after setting Target. It creates a new troubleshooting directory under your user TEMP location. Protect the reports and record the actual command exit status; success creating a report is not success of the contained network probe.
$Target = 'files01.corp.example.com'
$ReportPath = Join-Path $env:TEMP ('Network-' + (Get-Date -Format 'yyyyMMdd-HHmmss'))
New-Item -ItemType Directory -Path $ReportPath -ErrorAction Stop | Out-Null
ipconfig /all | Out-File (Join-Path $ReportPath 'ipconfig.txt') -Encoding utf8
route print | Out-File (Join-Path $ReportPath 'routes.txt') -Encoding utf8
Test-NetConnection $Target -Port 445 | Export-Clixml (Join-Path $ReportPath 'tcp445.xml')Reachability differs from service function
Separate TCP probes from functional SMB tests. Correlate latency, reconnects and network events with incident timing. Monitor from a subnet representative of user access.
DNS timeout, closed port or access denied
If the destination is reachable by IP but DNS requests time out, inspect the configured resolver, port-53 access and DNS suffix. If ping works but TCP fails, investigate listeners and ACLs. If TCP succeeds but SMB returns Access Denied, investigate the user identity and share/NTFS permissions.
Get-NetTCPConnection -State Listen | Select-Object LocalAddress,LocalPort,OwningProcess
$Listener = Get-NetTCPConnection -LocalPort 445 -State Listen -ErrorAction SilentlyContinue | Select-Object -First 1
if ($null -ne $Listener) {
Get-Process -Id $Listener.OwningProcess
} else {
Write-Warning 'No TCP/445 listener found on this host'
}
Get-WinEvent -LogName 'Microsoft-Windows-SMBClient/Connectivity' -MaxEvents 20 -ErrorAction SilentlyContinueInspect listeners on the file server, not the client. Empty output means no matching listener on that host. Unresponsive tracert hops alone do not prove application loss because ICMP might be limited.
DNS failure
nslookup -type=A files01.corp.example.com 192.0.2.53
ipconfig /displaydnsIf the configured resolver times out, check resolver reachability and DNS service/ACLs. NXDOMAIN requires record/zone/FQDN checks. If direct server queries are right but the application uses an old IP, preserve then clear the client cache and inspect application caching. Do not flush every machine before comparing evidence.
No connectivity or wrong gateway
ipconfig
route print -4
ping /n 3 192.0.2.1
arp -a 192.0.2.1An off-subnet/wrong gateway or absent default route explains remote failures. If even the local gateway has no neighbor entry after traffic, inspect link, VLAN and switch path. If gateway works but remote TCP fails, continue with route and server checks. Correct the DHCP scope or authoritative static configuration, not a random client route.
Unexpected routing or duplicate IP
route print -4
tracert /d /h 15 198.51.100.20
arp -aCompare selected source/interface through the separate PowerShell route diagnostic. A more-specific VPN route can override the branch default. For suspected duplicate IP, compare neighbor MACs with switch tables and IPAM over time; verify HA/virtual MAC behavior. Route deletion and ARP clearing destroy evidence and are not the first step.
TCP succeeds but SMB fails
net view \\files01.corp.example.com
net useWhen TCP works but the share does not, move the investigation to identity and authorization. Confirm TCP/445 in PowerShell and the listener with netstat -ano on the file server, then test an approved temporary mapping and share/NTFS permissions. Analyze errors 5/53/67/1219 without clearing every session. Replacing the hostname with an IP can change Kerberos and SPN behavior, so it is not an equivalent authorization test.
Latency and packet loss
ping /n 20 /w 1000 198.51.100.20
pathping /n /q 20 /p 250 198.51.100.20Capture at incident time from the affected subnet. Compare destination loss/latency with application telemetry and switch error counters. Isolated silent/slow intermediate hops can be ICMP rate limiting. Persistent loss extending to the destination needs path investigation; TCP retry and application logs establish actual user impact.
Limited corrections and retesting
After locating the failed layer, record the previous route or rule and prepare to reverse that specific change. Release and netsh int ip reset can disconnect remote management and require a console and recovery plan. Completion means the original hostname, port and application work again through the user's path.
Hostnames and IPs in authentication
IP tests help isolate DNS, but SMB by IP might change Kerberos behavior. Do not assume IP and hostname tests are equivalent. Netstat/PID output is only a snapshot.
Best Practices
- Version-control configuration and review changes.
- Use least privilege and explicit allow-lists.
- Automate repeatable checks and monitor the expected state.
- Test upgrades and restores before production rollout.
Conclusion
A reliable implementation of Windows Network Commands for DNS, TCP and SMB Diagnostics is more than a successful first run. Keep the configuration documented, observable, recoverable, and aligned with the team's change-management process.
Frequently Asked Questions
Does successful ping prove SMB is healthy?
No. Test TCP/445, authentication and permissions independently.
Should DNS cache be cleared first?
No. Record and compare cached and resolver responses before clearing it.
