sorry, i was refering to windows 10 not haveing the smb v1 protocol installed and would not connect to a windows 7 share that uses smb v1 protocol only.
windows 10 connecting to another windows 10 would not need to negotiate smb v1 so it would not be that issue.
I just tend to open an admin cmd.exe then use the various net.exe commands an provide the credentials on the command line.
like:
net.exe use * \\servername\share /user:johnbl *
* prompts for the password of the user account on \\servername
or I connect to the interprocess communication share the use the UI
like
net use \\servername\ipc$ /u:johnbl mypassword
(after you make this connection all future connections will piggyback off of these credentials so you will not have to put them in)
again I provide the credentials of the server machine user account
guess I would look to see if the NetBIOS over tcp is turned on.
https://social.technet.microsoft.com/forums/windowsserver/en-US/d18bd172-e1a0-4a61-ba52-0952a1e3cabc/configuring-netbios-over-tcpip
in my case
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\Interfaces\Tcpip_{1e52f49e-aeba-4430-8b62-b824976ec0a5}
NetbiosOptions key
set registry key to 1 to enable
hardtech :
johnbl :
this link had interesting comments, one that indicated that he could not connect until the local account had entered in a password. various people had varioius different issues. it could give you a hint at what the problem could be.
windows 10 to windows 10 connections would have the correct protocol version. Ff it does not connect you would have a different issue. different network key, account not validated on the remote machine, or firewall blocking the connection.
hardtech :
Will this solve issue windows 10 pc accessing windows 10 share?
What different issue? All windows 10 same issue. Are you aware windows 10 v1803 removed home group? Am able to access using ip address but no using PC NAME