Accessing default shares

Page 3 of 3 FirstFirst 123

  1. Posts : 107
    Windows 10 Pro
    Thread Starter
       #21

    Well, I did find a solution that worked for me as described earlier in this thread but guess you already tried that to no avail since you're asking?
      My Computer


  2. Posts : 2
    win10
       #22

    WebMaximus said:
    Well, I did find a solution that worked for me as described earlier in this thread but guess you already tried that to no avail since you're asking?
    Did not work. That solution is for a Win10 machine that you are trying to connect TO, not connect FROM. If I connect from Win7 to Win10, it works (admin shares), if i try from Win10 to Win7, it doesn't work.

    If it's win7 to win7, again, works just fine.
      My Computer


  3. Posts : 107
    Windows 10 Pro
    Thread Starter
       #23

    teredactle said:
    Did not work. That solution is for a Win10 machine that you are trying to connect TO, not connect FROM. If I connect from Win7 to Win10, it works (admin shares), if i try from Win10 to Win7, it doesn't work.

    If it's win7 to win7, again, works just fine.
    Ah, sorry...didn't read close enough.
      My Computer


  4. Posts : 1
    win98se win7 win10
       #24

    I'm not looking forward to the hardware challenges that are probably going to hit me in the near future:

    I'm upgrading the old WRT54 that I've probably had for 20 years, replacing it with a dual WRT1900ac system in Master/Bridge mode, to insure best operating speed for both Wifi and streaming video around the house.

    Oh, left out a little detail - The machines I'm attaching are a Win10, Win7-SP1, WinXP-SP3, Win95 and Win98se. The XP and 95 machines are laptops (Dell D820 w/XP, Toshiba XT Portable w/ISA slot w/95).

    The Win10 is not here and online yet. All of the other above machines are peacefully coexisting on the network. I actually spent tonight putting in a Gigabit/100/10 card and a Belkin USB2.0/4port USB card in the Win98se machine in order to backup trade/audio tracks recorded in the studio using the 98se machine in DOS mode w/proprietary software that requires two ISA slots for studio interface.

    At this point I can transfer files willy-nilly among all of the machines, and the music studio is a dream to work with.

    So the idea of getting that "FREE" copy of Win10 for my current project (Win8 machine) and pushing it to the network is a bit scary. I'm hoping to downgrade the Win10 networking to a NetBEUI or pure IP machine client.

    Thanks to you guys for the posts and the information. I'm writing copious notes to hopefully head off the future "elephant in the room."

    Rick
      My Computer


  5. Posts : 1
    Win7, Win8, Win10, Linux, Nutxx
       #25

    Using RDP instead!?


    Well I guess that Redmond screwed us a bit here. I was looking for the same issue all the web-round with no clear solution. But I got this workaround that might help others. RDP!! As long your "controlled" PC has a WIn10 Pro. Your "controlling" PC might be a Win 10 Home. Do not forget to enable remote access on the controlled PC and do not forget to check local resources. Drives in this case particularly. That's it. I know, I know, it's not what was asked in the first place, but might be a workaround for someone.

    Cheers, D.
    Attached Thumbnails Attached Thumbnails Accessing default shares-2016_02_24_23_27_371.png  
      My Computer


  6. Posts : 2
    Windows 10
       #26

    WebMaximus said:
    I have two Windows 10 PCs on the same home network and I can't access the default shares on either one of them, I keep getting 'Access denied'.

    Any ideas?
    You can try this... A small registry hack is all it takes to get around the issue by creating a policy manually that overrides the default setting. Do this on the server that has the shares you want to access remotely:


    1. Click the Windows Start icon and search for “regedit”. Right-click and select “run as administrator”.
    2. Expand the tree to HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft\ Windows \ CurrentVersion \ policies \ system.
    3. Create a new key (Right click -> New -> choose “DWORD Value (32bit)”).
    4. Name the key LocalAccountTokenFilterPolicy and give it the value of “1”. Click OK. (refer below pic)
    5. Reboot the server to enable the setting to take effect.
    6. Now when you try to access the administrative shares on the remote computer, it should magically work.


    Pl reply if it works for you.
      My Computer


  7. Posts : 330
    Windows 10 Pro
       #27

    jimbo45 said:
    Hi there

    this doesn't always work -- I've had problems even with firewall totally disabled. Sometimes W10 computers can see other computers in the network, sometimes they can't --seems to be unpredictable and even when you have 2 seemingly identical machines one works fine and one doesn't.

    Never had this problem on W7 or XP. Networking though IMO is still a TOTAL HOSEUP on any Windows system. If it works - breathe a sigh of relief --if it doesn't you can try 2,000 zillion different things and it sometimes STILL doesn't work. It's a total crap shoot IMHO.

    Cheers
    jimbo
    jimbo i totally agree with you.
    I have tried zillions of fixes but none has worked for me yet. The anniversary update done something to my computer that broke the communication and MS will not admit it.
    I just have to wait patiently until a fix works

    cheers
      My Computer


  8. Posts : 1
    Windows 10
       #28

    Ok, sunday morning - just took some time to figure this out for myself, as I had the same problem. Since I switched to 2x Win10 machines (let's call them "A" and "B"), I can't access the default share on A from B anymore... Note that currently I dont have on both machines the same account (name & password), but both accounts have admin rights. When I try to access the default share on A from B like "\\A\c$", the popupbox shows up where I have to provide my account from machine A. As discussed here, I also had the "Access denied" problem... So (as already discussed here too) I tryed editing the registry and adding "LocalAccountTokenFilterPolicy" to HKLM... But actually on my machine B that entry was already there... on another forum somebody wrote, that on 64bit machines it should be QWORD instead DWORD (tryed that too, but didn't help). I just found the solution on this Website: "https://tommynation.com/enable-remote-access-administrative-shares-windows-10/" and now it's clear why this thread here never got closed: I had to add that registry key on Machine A (and NOT on machine B)! While on machine B that key was already there, interestingly on machine A it wasnt... However, I just added "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system\LocalAccountTokenFilte rPolicy" DWORD Value 1 on machine A (even A is a Windows 10 64bit machine, I did add DWORD and not QWORD) and after that rebootet A. Et voila - I can now access the default share on A from B.

    Cheers,
    Alen
    Last edited by Supertramp1973; 27 Nov 2016 at 03:32.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 17:32.
Find Us




Windows 10 Forums