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. I can ping my phones IP (Ping 192.168.1.14) I can connect with my browser ( https://192.168.1.14:8080/ ) I cannot connect or Map using my IP with a "net use" command or "Map Network Drive". Net use Y: \192.168.1.14\Storage\Emulated\0 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.

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.

"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

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.

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)

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.

I cannot map a drive with the ip address

Jeffrey Grammer 0

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.

I can ping my phones IP (Ping 192.168.1.14)
I can connect with my browser (https://192.168.1.14:8080/)
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.

Jeffrey Grammer 0 Reputation points

2024-09-26T00:54:06.2866667+00:00

I tried your stuff no luck. I noticed the reference to SMB which sounds familiar. I think I had to enable it at work a couple of years ago for an issue like this. So, I used these statements.

Detect:

Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

Disable:

Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

Enable:

Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

5 answers

Kapil Arya 8,126 Reputation points MVP

2024-09-25T08:54:15.04+00:00

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.
Please sign in to rate this answer.
Jeffrey Grammer 0 Reputation points

2024-09-25T14:29:13.1766667+00:00

I tried both things but still it can't see my drive. Thanks anyway

Jeffrey Grammer 0 Reputation points

2024-09-25T14:32:51.0366667+00:00

I tried both suggestions, but I still can't map by IP

Jeffrey Grammer 0 Reputation points

2024-09-26T00:49:00.2166667+00:00

That didn't work, but I noticed the references to smb which sounded very familiar.

So, I used these powershell statements to enable SMB1. I was not enabled.

Detect:

Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

Disable:

Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

Enable:

Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
MotoX80 33,471 Reputation points

2024-09-25T15:34:22.39+00:00
"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
Please sign in to rate this answer.
Jeffrey Grammer 0 Reputation points

2024-09-26T00:59:03.07+00:00

No Luck Thanks anyway

PS C:\WINDOWS\system32> Test-NetConnection -ComputerName 192.168.1.14 -CommonTCPPort SMB

WARNING: TCP connect to (192.168.1.14 : 445) failed

ComputerName : 192.168.1.14 RemoteAddress : 192.168.1.14 RemotePort : 445 InterfaceAlias : Wi-Fi SourceAddress : 192.168.1.27

PingSucceeded : True

PingReplyDetails (RTT) : 12 ms

TcpTestSucceeded : False

Jeffrey Grammer 0 Reputation points

2024-09-26T01:03:45.33+00:00

No luck thanks anyway

PS C:\WINDOWS\system32> Test-NetConnection -ComputerName 192.168.1.14 -CommonTCPPort SMB

WARNING: TCP connect to (192.168.1.14 : 445) failed

ComputerName : 192.168.1.14 RemoteAddress : 192.168.1.14 RemotePort : 445 InterfaceAlias : Wi-Fi SourceAddress : 192.168.1.27

PingSucceeded : True

PingReplyDetails (RTT) : 12 ms

TcpTestSucceeded : False

MotoX80 33,471 Reputation points

2024-09-26T02:57:05.12+00:00

Well sure, if 192.168.1.14 is your phone, you installed "WebDav from Google Play", not an SMB (network share) server software. The fact that Test-Netconnection failed just verifies the fact that your phone is not listening on SMB port 445. And "net use" isn't going to work.

Did you follow the instruction in the link that I posted to map the drive using WebDav?

Did you do step 6?

If you configured that software to listen on port 8080 on your phone, then that's what you will need to connect to. Map the drive to https://192.168.1.14:8080
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Jing Zhou 6,860 Reputation points Microsoft Vendor

2024-09-26T07:26:34.0833333+00:00

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.
Please sign in to rate this answer.
Jeffrey Grammer 0 Reputation points

2024-09-26T12:56:50.11+00:00

You did not ask but it will ping just fine

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

The error is net use y: \\192.168.1.14\storage\emulated\o admin /user:admin /persistent:no /y System error 67 has occurred. The network name cannot be found.

The network name cannot be found.

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.

FeatureName : SMB1Protocol

DisplayName : SMB 1.0/CIFS File Sharing Support

Description : Support for the SMB 1.0/CIFS file sharing protocol, and the Computer Browser protocol.

RestartRequired : Possible

State : Enabled

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

yes

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

443 no 8080 yes It just opens a blank screen but ctrl + ] goes to a telnet prompt

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

I checked the firewall is turned off

Jeffrey Grammer 0 Reputation points

2024-09-26T13:00:14.43+00:00

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?

The error is net use y: \\192.168.1.14\storage\emulated\o admin /user:admin /persistent:no /y System error 67 has occurred. The network name cannot be found.

The network name cannot be found.

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.

FeatureName : SMB1Protocol

DisplayName : SMB 1.0/CIFS File Sharing Support

Description : Support for the SMB 1.0/CIFS file sharing protocol, and the Computer Browser protocol.

RestartRequired : Possible

State : Enabled

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

yes

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

443 no 8080 yes It just opens a blank screen but ctrl + ] goes to a telnet prompt

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

I checked the firewall is turned off

Jeffrey Grammer 0 Reputation points

2024-09-26T14:36:40.98+00:00

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. I'm on>

Host Name:

OS Name: Microsoft Windows 11 Pro

OS Version: 10.0.26120 N/A Build 26120

Jeffrey Grammer 0 Reputation points

2024-09-26T14:39:16.4433333+00:00

to see the successful mapping go to minute about minute 13:37 on this video https://youtu.be/aMBK675WCDQ

MotoX80 33,471 Reputation points

2024-09-26T15:22:11.2366667+00:00

Try mapping the drive using the highlighted link.

Start with just the IP address and port number. If it doesn't work, please share the error message that you get. A screen image where we can see what you typed in and the resulting error message would be preferable.

Jeffrey Grammer 0 Reputation points

2024-09-27T01:31:01.3966667+00:00

Thanks, MotoX80, I did try that. In fact, that youtube video I mentioned earlier used that. I learned that you could enter a url directly in the normal Map Network Drive dialog box and it is the same as using that link. I'm usually the one helping others, this has me stumped. I truly appreciate all your help.

https://youtu.be/aMBK675WCDQ
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Jeffrey Grammer 0 Reputation points

2024-09-27T01:49:10.8166667+00:00

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)
Please sign in to rate this answer.
MotoX80 33,471 Reputation points

2024-09-27T12:41:39.0166667+00:00

I can connect with my browser (https://192.168.1.14:8080/)

You should have gotten some warnings about the certificate then. With HTTPS the URL on the request needs to match the certificate on the server. Like with this web site.

What certificate is your phone returning?

If you see "Not secure" then you are using HTTP.

Open a command prompt and copy/paste/run these commands. (Use current IP if it changed.)

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

What output do you get?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Jeffrey Grammer 0 Reputation points

2024-09-28T15:00:54.1533333+00:00
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.
Please sign in to rate this answer.
MotoX80 33,471 Reputation points

2024-09-28T15:51:46.7666667+00:00

HTTP/1.1 200 OK Server: NWebDav/2.4.8724.38630

You are using HTTP, not HTTPS.

How did you configure the software on your phone? Did you set it to anonymous authentication, or did it allow you to define a userid+password to authenticate with?

Does it allow you to set a root folder? What did you set it to?

Go back to the "map a drive" dialog and try HTTP. http://192.168.1.14:8080/

Try it both ways, the "Folder" field and "Connect to a web site..." link.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.