Subj : Network Notwork To : Ky Moffet From : Barry Martin Date : Sun Oct 06 2019 07:11:00 Hi Ky! > KM> So I have this collection of random PCs on a Windows workgroup. > KM> Objective: share the root of the drive. > KM> WinXP -- no problem, can share the root of a drive, and > KM> everything on it is accessable (except the Windows directory > KM> itself). XP64 -- no problem, ditto. > KM> Win7Pro and Win10somerandomrelease -- go through the motions but > KM> nothing happens, even when I'm using the hidden admin account. I > KM> can share a directory, but not the root (of any drive, not just > KM> the boot drive). Root shows as shared, but variously swears at > KM> intruders and won't let them see anything, or asks for login > KM> credentials, which don't exist. (The homegroup password that it > KM> concocted does not work. Besides, this is not using the > KM> Homegroup.) The XP boxen firmly believe there is a share named > KM> "C" (which should be C root) but that gets a big Keep Out. > KM> However they can see /Users/Public. > You've probably seen these in your Googling but: KM> Nope, but... been there, done that, have both Administrator and KM> Everyone set to Every Damn Thing, altered the registry, and no KM> joy. Removed the bogus C share and tried again, still no joy. KM> Ditto from the other admin account. Grrrrrrr....... KM> In fact when I went to remove the share and try again, it whined KM> at me that there was still a user connected to it, so it knows KM> it's seen, it just won't share the contents! "Access denied" bah KM> humbug to you too! Perhaps a Blacklist and/or Whitelist? And maybe thinking backwards: blacklist no one and whitelist everyone. ...I have nothing specific in mind, juist trying to thing of a workaround to trick the system. > Two not-so-intuitive items in there: > (1) Each pcs connection needs to be set to private not public. KM> And where in the hell is this?? Don't you love it when the instructions give only part of the instruction?! KM> I certainly don't want to mung up the other machines, which are KM> perfectly happy to keep all their files in a shared basket. No, would not be good to make things worse. Perhaps consider this 'shared basket' as the remote computer and share with this one rather than the individual computers? > And here's something from the last post: > I think it started with Vista - even if you are an administrator you > connect with standard user credentials. By default the root of > drives grants administrators group full access and users only read. KM> Yeah, that's when it started driving me mad, all right. Only KM> messed with Vista briefly but lack of normal network access was KM> the first Bad Thing I noticed. Wasn't such a pleasant view after all! (Pun on 'Vista'.) > You can change this (and so bypass UAC by connecting using > administrators group authority) by setting > LocalAccountTokenFilterPolicy registry key to "1" as described here > > https://support.microsoft.com/en-us/help/951016/description-of-user- > account-control-and-remote-restrictions-in-windows KM> Nope, didn't help. Further, somewhere along the way WinExplorer KM> lost the ability to see/remember the other PCs -- so now I have KM> to either type in the name or use a shortcut. So it's not caching KM> network names anymore. Effing Win7/8/10/forever... As things go from bad to worse..... > Hope something up there is somewhat useful for you! KM> So did I! Ah well, thanks for trying!! And I've been out of Windows so long I'm just remembering the basics. > BTW, with Ubuntu 18.04 I had found for some of the mounts to hardware > using older version of SAMBA I needed to add ",vers=1.00" prior to > the 0 0 at the very end of the line in fstab. (Didn't need in 16.04.) KM> Now that I have no idea what you're talking about... Was an attempt to say what worked in one version may need a helper in the new. The new way to add remote drives/computers wasn't fully compatible with the old way because of security. I included that bit of trivia for you in case Windows also was doing that. KM> The Winders PCs see the PCLOS/KDE box as "Samba-PC" but it won't KM> let them connect. And lately (I think this happened when I KM> installed Timeshift, come to think of it -- this box has KM> otherwise been frozen for almost a year, cuz of kernel and NVidia KM> conflicts I don't want to deal with) it can't see them either. Hmmm: about a year or so ago there was a problem with the computer we have by the kitchen table: an update was not compatible with the nVidia XServer utility; IIRC just looped the boot process. Temporary fix was to get into the Boot Loader and use select the previous kernel. The issue was fixed about a week later. The newsgroups were _really_ active for a few days! ¯ ® ¯ Barry_Martin_3@ ® ¯ @Q.COM ® ¯ ® .... What you don't know can't hurt you - but can make you look like idiot. --- MultiMail/Win32 v0.47 þ wcECHO 4.2 ÷ ILink: The Safe BBS þ Bettendorf, IA --- QScan/PCB v1.20a / 01-0462 * Origin: ILink: CFBBS | cfbbs.no-ip.com | 856-933-7096 (454:1/1) .