Useful diagnostics explain what failed without changing a workstation's network settings. Run tests against destinations you are authorized to use, and keep the results inside your support ticket or approved secure channel.
Collect three kinds of evidence
In Command Prompt, view the active adapter's addressing:
ipconfig /allThen check resolution for the affected hostname:
nslookup example.comIn Windows PowerShell, test a TCP connection to the affected service's HTTPS port:
Test-NetConnection -ComputerName example.com -Port 443Replace example.com with the hostname support asks you to test. Do not scan ranges of addresses or try unrelated ports. These commands do not require a network reset.
Understand the limits
A successful TCP test means the connection to that port was established. It does not verify the certificate, application response, user permissions, or sign-in flow. A successful DNS lookup also does not prove the application is available. Share the application's own error alongside the command output.
Report a reproducible problem
Include the local time and timezone, device, connection type, affected application, and whether a second device works. Diagnostic output can contain internal names and addresses; do not post it publicly. Avoid uninstalling adapters, resetting TCP/IP, changing DNS, or disabling the firewall unless your authorized support team directs the next step.
Get help with your network
For an existing service issue, open an AvrinTech support ticket. For an assessment or planned improvement, request a scoped proposal and review our networking services. Work, coverage, and response targets depend on your agreement.
