10 Replies Latest reply on Mar 17, 2011 3:39 AM by scottunify

    UNC Authentication Failed (Preferred Servers)

    Apprentice

      Hi all

       

      We have configured 12 Preferred Servers in our LANDesk 8.8 SP3 Console and entered the same username and password for each.  However, 3 out of the 12 fail UNC Authentication.  We have triple checked the username and password is correct.  We have re-created them from scratch and closed/reoepened the Console to no avail.  We know these 3 servers are up and working as normal because machines have been LANDesk imaged and software deployed from them and the core can ping them and vice versa.  Software distribution appears to working as normal so we're not sure what problems this lack of authentication may cause.

       

      Where are we going wrong please?  Perhaps there's a logfile we can check for more info to help us locate  the problem?

       

      Thanks
      Scott

        • 1. Re: UNC Authentication Failed (Preferred Servers)
          zman Master

          I would double check the rights on the share where they are failing.

          • 2. Re: UNC Authentication Failed (Preferred Servers)
            Apprentice

            Thanks for the reply.  There are many shares on the 3 servers that are failing to authenticate, so which share should we check for the correct permissions?  We've checked the software distribution share and set to everyone full control so there should be no share permission issue on the affected servers.

             

            We've read the Console help file which states:-

            "...As long as the credentials you provide for the preferred server work with the package share (Click Test credentials in the User name and password dialog), managed devices should be able to access the share".

             

            Despite supplying the same username/password, we still cannot understand why 9 preferred servers authenticate but the other 3 servers do not.  What, if any, are the implications of failed authentication?  Any ideas how we can resolve this please?

             

            Cheers

            Scott

            • 3. Re: UNC Authentication Failed (Preferred Servers)
              zman Master

              Check the remote server's security log for failures. Can you authenticate to the package share on the remote server using the credentials? No real logs that I know of.

              • 4. Re: UNC Authentication Failed (Preferred Servers)
                Apprentice

                I launched a cmd prompt using the credentials and accessed the share from there, so yes we can authenticate to the package share on the remote server using the  credentials.

                 

                The only items I found in the server's Security Event Log are:-

                ------------------------------------------------------

                Event Type:    Success Audit

                Event Source:    Security

                Event Category:    Logon/Logoff

                Event ID:    576

                Date:        07/07/2010

                Time:        09:50:57

                User:        <domain\username>

                Computer:    <server>

                Description:

                Special privileges assigned to new logon:

                     User Name:    <username>

                     Domain:        <domain>

                     Logon ID:        (0x0,0x1CBF64C)

                     Privileges:    SeSecurityPrivilege

                            SeBackupPrivilege

                            SeRestorePrivilege

                            SeTakeOwnershipPrivilege

                            SeDebugPrivilege

                            SeSystemEnvironmentPrivilege

                            SeLoadDriverPrivilege

                            SeImpersonatePrivilege

                For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

                 

                Event Type:    Success Audit

                Event Source:    Security

                Event Category:    Logon/Logoff

                Event ID:    540

                Date:        07/07/2010

                Time:        09:50:57

                User:        <domain\username>

                Computer:    <server>

                Description:

                Successful Network Logon:

                     User Name:    <username>

                     Domain:        <domain>

                     Logon ID:        (0x0,0x1CBF64C)

                     Logon Type:    3

                     Logon Process:    Kerberos

                     Authentication Package:    Kerberos

                     Workstation Name:   

                     Logon GUID:    {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}

                     Caller User Name:    -

                     Caller Domain:    -

                     Caller Logon ID:    -

                     Caller Process ID: -

                     Transited Services: -

                     Source Network Address:    xxx.xxx.xxx.xxx

                     Source Port:    0

                For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

                 

                Event Type:    Success Audit

                Event Source:    Security

                Event Category:    Logon/Logoff

                Event ID:    538

                Date:        07/07/2010

                Time:        09:52:24

                User:        <domain\username>

                Computer:    <server>

                Description:

                User Logoff:

                     User Name:    <username>

                     Domain:        <domain>

                     Logon ID:        (0x0,0x1CBF64C)

                     Logon Type:    3

                For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

                ------------------------------------------------------

                 

                I didn't find any errors for this user account so assume the credentials are fine.

                 

                This really has us stumped.  Any other ideas please?

                 

                Thanks
                Scott

                • 5. Re: UNC Authentication Failed (Preferred Servers)
                  Employee

                  Can you try disconnecting any mapped drives from the server where you are doing the preferred server credentials test to the servers where the authentication is failing and try again?

                  • 6. Re: UNC Authentication Failed (Preferred Servers)
                    Apprentice

                    We've checked there are no mapped drives from the core to the server that fails to authenicate and vice versa.

                     

                    We ran net use on the core but there are no connections to any other servers.  In case it may be hidden for some reasons, we tried to disconnect any connection to the share but no joy:-

                     

                    C:\Documents and Settings\admin>net use \\server\share /d
                    The network connection could not be found.

                     

                    More help is available by typing NET HELPMSG 2250.

                     

                    Then we tried map to this share but there are multiple connections to it already apparently:-

                     

                    C:\Documents and Settings\admin>net use \\server\share  <password> /u:<domain\username>
                    System error 1219 has occurred.

                    Multiple connections to a server or shared resource by the same  user, using mor
                      than one user name, are not allowed. Disconnect all previous  connections to th
                      server or shared resource and try again.

                     

                    Any ideas please?

                     

                    Cheers
                    Scott

                    • 7. Re: UNC Authentication Failed (Preferred Servers)
                      Rookie

                      Hhave you been able to resolve this issue?

                       

                      on the core server, go to a command prompt and type net use * /d /y then attempt again.  The server has a remembered connection to the target device under a specific set of credentials and will not allow multiple connections to be created with different credentials.

                      • 8. Re: UNC Authentication Failed (Preferred Servers)
                        Apprentice

                        Ben, thanks for your suggestion but we've already tried that several times, there are no connections at all.

                         

                        Any other suggestion welcome....

                         

                        Thanks

                        Scott

                        • 9. Re: UNC Authentication Failed (Preferred Servers)
                          baderr Rookie

                          I had a similar problem, then after reading this stream I closed the Landesk management console on my desktop and opened it on the Core. The core has no other network connections, but my desktop had a variety, including DFS shares. I was able to verify the Preferred Server from the Core.

                           

                          ...for what this is worth...

                          • 10. Re: UNC Authentication Failed (Preferred Servers)
                            Apprentice

                            I don't have the Console on my desktop but I know there are several other people scattered around the firm who do.