Cannot register new teamcity build agent in different network

We are planning to added one new build agent to the current pool. The new machine is not in the same network as the teamcity server and our firewall policy is quite strict. However, our network people has opened the port 999(which the teamcity server using)on the agent machine and we can log on to the teamcity page in IE without problem.

After install the build agent,the service started without problem but it cannot connect to the teamcity server and in the teamcity-agent.log file, we found a entry saying :

[2009-07-22 16:54:31,728] INFO - jetbrains.buildServer.AGENT - Build agent started [2009-07-22 16:54:31,775] INFO - buildServer.AGENT.registration - Registering on server: [name: ctf-dev-ws01-96, ownAddress: 172.17.36.96, ownPort: 9090, buildId: <not running build>, availableRunners: [simpleRunner], availableVcs: []] [2009-07-22 16:54:46,837] WARN - buildServer.AGENT.registration - Call http://10.5.25.43:999/RPC2 buildServer.registerAgent2: java.net.ConnectException: Connection refused: connect [2009-07-22 16:54:46,837] WARN - buildServer.AGENT.registration - Connection to TeamCity server is probably lost. Will be trying to restore it. Take a look at logs/teamcity-agent.log for details (unless you're using custom logging).

Do we need open more port to the teamcity server in order to use this machine as build agent? Please advise.



3 comments
Comment actions Permalink

Sorry for the delay. The question is still actual with latest TeamCity release?


 
Kind regards,
Marina
 
0
Comment actions Permalink

We have just the same problem. I have no idea what can be the reason of this problem. Could you please help?

We use TeamCity Enterprise 6.0 (build 15772).

0
Comment actions Permalink

Hi Ekaterina

Server and agents open network connections in both directions. So your firewalls should additionally allow traffic from server to agent's port.
Here are detailed description of Server-Agent Data Transfers. Pay attention on security, if you're deploying the agents in unprotected networks.

Michael

0

Please sign in to leave a comment.