Windows 10 can't find the Workgroup but says the drive is shared

This is a new question about my homenet: workgroup name HOMENET . Windows 10 said it could not find the path with the error code 0x80070035

a help page I looked at is here:
Error code: 0x80070035. The network path was not found. [Solved] - Driver Easy

gives some instructions-- quite a few -- and I wonder if there is some other shorter solution or if the drivereasy method will even work.

I inspected the Win 10 drive c: Properties and indeed it did say not shared. So I changed that
in the procedure. Win 10 now says that c: is recognized, I can open the run command and get the directory.

But the error persists that Windows 10 cannot find the path.

Then there is a step involving ipconfig and IPv4. I made the requested ipconfig /all as
requested and I have forgotten how to keep the result from running then winking off. For all these reasons I am starting over here. Is it /p to get it to pause? Nope not slash p

What does TenForum suggest to solve the problem of this simple path not found that previously
did not exist?

Full disclosure on this is I have run the Blackbird privacy suite. I do not know if that does
something to break my home network or if this is a separate issue.

Open a cmd prompt type

net share

by default all drives are shared as a hidden admin share starting with $ so you should see c$ you can connect to it by supplying a admin name/password

Progress.

[run box] type cmd /k ipconfig /all

gets the screen to stay open. IPconfig down at bottom says NetBIOS over TCP/IP Disabled.

More to do since giving the local IPv4 then \c still did not find the homenet.

drivereasy tutorial has steps below that as well. I'd have to print out the whole thing to follow it all.

More progress

I see that running the ipconfig /all on my main PC shows that the same NerBIOS command is
enabled.

Onward.

Samuria said:

Open a cmd prompt type

net share

by default all drives are shared as a hidden admin share starting with $ so you should see c$ you can connect to it by supplying a admin name/password

I have been making replies so will wait for things to catch up. I'll try net share a bit later.

ok one more today.

I used [run box] cmd /k net share.

The command shows ' completed successfully' but still the same error I started with persisits

Is this run on both machines? Restart necessary? any of that? As it is the command has not solved the
problem.

Eagle51 said:

Hey loninappleton,
On the PC where you're getting ... NetBIOS over TCP/IP Disabled ... check your adapter properties.
1. Open Control > Network & Sharing > Change Adapter Settings
2. Right Click on your Active Adapter > Properties
3. In the Properties popup box > Click on the Internet Protocol Version 4 (TCP/IPv4) > Click Properties > Advanced
4. Go to the WINS Tab and make sure Enable LMHOST Lookup is checked and NetBIOS Settings that Default is Selected

Ok. I think this is also contained in the other tutorial down the list.

But my last thing of the day is on Blackbird since that is part of this build. Where it says in the Blackbird FAQ to Use 'L" to fix network problems, I did. It said completed but that did not solved anything. This is not a discussion of Blackbird proper but I think it is a good tool. It just locked me out of my own workgroup. :-/ I am always the goat.