| Previous | Next |
| STATUS_NO_QUOTAS_FOR_ACCOUNT | STATUS_PAGE_FAULT_TRANSITION |
STATUS_PRIMARY_TRANSPORT_CONNECT_FAILED
The preferred network transport failed but fallback succeeded
This successful status records a degraded connection path. The client first tried the transport ranked as primary for the remote server, that attempt failed, and a secondary transport completed the connection. In older redirector and workstation-service designs, more than one network transport could be enabled and ordered for remote file access.
The application may continue, but diagnostics should preserve both attempts. A working fallback does not prove that the preferred adapter, protocol binding, route, name resolution path, or server listener is healthy. Reordering transports or disabling one can hide the symptom while changing latency, authentication behavior, or reachability.
What to inspect
- Record the primary and fallback transport names and remote address.
- Compare routes, interface bindings, name resolution, and firewall policy for both paths.
- Do not treat the fallback success as proof that the preferred path is correctly configured.
References
- Microsoft Open Specifications: NetrWkstaTransportEnum
- Microsoft Open Specifications: WKSTA_TRANSPORT_INFO_0
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.