Windows 11 Networking fails asking for Credentials

%3CLINGO-SUB%20id%3D%22lingo-sub-2855700%22%20slang%3D%22en-US%22%3EWindows%2011%20Networking%20fails%20asking%20for%20Credentials%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2855700%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20issue%20I'm%20having%20is%20with%20Windows%2011%20networking%20and%20accessing%20a%20computer%20on%20the%20LAN%20using%20it's%20UNC%20name%2C%20which%20in%20my%20case%20is%20my%20primary%20computer%20running%20Windows%2010%3CSPAN%3E%26nbsp%3B(%3C%2FSPAN%3EPROMETHEUS%3CSPAN%3E)%20and%20my%20secondary%20computer%20(%3C%2FSPAN%3ESORCERESS%3CU%3E)%3C%2FU%3E%3CSPAN%3E%20running%20Windows%2011.%20%3C%2FSPAN%3E%3CEM%3EBoth%20computers%20sign%20in%20at%20startup%20using%20the%20same%20Microsoft%20Account.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20trouble%20I'm%20having%20is%20if%20I%20open%20Explorer%20in%20Windows%2011%20using%20%3CWINDOWS%3E%2B%3CE%3E%20(or%20via%20a%20desktop%20or%20taskbar%20shortcut)%20and%20then%20directly%20enter%20%22%5C%5Cprometheus%22%20into%20the%20address%20bar%2C%20it%20will%20sometimes%20allow%20access%20to%20the%20computer%20on%20the%20network%2C%20and%20other%20times%20it%20will%20ask%20for%20login%20credentials%20and%20fail%3A%3C%2FE%3E%3C%2FWINDOWS%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22Screenshot%202021-10-18%20065907.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F317986i21C07AC1F6A984EE%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Screenshot%202021-10-18%20065907.png%22%20alt%3D%22Type%20computer%20UNC%20Name%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EType%20computer%20UNC%20Name%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22Screenshot%202021-10-18%20065933.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F317987iEC0727480DAB917F%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Screenshot%202021-10-18%20065933.png%22%20alt%3D%22Network%20credentials%20fail.%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3ENetwork%20credentials%20fail.%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20on%20the%20rare%20occasion%20that%20the%20connection%20is%20made%20using%20the%20UNC%20path%2C%20and%20I%20can%20map%20a%20network%20drive%2C%20the%20network%20drive%20might%20not%20automatically%20reconnect%20at%20startup%20because%20of%20the%20same%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20if%20I%20enter%20the%20IP%20Address%20for%20PROMETHEUS%20as%20%22%5C%5C192.168.1.3%22%2C%20then%20I%20can%20browse%20the%20network%20without%20problems%20and%20correctly%20maps%20network%20drives%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22Screenshot%202021-10-18%20070351.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F317989iBD72B10A4A9D2FEE%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Screenshot%202021-10-18%20070351.png%22%20alt%3D%22Browse%20the%20network%20using%20IP%20Address%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EBrowse%20the%20network%20using%20IP%20Address%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22Screenshot%202021-10-18%20071301.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F317990iD16C2483BE43052A%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Screenshot%202021-10-18%20071301.png%22%20alt%3D%22In%20network%20folder%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EIn%20network%20folder%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOne%20might%20think%20this%20is%20a%20configuration%20issue%20on%20the%20Windows%2010%20machine%20regarding%20file%20sharing.%20I%20do%20not%20believe%20so%2C%20as%20other%20devices%20on%20the%20network%20(mixed%20between%20Windows%2010%20and%20Android)%20can%20access%20the%20PROMETHEUS%20computer%20without%20issues%20using%20either%20the%20UNC%20Name%20%22%5C%5Cprometheus%22%20or%20the%20IP%20address%20%22%5C%5C192.168.1.3%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20problem%20about%20credentials%20appears%20only%20when%20I'm%20trying%20to%20access%20PROMETHEUS%20from%20SORCERESS%20which%20is%20running%20Windows%2011%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22Screenshot%202021-10-18%20072103.png%22%20style%3D%22width%3A%20460px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F317991i075375BBFB8F59E1%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Screenshot%202021-10-18%20072103.png%22%20alt%3D%22SORCERESS%20running%20Windows%2011%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3ESORCERESS%20running%20Windows%2011%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2855700%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EConfiguration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESecurity%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

The issue I'm having is with Windows 11 networking and accessing a computer on the LAN using it's UNC name, which in my case is my primary computer running Windows 10 (PROMETHEUS) and my secondary computer (SORCERESS) running Windows 11. Both computers sign in at startup using the same Microsoft Account.

 

The trouble I'm having is if I open Explorer in Windows 11 using <WINDOWS>+<E> (or via a desktop or taskbar shortcut) and then directly enter "\\prometheus" into the address bar, it will sometimes allow access to the computer on the network, and other times it will ask for login credentials and fail:

Type computer UNC NameType computer UNC Name

 

Network credentials fail.Network credentials fail.

 

If on the rare occasion that the connection is made using the UNC path, and I can map a network drive, the network drive might not automatically reconnect at startup because of the same error.

 

But if I enter the IP Address for PROMETHEUS as "\\192.168.1.3", then I can browse the network without problems and correctly maps network drives:

Browse the network using IP AddressBrowse the network using IP Address

 

In network folderIn network folder

 

One might think this is a configuration issue on the Windows 10 machine regarding file sharing. I do not believe so, as other devices on the network (mixed between Windows 10 and Android) can access the PROMETHEUS computer without issues using either the UNC Name "\\prometheus" or the IP address "\\192.168.1.3".

 

This problem about credentials appears only when I'm trying to access PROMETHEUS from SORCERESS which is running Windows 11:

SORCERESS running Windows 11SORCERESS running Windows 11

 

1 Reply

@Dzomlija 
I was having a similar problem, this site helped me as the credential manager was caching some credentials which were not valid.

Enter network credentials error on Windows 11/10 [Fixed] (thewindowsclub.com)

Once I cleared the offending credentials and re-tried I got access to my shared resources without requiring a login.