1803 File Sharing

I have two nearly identical PCs both running Windows 10. Both were
updated from 1709 to 1803 about a week ago. All went well with the
update except neither machine was able to share files with the other.
After googling the problem, I saw many were having the same issue.
I found people who had solved the issue by starting the "Function
Discovery Resource Publication" service. That solved part of my
problem. The two PCs can now see each other, but they still can't
access any files on each other. I tried installing the SMB feature in
Windows, but nothing changed. (I didn't expect it to since it was
proposed as a way to talk to Win 7 machines.) I stumbled across using
"RUN" to access files on the other machine. Typing "\\PC-B\MyDir"
into the run window on PC-A works. I get the directory and can access
the files. If I leave that window open, I can then use file explorer
to access the files on PC-B. However, if I try File Explorer without
having first used RUN, then I get error 0x80070035 (Network Path Not
Found). I could almost live with that except PC-B never sees the
files on PC-A no matter what I try. I always get the 0x80070035 error
regardless of whether I am using RUN or file explorer. My intent is
that PC-A and PC-B be configured identically so I can't see why typing
"\\PC-x\MyDir" works in one direction but not the other. The only
intentional difference between PC-A's and PC-B's configuration is IIS
is running on PC-A but not PC-B. But, I don't see that as having
anything to do with file sharing.

Any ideas for what to try next? I feel like I am missing something
simple.
Thanks,
Pat

On 09/05/2018 5.02 pm, Pat wrote:
I have two nearly identical PCs both running Windows 10. Both were
updated from 1709 to 1803 about a week ago. All went well with the
update except neither machine was able to share files with the other.
After googling the problem, I saw many were having the same issue.
I found people who had solved the issue by starting the "Function
Discovery Resource Publication" service. That solved part of my
problem. The two PCs can now see each other, but they still can't
access any files on each other.

I too had to set that service to "Automatic - delayed start" on my
Windows 10 machine as the Windows 7 machine could no longer see it. Is
that what you set it to? I understand that just "automatic" doesn't work
correctly - I'm not sure why it needs the delay. You did do it on *both*
machines? I'm told you need to do it on every machine that runs 1803. If
you haven't that may explain why you seem to have one way traffic.

However, I also lost some of my share settings/permissions - it may be
worth going back over your shares and checking them and also checking in
the settings menu that you still have "Network and Sharing Centre
Change Advanced Sharing settings" set as you would like it. I'm not very
technical - but I am guessing there may be a connection with 1803 doing
away with Homegroups.

Regards,
Bob

--
Tetbury, Gloucestershire, England

The penalty for bigamy is two Mothers-in-Law.

On Wed, 9 May 2018 19:32:10 +0100, Bob Henson
wrote:

On 09/05/2018 5.02 pm, Pat wrote:
I have two nearly identical PCs both running Windows 10. Both were
updated from 1709 to 1803 about a week ago. All went well with the
update except neither machine was able to share files with the other.
After googling the problem, I saw many were having the same issue.
I found people who had solved the issue by starting the "Function
Discovery Resource Publication" service. That solved part of my
problem. The two PCs can now see each other, but they still can't
access any files on each other.

I too had to set that service to "Automatic - delayed start" on my
Windows 10 machine as the Windows 7 machine could no longer see it. Is
that what you set it to? I understand that just "automatic" doesn't work
correctly - I'm not sure why it needs the delay. You did do it on *both*
machines? I'm told you need to do it on every machine that runs 1803. If
you haven't that may explain why you seem to have one way traffic.

However, I also lost some of my share settings/permissions - it may be
worth going back over your shares and checking them and also checking in
the settings menu that you still have "Network and Sharing Centre
Change Advanced Sharing settings" set as you would like it. I'm not very
technical - but I am guessing there may be a connection with 1803 doing
away with Homegroups.

Regards,
Bob

Bob,
Thanks for the reply. I will give delayed start a try. Regarding
your other questions, yes, I used these same settings on both PCs.
They are the only Windows machines I have. All the other devices on
my network are things like iPhone, iPads, security cameras, a printer,
and other Iot devices. Regarding sharing setting, I agree the problem
could be there, but I have looked at all those settings over and over
and can't see anything wrong.

Thanks,
Pat

