My home network is being stupid (computer file sharing)

[Mr. Ingram's Computer Repair & Shoppe]

I am re-doing some cabling (because thumbtacked to the wall "isn't a solution").... so while I was re-cabling, I decided to switch up some hardware.

I am troubleshooting two computers. "dad" and "sexy" here is an IPCONFIG screenshot of the two:


The setup is stupid simple.
ATT Router has "dad" wired straight in and a "dumb" switch straight in.
The "dumb" switch has "sexy" straight in.

both computers are up-to-date Win10 1803

I want to share a folder on "sexy" so "dad" can view it.

 

[sapphirescales]

I don't understand the problem. Can't you just use a Workgroup (or even a Homegroup)? So long as file sharing is set up on both of them and they both have passwords, you should be able to share files between them quite easily.

 

[River Valley Computer]

I have been on vacation for two weeks but it seems like I read somewhere Update 1803 eliminated Homegroups, etc. or did I have too many Coronas?

 

[Mr. Ingram's Computer Repair & Shoppe]

Can't you just use a Workgroup (or even a Homegroup)?

This V

I read somewhere Update 1803 eliminated Homegroups, etc.

I thought the same thing, didn't even bother looking...

 

[fincoder]

Fix Network Computers are Not Visible in Windows 10 Version 1803
https://winaero.com/blog/network-computers-not-visible-windows-10-version-1803/

 

[Mr. Ingram's Computer Repair & Shoppe]

Fix Network Computers are Not Visible in Windows 10 Version 1803
https://winaero.com/blog/network-computers-not-visible-windows-10-version-1803/

Awesome! we are a step closer! I can see "sexy" now. but I get this error:

(had to click on a different computer, as I am logged into "sexy" ATM) same error though

 

[Porthos]

I have been on vacation for two weeks but it seems like I read somewhere Update 1803 eliminated Homegroups, etc. or did I have too many Coronas?

You are correct, Homegroups are gone.

 

[YeOldeStonecat]

So you have network exploring (name resolution) working, based on your reply above that you "can see" the other computer. However you now have a permissions issue. I always go back to the old fashioned file/folder sharing we did back going back to the WinNT 4 days. Since Win7...gotta go into advanced sharing settings and lower those. Do the permissions on the Share part wide open, and same for the Security tab (NTFS permissions)..just to get it working and then dial it back to users. I also added local users that matched the user/pass used on the other computer.

 

[Moltuae]

I want to share a folder on "sexy" so "dad" can view it.

I never rely on Windows network discovery/visibility or homegroups. I've always done it the old way ... much more reliable.

Here's what I would do ...

Add a local (password protected) Windows account for "dad" on the "sexy" computer.

Set both the sharing and NTFS security permissions on the folder, making sure that user 'dad' has read/write access.

Preferably I would give the 'sexy' computer a static IP to refer to it by, otherwise you could use the computer name, eg:

\\192.168.1.202\SharedFolder

Or

\\ComputerName\SharedFolder​

Personally I would run Net Use from the command line and map it to a network drive, eg:

net use S: \\192.168.1.202\SharedFolder /user:ComputerName\UserName UserPassword /persistent: yes

Replacing SharedFolder, ComputerName, UserName and UserPassword of course (ComputerName should be the name of the 'sexy' or 'sharing' computer).

You could also replace the IP address here with the computer name if you prefer but if the computer has a static IP address, I would use that instead.

I would generally have a script reconnect the network drive at startup too for greater reliability. Windows doesn't always reconnect drives, despite the 'persistent: yes' argument.

I usually have something like this run at login:

@echo off

:: Wait for the LAN connection to be established
:checknet
Ping GatewayIP -n 1 -w 1000 >nul
if errorlevel 1 ( goto :checknet )

:: Delete exisiting network connections
net use S: /delete

:: Remount network folders
net use S: \\192.168.1.202\SharedFolder /user:ComputerName\UserName UserPassword /persistent: no

Replace GatewayIP with the IP of your gateway/router.





(Edited to add the missing '/delete')

 

[timeshifter]

I have been on vacation for two weeks but it seems like I read somewhere Update 1803 eliminated Homegroups, etc. or did I have too many Cortanas?

Admit it. I'm not the only one who read it that way.

 

[Mr. Ingram's Computer Repair & Shoppe]

just had a business customer call me. He is now having the same problem because his computer just updated to 1803 and now 1 can't connect. same problem I have... because you know, I had set both up using HomeGroups -.-

 

[Diggs]

Although Homegroups are gone, the semi-annual updates always change the sharing settings. You'd think it's be easy enough to read the current setting and maintain it.

 

[Cambridge PC Support]

Had something similar and it was because the machine was set to Public instead of Private. Changed it but it kept switching back, there was a box ticked somewhere (sorry can't remember where) that was pulling the setting from the MS account. Unticked that and it stayed on Private.

 

[Mr. Ingram's Computer Repair & Shoppe]

Had something similar and it was because the machine was set to Public instead of Private. Changed it but it kept switching back, there was a box ticked somewhere (sorry can't remember where) that was pulling the setting from the MS account. Unticked that and it stayed on Private.

Mine stay on private, and I only use Local accounts.

 

[AtlCPU]

Thanks for all your help! I was finally able to get it connected up using a combination of your suggestions.