Forum Home
Press F1
 
Thread ID: 147425 2018-12-12 09:25:00 Win10 Home Network bk T (215) Press F1
Post ID Timestamp Content User
1456474 2018-12-12 09:25:00 My home network sharing was working OK before, until I had to 'repair' my PC as Win10 couldn't start up properly. I didn't do any file sharing after that so, wasn't aware of any problem.

As mentioned in my other thread, I got a used laptop and installed Win10 Pro on it. They all work well.

Earlier this afternoon, I tried to set up the network sharing for my home network, they just not working correctly, it's driving me crazy:

Here is my network setup: HPlaptop MainPC PC2

Laptop and PC2 could access all machines just fine - no issues.

But,
1, MainPC couldn't access Laptop with error: " Windows cannot access \\HPlaptop Check the spelling of the the name, Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose."
Of course, clicked Diagnose produced no positive results.
2. MainPC totally couldn't see PC2.

It's driving me crazy.
bk T (215)
1456475 2018-12-12 09:58:00 Are they all in the same Homegroup/work group?
Is Home Group enabled?
Are you using DHCP addressing or static IPs?
Do you have Network discovery enabled on all machines?
Do you have file and printer sharing enabled on all machines?
Can you see the shares on each of the machines?
What versions of Windows 10 are you using.... the build number? Homegroups have been removed from 1803 onwards see here (support.microsoft.com)
chiefnz (545)
1456476 2018-12-12 11:44:00 Yup, That's what screwed folder sharing up 1803 or 1809 of Win10

Some sites say you have to put the UPNP device Host, SSDP Discovery, Function Discovery Provider Host, and Function Discovery Resource Publication service on automatic

It did work here, but now it doesn't. Altho, I think the main prob here is this useless Vodafone Ultra hub. The 5 ghz connection is stuffed. It keeps disconnecting. But 2.4 ghz works

The only way to get anything to connect to it, I have to turn this modem off then it decides to work again
Speedy Gonzales (78)
1456477 2018-12-12 13:18:00 Actually scratch that. I didnt know the fw on the modem was out of date. Even tho Vodafone say they update these ultra hubs automatically, they didnt update this.

So hopefully the 5 ghz connection stays put. And folder sharing (at the mo anyway) decided to work. It'll probably stop working later today
Speedy Gonzales (78)
1456478 2018-12-12 18:15:00 Are they all in the same Homegroup/work group?
Is Home Group enabled?
Are you using DHCP addressing or static IPs?
Do you have Network discovery enabled on all machines?
Do you have file and printer sharing enabled on all machines?
Can you see the shares on each of the machines?
What versions of Windows 10 are you using.... the build number? Homegroups have been removed from 1803 onwards see here (support.microsoft.com)


Yes. -- they are all in the same work group, created my own workgroup called : FERN , they all have different computer names.
All using DHCP may try static IPs later.
Network discovery enabled on all machines
File and printer sharing enabled on all machines -- have compared advance network sharing settings side-by side. 2 machines work perfectly OK, could see and access all the 3 machines without any issues.
They all on Windows ver 1809 (OS Build 17763.194)
The two happily working machines have no password to log in to Windows; whereas, the problematic machines needs a password to log in to Windows.
bk T (215)
1456479 2018-12-12 20:06:00 Windows networking has never worked 100% for me and I long since gave up on it in frustration. Annoyingly enough Linux works better with it than windows does.
I solved my issues by getting a NAS device and sharing it with everything, that seems to work even if not all machines always see each other. Of course the NAS doesn't run windows.

One thing that helps a lot but doesn't suit everyone is to set the same username and password on every machine, in theory you don't need to though.
dugimodo (138)
1456480 2018-12-12 21:07:00 try ip adress rather than PC Name \\192.168.x.x
try \\192.168.x.x\foldername

Disable homegroup services (where applicable)
The sharing on that PC may be completely screwed up : make another shared folder as a test
Turn off pass protected sharing
Turn on network discovery
Change the shared folder share permissions , both at folder and NTFS level(security in folder properties) : add everyone & guest

less likely but have a look at....
support.microsoft.com

Worst case: 'net use' to add mapped drive with share logon/pass
1101 (13337)
1456481 2018-12-12 21:18:00 Don't have time to write out a long possible fix at the moment Off to do exactly the same fix on a business Laptop. ( late already)

Sometimes the TCP/IP stack get in a twist.

What you can do is in the search, type in Network Reset, hit Reset Now, it will Kill the Connection Completely, reboot, on reboot it will rebuild a new network Stack, wait for the window to pop out on the right, click YES to allow access / Sharing etc. If Its wireless you'll need to renter your Details again.
wainuitech (129)
1456482 2018-12-12 21:57:00 Trying to assign a static IP address, but Win10 won't allow me to manually input the ip address. ???? bk T (215)
1456483 2018-12-12 22:50:00 Trying to assign a static IP address, but Win10 won't allow me to manually input the ip address. ????

??
is there an error message it spits out, or you cant enter any numbers

are you doing it through the old school , control panel, networking.....
untick IPv6 .

The user you are logged in as might need to have local admin rights.

Another thought, have you got any 3rd party AV or firewall installed ?
Try disabling the Firewall
Also make sure the network connection shows as "work network" (not public)
1101 (13337)
1 2