On Wed, 9 May 2018 19:32:10 +0100, Bob Henson
wrote:

On 09/05/2018 5.02 pm, Pat wrote:
I have two nearly identical PCs both running Windows 10. Both were
updated from 1709 to 1803 about a week ago. All went well with the
update except neither machine was able to share files with the other.
After googling the problem, I saw many were having the same issue.
I found people who had solved the issue by starting the "Function
Discovery Resource Publication" service. That solved part of my
problem. The two PCs can now see each other, but they still can't
access any files on each other.

I too had to set that service to "Automatic - delayed start" on my
Windows 10 machine as the Windows 7 machine could no longer see it. Is
that what you set it to? I understand that just "automatic" doesn't work
correctly - I'm not sure why it needs the delay. You did do it on *both*
machines? I'm told you need to do it on every machine that runs 1803. If
you haven't that may explain why you seem to have one way traffic.

However, I also lost some of my share settings/permissions - it may be
worth going back over your shares and checking them and also checking in
the settings menu that you still have "Network and Sharing Centre
Change Advanced Sharing settings" set as you would like it. I'm not very
technical - but I am guessing there may be a connection with 1803 doing
away with Homegroups.

Regards,
Bob

Hello again,
I got a chance to try delayed start on the FDRP service. No change
in symptoms. I looked at all the sharing options I could find both
for the entire PC as well as the specific folders I am try to access.
Still no change.

To repeat the symptoms for any new readers: I have two PCs running
Win 10 Pro 1803. After the update from 1709 to 1803, neither PC was
visible from the other. (All worked well before the upgrade). After
starting the Function Discovery Resource Publication service on both
machines, they now see each other, but I still can't access the shared
directories on the opposite PC. The error code is 0x80070035. The
one exception to this is that PC-A can access the shared directories
on PC-B if I type "\\PC-B\MyDir" into the run command window on PC-A.
However, PC-B can never access the shared folders on PC-A no matter
what I try. All ideas welcome.

Thanks,
Pat

Pat wrote in
:

Hello again,
I got a chance to try delayed start on the FDRP service. No change
in symptoms. I looked at all the sharing options I could find both
for the entire PC as well as the specific folders I am try to access.
Still no change.

To repeat the symptoms for any new readers: I have two PCs running
Win 10 Pro 1803. After the update from 1709 to 1803, neither PC was
visible from the other. (All worked well before the upgrade). After
starting the Function Discovery Resource Publication service on both
machines, they now see each other, but I still can't access the shared
directories on the opposite PC. The error code is 0x80070035. The
one exception to this is that PC-A can access the shared directories
on PC-B if I type "\\PC-B\MyDir" into the run command window on PC-A.
However, PC-B can never access the shared folders on PC-A no matter
what I try. All ideas welcome.

Thanks,
Pat


Have you tried breaking the share and then recreating it. sometimes there
are bits and byte laying around that cause problems, and recreating the
share makes them go away.
Remember that 1803 made the Homegroup go away. I don't think that should
bother shares, but one never knows.

On Sat, 12 May 2018 05:23:54 GMT, Tim wrote:

Pat wrote in
:

Hello again,
I got a chance to try delayed start on the FDRP service. No change
in symptoms. I looked at all the sharing options I could find both
for the entire PC as well as the specific folders I am try to access.
Still no change.

To repeat the symptoms for any new readers: I have two PCs running
Win 10 Pro 1803. After the update from 1709 to 1803, neither PC was
visible from the other. (All worked well before the upgrade). After
starting the Function Discovery Resource Publication service on both
machines, they now see each other, but I still can't access the shared
directories on the opposite PC. The error code is 0x80070035. The
one exception to this is that PC-A can access the shared directories
on PC-B if I type "\\PC-B\MyDir" into the run command window on PC-A.
However, PC-B can never access the shared folders on PC-A no matter
what I try. All ideas welcome.

Thanks,
Pat


Have you tried breaking the share and then recreating it. sometimes there
are bits and byte laying around that cause problems, and recreating the
share makes them go away.
Remember that 1803 made the Homegroup go away. I don't think that should
bother shares, but one never knows.

I just had time to try try your suggestion but it still doesn't work.
I also found the workgroup name set to different values on the two
machines. I fixed that but still have the same symptoms mentioned
above. Arrrrrrgh!