Thanks Ruben, i figured those had to be changed as well. so i updated both 
of those config files on the target server, and got the svc to start 
successfully. unfortunately there still seems to be something blocking our 
communication between the 2 servers, probably firewall related in our 
company, although i don't see why port 443 would be blocked.

On Monday, November 24, 2014 1:24:05 AM UTC-6, Ruben Willems wrote:

> you also need to update ccnet.exe.config or the ccservice.exe.config.
> There is a setting that specifies the port to use
>
> you could use Ip adress or a friendly name, bot will work
>
> with kind regards
> Ruben Willems
>
> On 21 November 2014 at 21:00, <[email protected] <javascript:>> wrote:
>
>> I have the same issue, but tried updating the dashboard.config of my main 
>> server to include this target server: 
>> url="tcp://ipaddress:443/CruiseManager.rem" but that still doesn't work.  
>> do you have to change some of the configs on the targer server?  Can you 
>> use friendly urls in place of ip address as well?
>>
>> On Wednesday, March 6, 2013 7:56:13 AM UTC-6, Dan Winsor wrote:
>>
>>> Huh, I never would've thought of that.  Worked like a champ and I don't 
>>> use SSL for anything on those boxes so that's perfect.  In fact, thinking 
>>> about it, that should fix some CCTray issues I regularly run into too.  
>>> You're a good man, Ruben.  :)
>>>
>>> On Wednesday, March 6, 2013 8:26:09 AM UTC-5, Ruben Willems wrote:
>>>
>>>> Hi
>>>>
>>>> maybe the ssl port : 443 ?
>>>>
>>>> with kind regards
>>>> Ruben Willems
>>>>
>>>> On 5 March 2013 20:32, Dan Winsor <[email protected]> wrote:
>>>>
>>>>> Hi all,
>>>>>  
>>>>> I have two CCNet servers on two separate LAN subnets and It blocks 
>>>>> port 21234 across subnets - actually they block pretty much everything 
>>>>> except "standard" ports like 80 and the like.  I'd like to be able to run 
>>>>> a 
>>>>> projectTrigger where I monitor one system from another, but I can't 
>>>>> figure 
>>>>> out what to use for serverUri within the projectTrigger, though.  Within 
>>>>> the subnet, the default tcp://<CCNetSystem2>:21234/CruiseManager.rem 
>>>>> works fine.  I was googling to see if some http address would suffice, 
>>>>> but 
>>>>> I couldn't find anything.  Also, I tried reconfiguring CCNet to use a 
>>>>> diferent port than .Net Remoting (21234) but I couldn't find anything 
>>>>> free 
>>>>> that the firewall would not block.  Any suggestions to try?  Thanks very 
>>>>> much in advance.
>>>>>  
>>>>> Dan
>>>>>
>>>>> -- 
>>>>>  
>>>>> --- 
>>>>> You received this message because you are subscribed to the Google 
>>>>> Groups "ccnet-user" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>> an email to [email protected].
>>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>>  
>>>>>  
>>>>>
>>>>
>>>>  -- 
>>
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "ccnet-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"ccnet-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to