SMB Connection to Server fails with "The Network path was not found", SMB attempts to connect over HTTP

Plasma

6/9/23, 10:35 AM

Have an issue where one spesific user is unable to connect to any SMB shares on any Windows Servers, they are not in the same domain, but there's Trust between the domains, and their user has the correct rights on the Shares. It's working for the other users in the same Office who are running the same configuration. Running Fiddler on the client computer shows that it's attempting to connect using HTTP instead of TCP.

This occurs if I'm testing with the FQDN, servername or IP, the server answers on pings just fine, and I'm able to open an SMB share on the computer from the Server.

Eventviewer

In the SMBClient -> Connectivity Logs, it's filled with Event ID 30800 events, with the following content:

The server name cannot be resolved.

Error: The requested interface is not supported.

Server name: REMOTESERVER

Guidance: The client cannot resolve the server address in DNS or WINS. This issue often manifests immediately after joining a computer to the domain, when the client's DNS registration may not yet have propagated to all DNS servers. You should also expect this event at system startup on a DNS server (such as a domain controller) that points to itself for the primary DNS. You should validate the DNS client settings on this computer using IPCONFIG /ALL and NSLOOKUP.

Test-Netconnection

Test-NetConnection -ComputerName 'REMOTESERVER' -port 445

Result:

ComputerName : REMOTESERVER
RemoteAddress : X
RemotePort : 445
InterfaceAlias : Local Area Connection
SourceAddress : X
TcpTestSucceeded : True

I'm at a bit of a loss of where to even start troubleshooting this issue, we had one client with the same problem a couple years ago but that one we ended up just reinstalling.

311

0 + 0

networking

windows

network-share

server-message-block

windows-10

Greg Askew

6/9/23, 11:17 AM

And NSLookup...?

Plasma

6/9/23, 11:50 AM

nslookup/Resolve-DNSName resolves correctly to the server in question.

Greg Askew

6/9/23, 1:36 PM

Does using the IP address work? `dir \\n.n.n.n\sharename`

Plasma

6/9/23, 3:12 PM

Nope, FQDN, IP nor servername works, exact same error message and error in event log.

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: SMB Connection to Server fails with "The Network path was not found", SMB attempts to connect over HTTP

TH: การเชื่อมต่อ SMB ไปยังเซิร์ฟเวอร์ล้มเหลวด้วย "ไม่พบเส้นทางเครือข่าย" SMB พยายามเชื่อมต่อผ่าน HTTP

RO: Conexiunea SMB la server eșuează cu „Calea de rețea nu a fost găsită”, SMB încearcă să se conecteze prin HTTP

RU: Сбой подключения SMB к серверу с сообщением «Сетевой путь не найден», SMB пытается подключиться через HTTP

VI: Kết nối SMB với máy chủ không thành công với "Không tìm thấy đường dẫn mạng", SMB cố gắng kết nối qua HTTP

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.