Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, January 22, 2018 11:13 PM
Hello, I`m unable to access my Mapped Azure VM Share Folder.
Error - Windows Cannot Access \10.1.x.x
Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose.
Error Code: 0x80070035
The network path was not found.
All replies (9)
Monday, January 22, 2018 11:55 PM
Is this the first time you are trying to connect to it? Or were you able to connect and now you are noticing you cannot?
Tuesday, January 23, 2018 12:03 AM
I created this 2 weeks ago and was able to connect to it until today.
I can logon to the VM and access this File Share etc.. But I cannot mapped to it.
Tuesday, January 23, 2018 2:07 AM
Thanks for that. So at least we can access the VM. That tells us the network is OK.
Have you ensured you have setup the correct sharing permissions on the drive?
In addition, if you do have it shared correctly try turning off the firewall momentarily to see if that helps.
Tuesday, January 23, 2018 9:11 PM
Yeah, it was Shared and Turning off/on Firewall doesn`t help.
Note: In my setup in Azure, I have a Virtual Network setup. Usually the status will show as "Connected" and Data in and Data out stays the same.
Tuesday, January 23, 2018 9:54 PM
Are you able to navigate to it via file explorer from another VM?
Such as just following the shared link that is generated when changing the sharing properties?
Wednesday, January 24, 2018 5:04 PM
Sorry, I don`t have another VM setup to test this on. I think I know the problem though, but I don`t know how to fix it. I can`t share a screenshot here but If you don`t mind, I can ping you over IM and share my desktop. My Alias is V-Kroade.
Cheers,
Kross.
Wednesday, January 24, 2018 5:32 PM
Just a quick Overview - There is An Azure site-to-site VPN connection that`s stopped working for one reason or another. It was working fine last week and this week it stopped. The status is stuck on "Connecting" Data in is stuck on 6.09 KiB and Data out stuck on 216 B. I checked the Error log on Meraki, It says:
| Jan 24 09:30:16 | Non-Meraki / Client VPN negotiation | msg: phase2 negotiation failed due to time up waiting for phase1. ESP 40.xx.xx.xx[0]->50.xx.xx.xx[0] | |
| Jan 24 09:29:45 | Non-Meraki / Client VPN negotiation | msg: initiate new phase 1 negotiation: 50.xx.xx.xx[500]<=>40.xx.xx.xx[500] | |
| Jan 24 09:29:35 | Non-Meraki / Client VPN negotiation | msg: phase1 negotiation failed due to time up. | |
| Jan 24 09:29:16 | Non-Meraki / Client VPN negotiation | msg: phase2 negotiation failed due to time up waiting for phase1. | |
| Jan 24 09:28:44 | Non-Meraki / Client VPN negotiation |
msg: initiate new phase 1 negotiation: |
I checked an article "Troubleshooting: An Azure site-to-site VPN connection cannot connect and stops working" But we`re not setup as Route-based but rather Policy-Based
Wednesday, January 24, 2018 6:36 PM
I will ping/ email you offline and we can take a look.
-Micah
Saturday, February 24, 2018 4:15 AM
Just coming back to this thread. We have determined this issue was due to a VPN issue not an actual fileshare issue. No VPN = No file share.
It was advised to work on the VPN issue and then look back into the fileshare