MK, Thank you for the response; I was unaware of this option. I made the change you suggested and it's still not working; i did see the new port referenced in the small GUI pop-up, and so I know that change was picked up. Neither host (master, slave) has firewall enabled. I issued trace from master->slave/slave->master and there are no intervening hops.
-john k. On Feb 6, 3:05 pm, Mattias Vannergård <[email protected]> wrote: > I had this problem when using a special Firewall. > > Go into Manage Jenkins -> Configure system -> and un-select the "Use random > port" under security. And set a Fixed port of your liking. > > /MV > > 2012/2/6 speKc <[email protected]> > > > > > > > > > > > i am a relatively novice Jenkins user but have some experience setting > > up slave-nodes on both Linux and Windows (2008 R2) systems. I'm > > experiencing a Windows slave-node issue that has me stumped. Any debug > > suggestion would be most appreciated. Launch method is 'Launch slave > > agents via Java Web Start'. I've confirmed master and slave-node can > > ping each other, and I am attempting to launch the Jenkins client > > while on remote'd into the client. > > What appears to be the problem, is the slave is attempting to connect > > to the wrong port. The small GUI pop-up that indicating an connection > > attempt is being made states 'Connecting to <server-name>:57040. I > > expect the port to be 8080. When the command-line launch command, > > shown in the slave configuration, is issued, the slave starts just > > fine; the port used is 8080. > > > thanks, > > > -jk
