The JNLP slaves do not communicate with Jenkins master using http, but they have their own protocol and they use a different port for that. Jenkins chooses a random port for that by default but if you need it to be a fixed port to make a hole in a firewall or something, you can set the port in master configuration page.
-- Sami speKc <[email protected]> kirjoitti 7.2.2012 kello 0.58: > > 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
