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

Duplicate name on Network while connecting to Windows Slave

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major Major
    • windows-slaves-plugin
    • None
    • Jenkins Master is running on Centos 7.3 installed via yum repo
      Jenkins Windows Slave is running Windows Server 2012 R2

      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.

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

              Created:
              Updated:
              Resolved: