Location:
State:
Carrier
Country
Status

Insider Preview network discovery not working.


I have 2 identical machines that I use for various system setups, one of which is the Insider Preview program.
The machines are Gigabyte MB with i7-47908 processor with 16 GB main memory.
Starting with 14915, the mapped NAS drives on my system failed to work:
When logged in with my MS account, any attempt to map NAS drives or to access previously mapped drives gives me the following error:
"An error occurred while reconnecting N: to \<NAS Address>Download
Microsoft Windows Network: A specified logon session does not exist. It
may already have been terminated.
This connection has not been restored."
When logged in with my local account, I CAN map and access the NAS locations, however, none of them show up in the Network area of Windows Explorer.
This happens with Insider Preview 14915 as well as 14926.
Insider Preview 14901 worked fine with mapping and accessing with MS login as well as Local login.
I do have homegroup set up and it seems to be working fine.

I have also tried a completely fresh install on a new drive with the same results.

Does anybody have any recommendations?
Thanks,

I have 2 identical machines that I use for various system setups, one of which is the Insider Preview program.
The machines are Gigabyte MB with i7-47908 processor with 16 GB main memory.
Starting with 14915, the mapped NAS drives on my system failed to work:
When logged in with my MS account, any attempt to map NAS drives or to access previously mapped drives gives me the following error:
"An error occurred while reconnecting N: to \<NAS Address>Download
Microsoft Windows Network: A specified logon session does not exist. It
may already have been terminated.
This connection has not been restored."
When logged in with my local account, I CAN map and access the NAS locations, however, none of them show up in the Network area of Windows Explorer.
This happens with Insider Preview 14915 as well as 14926.
Insider Preview 14901 worked fine with mapping and accessing with MS login as well as Local login.
I do have homegroup set up and it seems to be working fine.

I have also tried a completely fresh install on a new drive with the same results.

Does anybody have any recommendations?
Thanks,
I had this problem too. I used the Windows Credential Manager (Control Panel/User Accounts/Credential Manager/Manage Windows Credentials) to fix it.
I added a Generic Credential with my NAS as the Network address and it's admin/password. That worked!

In the Windows Credentials form you might have use the network name or IP for the user example: devicename/user

In a CMD prompt you can set drive mappings (net use * /delete deletes existing network drive mappings and "z" is your choice for drive letter)

netuse * /delete
netuse z: \devicenameshare password /user:devicenameuser

Some people have correlated using PIN to login as a problem, they revert to full password to login to Windows and their shares are back. I'm using PIN and the above worked for me on Build 14926

I have this same issue for 14915 as well as 14926.
BTW, 14901 works fine!
I can map the NAS shares but the devices are NOT visible in Network in Windows Explorer.
I can see the shares using net view \<NAS-Name>
but with net view, I get System error 1312 has occurred. A specified logon session does not exist. It may already have been terminated.
This same command (net view) works fine in 1607 (14393.187)
In the Insider preview, I had problems mapping my NAS shares when using the MS login, but worked OK using the local login.

Yes, network discovery has been crippled for me, and others, as well.

Basically, we have lost the ability to query the Master Browser, probably because NetBIOS is not functioning.

It will work if your comp is the MB but not otherwise.

Network discovery has FINALLY been fixed in IP 14936, I can actually see my NAS devices/shares again! Now, I got to see if I can get the Homegroup working properly again - leaving the Homegroup on all my machines and re-creating a new one with the IP machine.

Insider Preview network discovery not working.