Recommended Posts

I installed Windows 10 build 10061 today. On booting, the first thing I did was connect to the network share (QNAP NAS). It connected fine and I installed MS Office 2013 off it.

 

But on reboot, it does not connect to it anymore. I can access the same NAS from another W 8.1 based laptop. I can also ping it from command prompt from within Windows 10.

 

Any ideas?

 

ad7u1pV.png

 

hjZc6a7.png

Found out what is causing it.

 

Did a fresh install again and connected to my network share.

 

Now I wanted to use 4 digit pin to log-in to Windows. So to create it, Windows asked me to verify my Microsoft account using 2-step verification and code was sent on my registered mobile number. Once it was done and 4 digit pin was set up, I restarted the PC. 

 

...and bang!! my network drive stopped connecting. What kind of weird bug is this? Completely a deal breaker. This has been going on since first public preview from Jan.

 

yTpw1Rw.png

I found a way to map a Nas drive.  Go to File Explorer,  Right click on Network shortcut.  Map network drive and enter the IP of you NAS drive using exp  \\192.168.1.2 is mine and hit browse.  You should be able to browse some of your folders there and then map them.  Or, after you hit browse, add the 192.168.1.2 to either quick links or quick access. 

 

I hope that helps.  It's a bit different but it works.

  • Like 1

IP addresses are different? Wow, and this whole time, when explorer wouldn't see my shares, and I typed the direct IP it was magic? Who knew.... /s

  On 28/04/2015 at 05:10, Obi-Wan Kenobi said:

IP addresses are different? Wow, and this whole time, when explorer wouldn't see my shares, and I typed the direct IP it was magic? Who knew.... /s

Wrong. It did not work even after typing direct IP. 

 

Worked once I disabled 4 digit pin while signing.

Open Control Panel (Not sure these are in the PC Settings app yet).

 

Click "Credential Manager"

Click "Windows Credentials"

Click "Add a Windows credential"

Type in the credentials you use with the QNAP device.

 

Assuming you have password protected shares.

  • 4 weeks later...

^^ 

Tried that but it just doesn't connect to the share if I verify my account using mobile number. If it is a local account, the mapped network share starts working again.

 

Same problem in build 10122.

 

I can ping the server fine. But as soon as I try to mount it by typing it's name or IP address in explorer, Windows cannot find it. This problem started right from 1st publicly available Windows 10 beta.

 

These days, over complicating things is the new IN-thing. Once the settings are over complicated, you hide them. Problem solved. (Y)

 

:angry:

  • 5 weeks later...

This problem continues to exist in leaked build 10147.

1. Map a network drive in This PC as Z:

2. Working flawlessly so far. I can browse all my files.

3. Go to settings and under Login, create 4 digit PIN to be used to login, instead of a regular password.

4. Reboot the PC.

5. BAM!! Network drive is now not accessible.

6. I can ping it through Command prompt but it just doesn't map no matter what.

7. I try to map it by typing IP address but still fail

8. Then again go to settings, and under Login, reset PIN. Then instead of entering new PIN, close the window to disable PIN completely and switch to login by Microsoft account password.

9. Reboot the PC.

10. Now the network drive can be mapped and works as before.

I just can't believe a bug like this is seeping through all the builds released so far.

I tried all the solutions but when PIN is enabled, the network drives just fail to mount no matter what.

Side note question:  In build 10130, I don't have an option to Reset PIN under my Settings > Accounts > Sign In Options.  There's a button for Forgot My PIN, and Change, but no Reset.  And typing in no PIN on the Change page doesn't work. So, is there a way to revert from using a PIN in 10130?

Thank god I found this thread.  The PIN problem was keeping me out of my network drives as well!  10130 and the new 10162 builds were the same.  

 

The only way I found to ditch the PIN is to go into Settings > Accounts, click sign in with a local account instead, create the local account, then do the same thing again - but choose sign in with Microsoft account.  When you're going through the setup for that, and it gets to the PIN option, choose no thanks.  You lose the convenience of the PIN, but signing in with your password on a Microsoft account allows you to connect to your network drives again!  

 

  On 29/06/2015 at 12:26, BeerFan said:

Side note question:  In build 10130, I don't have an option to Reset PIN under my Settings > Accounts > Sign In Options.  There's a button for Forgot My PIN, and Change, but no Reset.  And typing in no PIN on the Change page doesn't work. So, is there a way to revert from using a PIN in 10130?

I found another easier way to disable the PIN. Go into Settings > Accounts > Sign In Options. Clic on button for Forgot My PIN, Clic on Continue, you may be prompted to enter the password for your account, type it, and when ask for the new PIN, you clic on Cancel and then the PIN will be disable.

 

