I cannot map a drive with the ip address

Question

The drive I'm trying to map only has an IP. It is my phone. But the same rule applies to my Buffalo NAZ. I cannot map a drive in my Naz by IP. Luckily, I know my name of my NAZ server. So I am certain if I fix the issue of not being able to map by IP, I will be able to map my Naz drives by Ip as well as my phone. I am using WebDav from Google Play to make my phone act as a server.

1. I can ping my phones IP (Ping 192.168.1.14)
2. I can connect with my browser (https://192.168.1.14:8080/)
3. I cannot connect or Map using my IP with a "net use" command or "Map Network Drive".
   1. Net use Y: \192.168.1.14\Storage\Emulated\0
   2. Right click on My Computer in File Explorer and selecting "Map Network Drive"

Somewhere in the back of my mind I remember fixing this at work, I just can't remember how.

Answer 1

Hello,

See if this fix helps you:

https://www.kapilarya.com/fix-cant-map-network-drive-on-windows-11

Let us know if this helps!

Note: Included link in this reply refers to blog post by a trusted Microsoft MVP.

Answer 2

"Net use" is going to try to use SMB to map the drive. But you have WebDav on your phone.

Try following these steps.

https://www.maketecheasier.com/map-webdav-drive-windows10/

Your NAS should support SMB. You can use Powershell to test if a given IP has the SMB port open. And net.exe will list SMB shares. (Or tell you that the server can't authenticate you.)

Test-NetConnection -ComputerName 192.168.1.8 -CommonTCPPort SMB
net.exe view 192.168.1.8

Answer 3

Hello,

 

Thank you for posting in Q&A forum.

Can you let me know what's the error message displayed when you try to map the drive?

Meanwhile, to further troubleshoot this issue, please kindly try below steps:

1.Check the SMB protocol version on both of client and server and make sure they are consistent.

2.Check if Network discovery and File and printer sharing are turned on.

3.Check if you can succeed to telnet the server via TCP.Port 443 and 8080.

4.Check if the traffic is blocked by any firewall or antivirus.

 

I hope the information above is helpful.

If you have any questions or concerns, please feel free to let us know.

 

Best regards，

Jill Zhou

 

---

If the Answer is helpful, please click "Accept Answer" and upvote it.

Answer 4

I did try that, and it also failed.

System error 67 has occurred. The network name cannot be found.

I am normally the one that people call for help. This issue has me stumped

Here is a video that makes it look so easy. The narrator on the video explained the process extremely slow, but it works for him on win 10. To see the successful mapping go to minute about minute 13:37 on this video https://youtu.be/aMBK675WCDQ

I did notice that you can take a url and put it in the normal "Map Network Drive" and it does the exact same thing as the link "Connect to a Website that you can use to store your documents and pictures." Except when you use the standard mapping process but insert url's (http:// , https://) you get the option to assign a Drive character. (C drive or F drive)

Answer 5

So I ran each commands in Power Shell and in MS Edge

**1.**curl.exe -v http://192.168.1.14:8080/

This returned in Power Shell

PowerShell 7.4.5

PS C:\Users\ffejr> curl.exe -v http://192.168.1.14:8080/

• Trying 192.168.1.14:8080...
• Connected to 192.168.1.14 (192.168.1.14) port 8080

GET / HTTP/1.1

Host: 192.168.1.14:8080

User-Agent: curl/8.8.0

Accept: /

• Request completely sent off

< HTTP/1.1 200 OK

< Date: Sat, 28 Sep 2024 14:19:40 GMT

< Server: NWebDav/2.4.8724.38630

< Content-Length: 8348

< Content-Type: text/html; charset=UTF-8

<

At the end of the stuff above power shell also generated the web page that

http://192.168.1.14:8080 generates in your browser with the addition at the very bottom of the page this statement:

*** Connection #0 to host 192.168.1.14 left intact**

2.curl.exe -v https://192.168.1.14:8080/

This returned in Power Shell

PS C:\Users\ffejr> curl.exe -v https://192.168.1.14:8080/

• Trying 192.168.1.14:8080...
• Connected to 192.168.1.14 (192.168.1.14) port 8080
• schannel: disabled automatic use of client certificate
• schannel: using IP address, SNI is not supported by OS.
• ALPN: curl offers http/1.1
• schannel: next InitializeSecurityContext failed: SEC_E_INVALID_TOKEN (0x80090308) - The token supplied to the function is invalid
• Closing connection
• schannel: shutting down SSL/TLS connection with 192.168.1.14 port 8080

curl: (35) schannel: next InitializeSecurityContext failed: SEC_E_INVALID_TOKEN (0x80090308) - The token supplied to the function is invalid

This statement did not generate a web page, so this is all I have

3. curl -v -k --request PROPFIND https://192.168.1.14:8080/ 

This statement returned the exact same things as statement #2.