Windows 10: Every OS recovery having had 1 PCname, while advised from Anti, keep just unchange-PCname...

Every OS recovery having had 1 PCname, caught once ,two PCnames existed , and put bitlock on by whom, that is impeded me at Advance-recovery ? How to free this yet ..."meanwhile advised from Anti front by 2013 that, keep just Not-Change-PCname always" getting mc-fw-host alerted from 3rd party ware-app where showing more than 1 repeated PCname . met 3x the same PCname installing Microsoft.365 when there is only 1 machine naming it? Clean Recovery in OEM key , at Jan 17 2024 , Rename PC to

:)

 

Network Share \\PCNAME vs \\PCNAME.local

Thanks, I know about disabling IPv6 and the difference in \\pcname vs \\pcname\share

Sorry, I wasn't clear ... basically I was doing a test and before I saved any credentials ...
If I accessed the PC by \\pcname or the share by \\pcname\share I got the network path not found vs prompt for credentials, but when using \\pcname.local or \\pcname.local\share I would get prompted for credentials. Once I got prompted for credentials, then the \\pcname or \\pcname\share would start working (i.e. prompt me for credentials vs network path not found). That's why I was wondering what the difference is between \\pcname and \\pcname.local

 

Network Share \\PCNAME vs \\PCNAME.local

You can disable ipv6 as it's not used as homegroup has been removed now. If you try and connect to \\pcname your connecting to the PC if you use \\pcname\sharename you are connecting specifically to the share

 

Network Share \\PCNAME vs \\PCNAME.local

Just an observation and I'm not really sure I understand ...

What's the difference between \\PCNAME and \\PCNAME.local ... when accessing a network share ???

I was trying to access a new PC network share by \\PCNAME and kept getting the 0x80070035 error, when it should be prompting me for credentials (see notes). I then accessed it by \\PCNAME.local and it prompted me for credentials which I entered (did not save) and it connected. The share then showed in File Explorer > Network as PCNAME.local ... which it should and I could access it. I then restarted both PC's and the PCNAME.local was NOT showing in File Explorer > Network ... which I expected. I then tried accessing the share by \\PCNAME and it prompted me for credentials, which I entered (saved) and it connected and has been working fine ever since.

Note:
1. I could see the share and access it by \\IPADDRESS (did not save credentials), so I know that all network share settings were correct (i.e. private,discoverable,share/ntfs permissions,password protected, etc)
2. IPv6 settings default (i.e. did not disable IPv6 or set prefer IPv4 over IPv6)
3. SMBv1 NOT Installed
4. Both PC's running Win10 (1803 - 17134.137)