Windows Ten having a problem accessing the Workgroup

PeterFragon said:

Make sure the "server" service, unpnp and ssdp discovery are all running.
can you get to any of the other hosts via UNC? start/run \\servername\sharename\ ?
Nethood often does not show the other machines in WIN10s latest updates but typically the UNC paths will still function.
also make sure you have a user with the exact same name and credentials on each host, a local user is best.

EDIT:

You can also try resetting the IP stacks

?

In ipconfig?

This sounds like I'm at Defcon25 (which I listen to some on youtube.) wink

The scratch install of WIN10 I have on should have all services going but I'll check that.
I put the OS on a freshly zeroed low level 320Gb old timer I'm using for practice.

I'm no expert on network install or credentialling.
Does the credentialing need to be done at install time or in the Admin functions?


netsh winsock reset catalog
netsh int ipv4 reset reset.log
netsh int ipv6 reset reset.log

The commands above I'm not familiar with.

I'll need to take things slowly. And I may forget things and have to come back to them.
A list of steps would be helpful.

Things done tonight. Services are all on or on default from the scratch install.

I found the Manage Credential screen but do not know how to proceed. With my two PC's on the Workgroup,
I never had to engage any of these commands before.

Thanks for the clarification.

At the CMD what is the exact code to enter and for the following commands you show?

Why does Win10 require the extra steps-- or is it because I made an error in Setup?

I'm asking because I don't know if I have to make a personal guide to
get through this another time.

So far MSI-WIN10 can see the Public folder on the one I call MSI_HD. But in MSI_HD, the error
which I encountered earlier is reversed and displays.

Perhaps I am getting ahead of making the commands. Thanks for your patience.

PeterFragon said:

Those commands rebuild/reset your IP stacks or in other words the TCP/IP drivers running on the NIC.
You just run the winsock reset in an admin command prompt then reboot, nothing to it..

The manage credential dialog allows you to change or remove any passwords windows has saved for you, such as your outlook email account creds and other apps that required a log in..

Here is the code for Winsock Reset

https://iihelp.iinet.net.au/Resettin...(Winsock_Reset)

netsh winsock reset

Was not sure if the added quotes in the piece were needed.

PeterFragon said:

Make sure the "server" service, unpnp and ssdp discovery are all running.
can you get to any of the other hosts via UNC? start/run \\servername\sharename\ ?
Nethood often does not show the other machines in WIN10s latest updates but typically the UNC paths will still function.
also make sure you have a user with the exact same name and credentials on each host, a local user is best.

EDIT:

You can also try resetting the IP stacks

[FONT="]netsh winsock reset catalog[/FONT]
[FONT="]netsh int ipv4 reset reset.log[/FONT]
netsh int ipv6 reset reset.log

Still working on this.

The story so far is Win10 sees MSI-HD machine and opens it's shared folder.

I ran just the first of the netsh commands on MSI-WIN10.

Should I be running that on MSI_HD?

MSI-HD continues to give the error in the screenshot. I'll continue with completing the commands on both ends.
The other things discussed I'll have to backtrack on.

From Post 11:

Please give the code for start run server name share name etc. where the machine name is MSI-HD
and the target machine name is MSI-WIN10.

My goal here is to have a network folder shared by the two PCs at the usual User/lon/Public on the network.
Or move exiting shared folders I haven't found on WIN 10 anywhere yet. As I've said there seems to be a lot of
cabbage leaves to uncover.

There are problems getting the netsh commands to complete.
on Win10 I've made a screen shot of the error. But I'm just now getting a browser installed (not IE)
and will post the screen shot. I am finding though that all the commands I know from Win7
can be found but harder to use.

I will make a separate question to 10Forums on the use of the Classic Win7 Shell program where
(maybe) I can see what I'm doing.

Maybe will have the screen shot up yet today.

On MSI-HD the command would not complete. That screen shot I can do now-- see attached.

A variety of problems.

And here is the screen shot from the netsh commands on MSI-WIN10

I made what might be a more legible screen shot same as above.