DM800 cs set up problem

K

kdol

Member
My Satellite Setup
DM800 & DM500
My Location
North East UK
Hi,
I have an 800 & a 500 which are now talking to each other & I can watch sly white card on either.
I now want to progress to cs and have been trying to set this up with a mate who also has the same white card + he is trying to share with me his also, so that we can have a server/client connection before we move on.

The 800 is running blackhole v12and cccam2.1.2 & newcs 1.67, this is the server. I thought all I needed to do was add a F line for my mate and his C line to my cccam.cfg .... wrong!!

We both have dyndns addresses but have also tried with actual ip addresses and still cannot connect with each others cards. The cards are shown with red button in cccam info.

My cccam.cfg contains the following
This file was created with NewCS & CCcam Config Creator Written By B16MCC
N: 192.168.0.4 15000 User1 User1 01 02 03 04 05 06 07 08 09 10 11 12 13 14
SERVER LISTEN PORT 12000
C: his.dyndns.org 12000 myusername mypasswd yes
F: hisusername hispasswd

There is also another F line that is used by the 500 but have ommitted this.

As mentioned, the server is not seen as active in cccam info.

We can ping each others dyndns addresses no problem.

Any help would be appreciated. Thanks
 
kdol said:
Hi,
I have an 800 & a 500 which are now talking to each other & I can watch sly white card on either.
I now want to progress to cs and have been trying to set this up with a mate who also has the same white card + he is trying to share with me his also, so that we can have a server/client connection before we move on.

The 800 is running blackhole v12and cccam2.1.2 & newcs 1.67, this is the server. I thought all I needed to do was add a F line for my mate and his C line to my cccam.cfg .... wrong!!

We both have dyndns addresses but have also tried with actual ip addresses and still cannot connect with each others cards. The cards are shown with red button in cccam info.

My cccam.cfg contains the following
This file was created with NewCS & CCcam Config Creator Written By B16MCC
N: 192.168.0.4 15000 User1 User1 01 02 03 04 05 06 07 08 09 10 11 12 13 14
SERVER LISTEN PORT 12000
C: his.dyndns.org 12000 myusername mypasswd yes
F: hisusername hispasswd

There is also another F line that is used by the 500 but have ommitted this.

As mentioned, the server is not seen as active in cccam info.

We can ping each others dyndns addresses no problem.

Any help would be appreciated. Thanks
Click to expand...

Have you port forwarded the listening Port to allow him in? And vice versa.
 
kdol said:
Yeah,
Port 12000 is open for both him and me.

cheers
Click to expand...


That is not really what was said, port forwarding is not just a case of opening a port, you have to tell the router to forward through a port to another IP
 
_www.portforward.com
 
Thanks for advice have had the 800 feeding the 500 now for 10 days and works fine.
Now really battling trying to cs with a mate. thought all that was needed was a F line in my 800 cccam.cfg. My file is:
# This file was created with NewCS & CCcam Config Creator Written By B16MCC
N: 192.168.0.3 15000 User1 User1 01 02 03 04 05 06 07 08 09 10 11 12 13 14
SERVER LISTEN PORT 12000
F: me mypasswordd (for 500 )
F: him hispassword (hs access to my 800)
c: his.dyndns.org 12000 me mypassword yes

Port 12000 is enabled for port forwarding in my router and is also seen as open using PFPortchecker

He has more or less the same as me with me and him reversed in his cccam.cfg

We both use blackhole 12 and Newcs 1.67 with Cccam 2.1.2

When looking in CCcam info - Servers the local card is shown as active (green) but the remote card (i.e. his on my box ) is shown with a red dot and there is no card recognised.

Tried all sorts to get this to work. thought this was supposed to be the easy bit?? We are aware of CCcam 2.1.3 but have not been successful with getting this to run either.

As you can detect its not quite a Dream yet!!

Help would be appreciated.
 
Thanks for your input.
I can confirm that we have done as directed by portforward site. The ports are open and are forwarded to our computers ip address.

Unfortunately we are no further forward.

Any other suggestions?
 
The ip address you need to forward the port to is not your computer but your dreambox which for you is 192.168.0.4. Also is there a check box in your router settings that needs ticked or checked to enable the router to use Dynamic ip addresses. Mine has .
 
Firstly, please don't ask the same question in more than 1 thread. I've moved you last post into here from the Config Creator 0.7.0 thread as it was a duplicate post and not relevant to the config creator release thread.


Now, It really is very simple. 1 thing to bare in mind, if you are trading C lines and your card is in NewCS you will both see the other persons card at hop2.

Also, is it a typo or did you copy and paste the CCcam.cfg into your post above ? The reason I ask is there's no : in the SERVER LISTEN PORT line. It should read
SERVER LISTEN PORT : 12000

Next, if you have forwarded port 12000 in your router to your Dreambox IP address then you should be good to go. Here's how to share your card with your friend.

Your CCcam.cfg
N: 192.168.0.3 15000 User1 User1 01 02 03 04 05 06 07 08 09 10 11 12 13 14
SERVER LISTEN PORT : 12000
F: Friend Password 2 0 0 { 0:0:2 }


His CCcam.cfg
SERVER LISTEN PORT : 12000
C: your.dyndns.org 12000 Friend Password no


Thats it, thats all you need. If your uncertain that your dyndns is setup correctly then try replacing that with your current WAN IP address which you'll find in your router status page normally.

Lastly, if you're getting into CS an essential piece of software is CCcamphpinfo by Toogoody. Its a php web based package that shows the status of your CCcam server, it shows very extensive information and is massively useful. Google for it and how to set it up.
 
Guys, I really appreciate that you are trying your best to help.
At the moment its still no go so here is more actual data.

Tom, straight after posting my last comment I thought that the dreambox ip should be input rather than my computer so changed to that. No change.

I have a sly Netgear DG834GT wireless router that is hard wired not wireless. Hence you can safely assume my network knowledge is low.
I had already ticked the use a Dynamic DNS service and included the DynDNS service provider, my name.dyndns as host name, plus the correct user name and passwords in the set up.

I created a Service which I called Dream 12000 which is for protocol TCP with start and end port 12000.
I then created Firewall outbound rule for this service that Always allows access to any Lan or Wan address.
The Firewall inbound rule is also Always allow to my dream800 ip address and from any Wan user.

I use AVG Internet Security for my firewall etc. I did have some blocks happening that I was unable to get round but worked this out with support at AVG. So now believe everything is open from that perspective. I did this before posting this thread.

B16MCC, my apologies if my two posts were seen a poor form but I did this intentionally because I considered I had two areas that needed clarification. The above being the router / firewall aspects and the second being my cccam / newcs elements.
I am quite happy to leave this as one post now.

I have now corrected my cccam server listen port line - thanks for pointing that out, its something I had totally missed, I'd copied the line from another post and assumed it was correct - I was wrong!!

Me and my mate have now included the lines exactly as you have specified and our cards are still not seen by the respective dreamboxes.
We have both tried using the Wan ip's instead of dyndns addresses and still nothing worked.

We have been at this a couple of weeks now and put in a great amount of effort. But if we are doing the wrong things is there any wonder?

Much as I wanted to stay away from pay servers do you think it is time to go down that track and work individually in trying to get the system set up, rather than the two of us possibly confusing each other?

Your advice is much appreciated.
 
Update

Thanks to Tom and B16MCC.

Having gone back through and made the corrections you outlined and leaving the stuff for a few hours I then found that all was working for me.

Jeez what a relief.
 
Back
Top