Hi 90% chance that this is a network / firewall issue : straight from the FAQ :
- First check that the used port is correct, standard it is 21234. If you never changed this, or it's the first time you see this number, this setting will probably be correct. You can find the value in the exe.config files (CCNet.exe.config, CCService.exe.config) in the system.runtime.remoting/application/channels part. - Next, check the firewall on the server. You can do this by running the following command in a prompt : *netsh firewall show portopening* If you get an empty list, no firewall is on, if you see a list, check that there is a line containing the correct port : standard it is 21234 To open the port, run the following command : *netsh firewall add portopening TCP 21234 CCNET* check firewall settings on both servers with kind regards Ruben Willems On Thu, Jul 30, 2009 at 11:18 PM, Saran <[email protected]> wrote: > > Hi, > > I recently installed Cruisecontrol.NET on a new machine and started > the same (I haven't setup any projects yet). I added the new server > details in webdashboard/dashboard.config on the machine where CC.NET > and webdashboard are working fine. > > <servers> > <server name="oldmachine" url="tcp://localhost:21234/ > CruiseManager.rem" /> #old line > <server name="newmachine" url="tcp://newmachine:21234/ > CruiseManager.rem" /> #new line > </servers> > > Even after restarting IIS I'm unable to see the new server. > > I'm not sure what I might be doing wrong. > > Thanks in advance for your help > Saran
