Networking :: Workgroup Shares Windows ID Versus Local Accounts
Nov 10, 2015
I have so far avoided using Windows ID login (except on a sacrificial VM I use for Windows Insider(*)) as I can no longer access the SMB shares that I have set up.
Is there any way for the two to co-exist? I can't get my head round using SMB shares and NTFS permissions with Windows Live ID - is it possible in any way at all, or have MS (as usual) given us a "new spiffy improved thing" which is actually none of the above?
Why can't I use a local login AND have have access to the Insider programme?
Using a LOCAL account I have no problem with Shares -- how do I set these now using an Ms account.
Samba just times out trying to access Windows machine where I'm logged on with an Ms account. Also I can't access other Windows machines from the Ms account. The other Windows machines can't access the Windows machine where I'm logged on with an Ms account.
All these problems DISAPPEAR when using a LOCAL account.
I think my future strategy will be just keep a MINIMAL Windows VM with an Ms account to GET the insider builds and then revert back to Local accounts.
I just switched to a new router (from DLink DIR-655 to TP-Link Archer C7) and now my Windows 10 Pro cannot see network shares nor can others on the network see its shares. Prior to the router switch, it could see shares and others could see the shares it exposed.
The Win10Pro can see the internet. I can still ping other computers and they can ping the Win10Pro, just no Windows sharing. All computers are in the same Workgroup. I am not using a Homegroup; computer connections are made with user accounts.
The Windows 10 Pro is connected via wire. When I made the switch, I remember that Win10 came up and told me it had a new network and prompted whether to allow network discovery - to which I said yes. I thought that odd at the time since changing the router didn't change the NIC connection from the Win10 -- but whatever. However, it did change the IP address on the Win10Pro from what it was. But I've since rebooted all computers (thinking that might cause them to refresh) but no improvement.
Advanced Sharing Settings are set as:
Private: Network Discover = ON, File and Printer Sharing = ONAll Networks: Password Protected Sharing = ON, Public Folder Sharing = ON
Surface Pro 4 - fully updated Surface Pro 3 - Windows 10, fully updated Lenovo X220T - Windows 8.1 Fully updated
All three machines can see all available network devices, including each other.All three machines can successfully access and interact with third party network devices. In this case, it is a NAS and a network printer.The windows 8.1 machine can access each of the other windows 10 machinesNeither Windows 10 machines can access any other windows share on the network.
This gets me error 80070035 with diagnostics telling me nothing
All three machines are on a Homegroup and while each can see, no one can access anything
Trouble shooting tried:
Double checked all sharing settings on all three computers. They are identical.Double checked workgroupsTried it via IP addressesReset winsock on all machinesFlushed DNS on all machinesReset the routerUninstalled and reinstalled Windows sharing and about 3 other network protocols and servicesEnabled NetBiosran this: sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi sc.exe config mrxsmb20 start= disabledMessing around with all sorts of netsh commands clearing and flushing all sorts of other things
I'm finding Windows 10 enjoyable and pleasant for the most part.
Unfortunately, some things that are easy to find or to do (probably due to years of experience) in Windows 7 and 8/8.1 are not easy to find, assuming they exist at all, in Windows 10 build 10130. For instance, I've looked high and low for "Change PC Settings" and it is like the proverbial needle in the haystack.
My present problem is that I can't see other computers in my network/workgroup. They are visible to my Windows 7 and 8.1 computers. My network is set to private in Windows 10. Find devices is set to on.
I note that I can ping all my devices, Squeezeboxes, WDMycloud hard disk, chromecast, computers etc., and the squeezeboxes, Logitech Media Server , WDMYcloud and Chromecast are showing up as devices.
Drive C: on a new win10 laptop is marked Shared for Everyone, read+write+control (because it will hold a webserver and database server that must be manageable from other workstations in the workgroup).
Yet win10 refuses access to a map-network-drive request from File Explorer run as administrator on any win7 machine in the same workgroup.
I have 3 pc's in my LAN Mark= Win7 32 bit Dave= Win10 32 bit HTPC = Win10 64 bit
I'm trying to share the files on HTPC and have created a workgroup.
Dave and Mark can share files Mark and HTPC can share files
But Dave who can connect to the win7 pc through the workgroup can't connect to HTPC. Error is Windows can't communicate with the device or resource (HTPC). The computer or service you are trying to reach might be temporarily unavailable. If the device or resource is nearby and you have access to it, make sure it is turned on and connected to the network.
Since the win7 pc can connect to the win10 HTPC why can't the win10 pc?
I have a workgroup on desktop and laptop both running windows 10 - it was functioning not long ago but recently stopped and i cant figure out why. i've pfoofed round so much trying to get it going again i've probably made it worse
I just want to access some files between computers and connect to printer attached to desktop
I can ping desktop from laptop but not reverse desktop to laptop - kaspersky is on both machines.
I tried setting up a homegroup but no luck there either - both machines can still access the internet thru netgear cgd24nv3.
After recent Windows 10 Update, my wireless connection no longer works. I've done some troubleshooting and I have ruled out my ISP, cable modem, and router, leaving the issue to be something within the computer (Dell laptop - Inspiron 7537).The wired connection works fineWhen I run Windows Network Diagnosis, it tells me that the Windows Wireless Service is not running (see attached pdf report).
When I try to manually start the WLANSVC service, i get an error message that says "Windows could not start the WLAN AutoConfig service on Local Computer Error 193:0xc1" (see attached)When I try to manually start the WLANSVC service from the command prompt (as Admin) I get a slightly different message that says "The WLAN AutoConfig service is starting. The WLAN AutoConfig service could not be started. A system error has occurred. System error 193 has occurred. *** is not a valid Win32 application." (see attached)I've downloaded the latest Intell PROset Wireless drivers from Dell (V22.214.171.124) for the Wireless-N 7260 wireless network adapter and have uninstalled and reinstalled the drivers.
We have a peer to peer network, with one Win 10 machine (acting as server - which we call server) which shares several hard drives for everyone in the office to access. It has network discovery on, file and printer sharing on, turn off password protected sharing off. It has all the drives named and shared properly so everyone has full access. All the other Win 7, and Win 8 machines have complete access as designed.
Another Win 10 machine has complete access as designed. All machines are part of the same workgroup Engineer. My machine is a Lenovo laptop which was upgraded from Win 8 to Win 10. When I try to access the Win 10 machine (which is acting as server), I get the Enter Network credentials pop-up asking for Username and Password which we do not use nor have ever set up on the Win 10 machine or any other. I know that there are several posts that have the Enter Network credentials popping up, but the difference is that their screenshot showed them as part of a workgroup.
See the following:
When I get the same pop-up on my Lenovo Laptop It looks like the following ....
My System Properties information ....
Notice that the example above which is part of the workgroup has no reference to a domain. My pop-up on the Laptop shows reference to a domain, and whats interesting is that the domain is the computer name of the laptop itself. There are no domains set up on any machine of our peer to peer network.
I was running Windows 7 on my laptop. I have a file server running Linux and Samba. When I open the Network icon in Windows 7, I see my server there and I can open it and access the associated folder shares.I upgraded to Windows 10. Now if I double click the network icon, I don't see any machines except my local client laptop. However, if I enter the UNC path to my samba server (myserver) into the path bar of Windows Explorer, I can access the server. If I want to add a network printer to my laptop that is shared by the server, it won't find the server in the search list. However, I can enter the literal UNC path to the printer and add it. So it has something to do with nmb I think? Not sure.
I have a networked Windows 10 Pro computer A with built-in 'Administrator' account disabled. However, it has a "normal" administrator account named 'Admin'.
I would like to access administrative share 'AC$' from another computer B in the network. Windows asks me for access credentials. I enter 'Admin' and the corresponding password. This results in "access denied" error.
Hence the question: What's preventing the access?
My guesses are
1. (Unlikely: ) Administrative shares are accessible to the built-in 'Administrator' only. 2. (More likely: ) Administrative shares are accessible to a designated set of users and there's a way to control it. My homemade 'Admin' is not on the list. 3. (Most likely: ) Network access to administrative shares is completely disabled by default in Windows 10, but can be enabled somehow.
I have a Freenas Server (based on FreeBSD Unix) connected to my network. I can't get it to show up in file explorer untill I type "//000.000.000.000" (it's IP address). When I try to drag a file to the window CIF shares (Permissions in Unix are Allow Guest Access and Recursively set sane default windows permissions on share) I get the error "You Need Permission to Perform this Action". Both of these features worked on Win 7 Pro before I did an upgrade to Win 10 Pro. I also did a fresh install of Win 10 Pro and it made no difference so I restored a Macrium image of the Win10 Pro Upgrade.
I have several usb-connected drives and several SATA drives on a Win7Pro-64 system just upgraded to Win10. The only account on the machine is a local administrator account. On each drive I have a shared folder.
Where before I could connect via SMB/Samba from non-Windows networked devices using the local account credentials, I can now only access the shares on SATA drives. Any share on a USB drive is inaccessible to, say, ES File Explorer or Astro on a Android Tablet (although the share name can be read).
I can still access all shares from another Windows 10 machine. All devices have the proper Workgroup.
Clearly there is some SMB policy change in Windows 10. I've seen one fix for network drives but it doesn't seem to apply here (and also doesn;t work). Also not working is anonymous login to shares with with Everyone access, which also used to work.
I've got 2 Western Digital Network drives hard wired on my network, a My Book World and an EX2.
Since upgrading to Windows 10 I've had intermittent problems viewing and setting network drives. I've read a lot of other posts and tried a number of things suggested without success.
The WD Discovery tool finds the Network drives, but the box to map network drive is greyed out. I can access the desktop control panel from my browser. If I try to add a network location the drives are not listed. If I try to add the drive letter WDMYCLOUDEX2Public the network path is not found?
I have another Windows 10 computer on the network which can access the drives without issue - so it must be a setting on my PC. Tried disabling my Kaspersky security - still not being seen? I suspect that this has been as a result of a windows upgrade?
Several PCs in my store.. some running W7 starter, some W10 Home pro.
A few days ago suddenly I could no longer access a folder on another W10 computer, where we tend to store a lot of important documents. The computer where the other folder is, runs also W10.
Shares are usually done vie HomeGroup - share with home group users.Other computers on the network have no problem accessing it. Furthermore, I can access it from another local account on my computer, but not from my main account (which is a MS account)..It asks for credentials, although I am a homegroup user.. nevertheless I enter the other computer's only username and password (admin ones) and it still does not let me in. Try my own MS user and pass - also "wrong".
Tried leaving and joining the Homegroup.
Tried restarting network related services and setting them on Automatic.
Tried homegroup troubleshooter - says probable problem is with network, so should run Network troubleshooter.
I do so and it shows error:This network troubleshooter shows error: resource (peer to peer grouping) is online, but not responding to connection attempts.
Following the latter and some google searches, I tried adding DisabledComponents" DWORD with "0"value in HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesTCPIP6Parameters But still NO-GO.
The last update triggered (13-01-2016) the loss of access to the start menu, many apps, as well the apps store and MS Edge. The exact same thing happened with the first version of Win 10 Pro received as an upgrade from WIN 7.
This time, as soon as build 1511 was received, I immediately created a ISO USB stick and then proceeded to use the machine as normal. At some stage, I created a Local Account with Administrator rights as I am the only user of the PC.
After the January upgrade, I can no longer switch back to the MS Account as the screen where one is supposed to be able to do this under [settings/accounts/Your email and accounts] does not load anymore, thus removing the option to switch back to a MS account. The screen is just blank.
I ended up activating the in-built Administrator account so that I could try and see what was going on.
I now notice under C:users the following user folders:
(1) Administrator (2) Default (3) Default.migrated (4) DefaultAppPool (5) My Name ---- I presume this is the user profile for my MS account? (6) My Name (Local ----- This is the created local Account
yet the "name of the account" when I log in has been truncated to My name L
Is this why the settings page for accounts cannot find the profile information which will allow me to switch back to my MS account?
I feel I have to unravel this mess before going any further in trying to establish why the start menu and all the apps have now "dissapeared"
Of course I can just redo the clean install but I feel I should first sort out the user profiles before going any further.
My computer crashed and when it rebooted, it required me to login with my Microsoft account. Now, this computer has had a local account since I got it 5 or 6 years ago. I have never used the Microsoft account on this computer.
Trying to switch back to the local user using guides on this site, that local account apparently doesn't exist anymore.
I'm obviously concerned that it deleted an account on its own. How do I get the account back? Creating a new one is easy enough, but are there any permission issues? I have enough of those between Windows 10, and the previous 7 installation.
I simply wanted to remove a long dead hotmail account from my user sign in account and update it with my current outlook email. Seems innocent enough. After much searching and finally finding out that you simply can't do this logical task, I found the 'magic formula' to achieve my goal. The problem is, Windows gives me an 0x80004005 error code after I complete filling out the information for the Local user, preventing it from being created. So it's not possible to switch to local, then switch back.
when i first got windows 10 i had a local account and used it as normal then for some reason i added my Microsoft account and now every-time i log in i need to use the Microsoft account, just now i tried to switch it to the local account and i got this error?
I have been using Windows 10 for last 2 months and i had no issues with update but few days ago i had a problem with opening applications . It says "App cannot open ,you're using inbuilt account sign in with Microsoft account " something like that so i googled about this problem and i have followed all steps but accidentally i deleted the local administrator and now I can't sign in into my pc , i know my password and pin code but it says "Your password was changed on a different device.You must sign in to this device once with your new password,and then you can sign in with your PIN " ...