You must log off (no need restart) and signing again with your password on a Microsoft or local account allows you to connect to your network drives again!

  On 05/07/2015 at 04:32, ChrisPollard77 said:

Thank god I found this thread.  The PIN problem was keeping me out of my network drives as well!  10130 and the new 10162 builds were the same.  

 

The only way I found to ditch the PIN is to go into Settings > Accounts, click sign in with a local account instead, create the local account, then do the same thing again - but choose sign in with Microsoft account.  When you're going through the setup for that, and it gets to the PIN option, choose no thanks.  You lose the convenience of the PIN, but signing in with your password on a Microsoft account allows you to connect to your network drives again!  

 

This problem is solved.

 

enter username as servername\username

password as password

  • 3 weeks later...
Thank god I found this forum. Spend all day re-installing / repairing the Windows 10 trying to figure out what was causing this issue.

After a repair I could acces my network shares on my NAS, but thanks to this forum I now know the PIN was causing this issue for me.
W10 was released a few days ago in my country. Very bad from Microsoft.
 
Gonna report this bug on the official MS website.
  • 5 weeks later...

Has there been any solution to this issue? I have it on a new ASUS Zenbook (10 Home) and my custom built desktop (10 Pro), but not my Surface Pro 3 (10 Pro). It's not a huge deal, but I can't come up with any rational explnation as to why the pin vs password would limit what you can see on the network.

  • xendrome locked this topic
This topic is now closed to further replies.
  • Posts

    • Samsung Electronics has multiple subsidiaries. Samsung Display is a subsidiary that deals in screen manufacturing, it's a supply chain-based company where the staff solely care about manufacturing displays. Samsung Electronic's TV and Phone division may have other priorities, for example Samsung TV didn't want to go in on OLED because margins were lower when building the entire TV. Samsung Display's entire existence however now depends on OLED as they couldn't undercut Chinese LCD manufacturers but could compete against LG Display who is the only competitor in that market. Samsung Display has this screen manufacturing investment, but Samsung Mobile may not be willing to reduce their margins for going with a display technology that eats into the phone margins.
    • The weather looks gorgeous, I love the atmosphere of this new area.
    • Similar to what started me on the path to switching to Linux... for the first 6mo of Win10 it was installing an AMD GPU driver that broke audio over HDMI which was essential to me. Driver from AMDs site was fine.
    • I have avoided many deer, a few moose, and other smaller animals during my years of driving and have managed just fine with only ABS and ESP, both of which can also be problematic depending on circumstance. I have never feared driving and I live in a rural area with a lot of deer and other animals. Winter or summer, heavy rain or sunshine, night or day, I always prefer and like to drive myself, and I drive constantly in my job. People die in accidents and they always will, that is a fact of life. Something like self-driving busses I can advocate for because they can be set to drive on static routes that always stay the same - i.e. those routes can be specially designed and maintained for them. I've already seen enough idiots doing random idiotic things with their Tesla autodrives that I would rather see them crash and burn because of their own stupidity instead of their "computer failing". I've also been a PC and tech enthusiast of over 25 years so I I'm fine with tech but I want to be the one who uses it, and decides how much of it I use. I also do not want it to make my hands, feet and brain obsolete. For me it's not really about if a computer can do it but about people not having to do things themselves (responsibly). I think that basic driving education should be done with a manual car and these "automatic only" cards should not exist (yes, I'm European and we drive a lot of manual cars, I even prefer them). If a person doesn't have enough coordination to manage a steering wheel, shitfer and pedals, how on Earth are they able to react to any unforseen situation on the road? And giving them autodrive doesn't make me feel any better if the person behind the wheel can't manage even basic driving themselves. One of the things I hate most in today's society (in general) is how pretty much everything that is considered even a bit dangerous is eliminated instead of educating people to assess risks and avoid problems themselves. Instead we make brains obsolete by building systems that do everything for us.
  • Recent Achievements

    • One Month Later
      KynanSEIT earned a badge
      One Month Later
    • One Month Later
      gowtham07 earned a badge
      One Month Later
    • Collaborator
      lethalman went up a rank
      Collaborator
    • Week One Done
      Wayne Robinson earned a badge
      Week One Done
    • One Month Later
      Karan Khanna earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      674
    2. 2
      ATLien_0
      274
    3. 3
      Michael Scrip
      219
    4. 4
      +FloatingFatMan
      170
    5. 5
      Steven P.
      161
  • Tell a friend

    Love Neowin? Tell a friend!