Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-41920

Duplicate name on Network while connecting to Windows Slave

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: windows-slaves-plugin
    • Labels:
      None
    • Environment:
      Jenkins Master is running on Centos 7.3 installed via yum repo
      Jenkins Windows Slave is running Windows Server 2012 R2
    • Similar Issues:

      Description

      When i try to connect to slave on Jenkins Master i'm getting the following strange error.

      [2017-02-10 10:51:19] [windows-slaves] Connecting to jenkins-slavewindows1.xxxx
      ERROR: A duplicate name exists on the network.
      jcifs.smb.SmbException: A duplicate name exists on the network.
      at jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:563)
      at jcifs.smb.SmbTransport.send(SmbTransport.java:664)
      at jcifs.smb.SmbSession.send(SmbSession.java:238)
      at jcifs.smb.SmbTree.treeConnect(SmbTree.java:176)
      at jcifs.smb.SmbFile.doConnect(SmbFile.java:911)
      at jcifs.smb.SmbFile.connect(SmbFile.java:954)
      at jcifs.smb.SmbFile.connect0(SmbFile.java:880)
      at jcifs.smb.SmbFile.queryPath(SmbFile.java:1335)
      at jcifs.smb.SmbFile.exists(SmbFile.java:1417)
      at hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:219)
      at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:261)
      at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
      at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      at java.lang.Thread.run(Thread.java:745)

      We only have this windows slave and the name is unique, so i don't understand why this is happening.

        Attachments

          Activity

          Hide
          ricko Richard Otter added a comment -

          I get the same message, unpredictably. A requirement seems to be that the Windows slave have a DNS alias in addition it it's host name.

          Chronology of current situation-  ( Jenkins v1.1651.3, Java 1.8 up 131 x64, OS Windows Sevrer 2008)

          I created a new Windows slave  and configured it using the "DCOM" method.

          For Hostname, I entered the Windows computer name. It had worked as expected for months.

          I decided to create a DNS alias for the slave that matches the Jenkins slave name. The slave names

          make sense to me, the computer names assigned by our IT are too long to remember)

          Still worked OK.

          I reconfigured the slave to use the new DNS alias in the hostname configuration field.

          Now I'm getting the duplicate name error and the slave won't connect.

          I reverted back to the Windows computer name. Still get the duplicate name error.

          I tried to flush the DNS cache on the Windows Jenkins host, but no luck. (ipconfig /flushdns)

          I then switched the host name configuration field to the numeric IPv4 address and it works again.

          How can this be fixed? Seems like a Jenkins bug. No Windows machine complains when I connect to the slave with normal file sharing using withe of the names.

           

           

           

           

          Show
          ricko Richard Otter added a comment - I get the same message, unpredictably. A requirement seems to be that the Windows slave have a DNS alias in addition it it's host name. Chronology of current situation-  ( Jenkins v1.1651.3, Java 1.8 up 131 x64, OS Windows Sevrer 2008) I created a new Windows slave  and configured it using the "DCOM" method. For Hostname, I entered the Windows computer name. It had worked as expected for months. I decided to create a DNS alias for the slave that matches the Jenkins slave name. The slave names make sense to me, the computer names assigned by our IT are too long to remember) Still worked OK. I reconfigured the slave to use the new DNS alias in the hostname configuration field. Now I'm getting the duplicate name error and the slave won't connect. I reverted back to the Windows computer name. Still get the duplicate name error. I tried to flush the DNS cache on the Windows Jenkins host, but no luck. (ipconfig /flushdns) I then switched the host name configuration field to the numeric IPv4 address and it works again. How can this be fixed? Seems like a Jenkins bug. No Windows machine complains when I connect to the slave with normal file sharing using withe of the names.        

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            syntetikvision João Ferreira
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: