I've noticed a similar problem to yours with the exception that when i check the web interface via a browser, I can connect without any problem.
For this reason I had put it down to a problem with the version of CCcamInfo which was pre-installed on the image I'm using (Its Dreamelite which I gather is closely related to Nabilosat teams images).
Is CCcam still reading the local card and accessing shares via remote servers? In my case it is, everything is fine except for connecting using CCcamInfo.
fintannl said:
i think the problem may be that clinet is hard powering down his dreambox each night (simply unplugging it without soft powering it down). i guess cccam might not be able to cope with such an immediate loss of communication and as such ther server hangs. is this likely or possible
Killing CCcam without a proper shutdown on the client end shouldnt cause any problems for a server. All the default CCcam start/stop script does is issue a 'killall -9' signal to tell the process to stop without letting it perform any cleanup operations (Like telling any servers its connected to that its going to sleep/shutting down), which amounts to the same thing as killing the mains power.
If your router is not updating your dynamic DNS mapping, you should use the Inadyn plugin thats already installed on your image for the job. It works flawlessly once you set it up. On the image I'm running its under Blue Panel -> Settings Panel -> Inadyn Settings.