DM800 Cccam Port Issue

T

tflpunk

Member
My Satellite Setup
Sky+
My Location
Surrey
Hi there,
I wondering if someone can help me out with a problem I've been having with my Dm800 set-up, because I've pretty much run our of ideas,
I've got a Dm800 running through a Home-plug (powerline ethernet), to my router (Belkin N1), then to my NTL/VM cable modem. I've got NewCS1.67 and Cccam2.1.2 working fine with my Sly Whitecard and it opens the channels fine. However, for some reason my peers are unable to connect to my server.
I have tried to portforward all sorts of different ports to my Dm800 through my router (in both UDP & TCP) but for some reason none of them appear to allow access. i.e. be it 12000, 34000 or 35241, I forward the ports in my router to the DM IP, but I'm still unable to see them when I do a port scan using something like canyouseeme.org

Can anyone help me resolve the problem?
Thanks in advance
 
If you are sure you are forwarding the port correctly then you need to check that your isp does not block certain ports.

I would always advise you to use a port other than the default ones such as 12000 or 15000.

Also check that you are opening and forwarding the open port to your dreambox.

Google portforwarding and port scanning.
 
I'm not familiar with your Cable modem/router.

On some routers, you need to open your required port as well as forwarding it to whichever IP address you want.

Can you forward any of the commonly used ports like 80, 21, 22 , 23?

EDIT: Too slow for Sonic :)
 
Hi there,

Thank you both for your speedy replies.

Cheers for the suggestion, however, I've tried forwarding all sorts of different numbers right across the range with no success.

On my router I have to specify the inbound port, the destination IP (the Dm800), then the internal port (which I set to the same value of the inbound port.

I've read through so many port forwarding sites and according to them I've doing everything correctly. So I think it's either my image or cccam is corrupt, or my ISP is port blocking. That said, I've searched the web for Virgin Media blocking ports and there's no info on it, so suggests it's not a problem.

Thanks again
 
It may be the Belkin N1 thats blocking inbound traffic on that port.

Are you using it as a switch or router?

Have you disabled the firewall on your Belkin N1? You may need to disable it and/or set up forwarding from that router too.

You could test whether or not its the Belkin that's at fault by temporarily connecting your dreambox directly to the NTL/VM cable modem.
 
Thanks for the reply.

The cable modem isn't a router (it's not adsl, it is fibre optic cable connection) so my only router is my Belkin N1. My dreambox plugs into that via my Homeplug connection.

Cheers
 
Step 1:
Locate a site called "Shields Up" (google it)on the internet from your PC which is behind the same router.
Step2:
Run a port scan on the ports you think you have opened using Shields Up.

It will show whether the port is closed, open, connectable.
a. If the port is closed, it means you have not opened the port in your router.
b. If the port is just open, it means you did not forward the port correctly or there is no service servicing the port => dreambox configured incorrectly or port forwarded to wrong port.
c. If the port is connectable then you have opened the port and the dreambox is listening on the port.
d. To check whether there is a service on your dreambox: telnet <dreambox ip> <port>
If the connection is made the dreambox is listening on the port, if no connection the problem is on the dreambox.

This is a good site to check port status.
 
Mate! That's a quality website, just what I'm looking for. I shall give them a go this evening.

Thanks for your help.
 
tflpunk said:
The cable modem isn't a router (it's not adsl, it is fibre optic cable connection)
Cheers
Click to expand...
I see...

Even so, I'd be very surprised if it would allow traffic through on all ports (Which is what is being assumed if you only set up any forwarding on the Belkin). Does it have a web interface you can connect to?
 
Fair comment.

I don't think it has a web interface as far as I know. Nothing seems to turn up on google.

Cheers
 
Just a thought, have you enabled DNS on your router/modem?
 
Cable modems are typically exactly that - just modems; they have no routing or switching capability, they merely convert the cable signal to a USB or ethernet interface. They also have no port handling capability or firewall. Up to now I have seen only one cable modem that has a builtin router (Cisco which is Waaaaaayy expensive) like you get on ADSL modems. Therefore all routing and firewall operations has to be done on the router that plugs into the cable modem, in this case the Belkin.
Most routers will automatically open the port on the firewall when you forward the port to the 'inside'. How this is done is very specific to the router being used. I don't know the Belkin products as I am no fan of Belkin products, so unfortunately I can't help with the configuration.
One thing to check is that you are not forwarding more than one port on the outside to the same IP/Port combination on the inside - I know that Cisco routers cannot handle it, so I imagine it is not possible to route that configuration.

DNS is not required to access the dreambox from the outside world - it used to look up requests from the dreambox to access other resources, so it could not cause the problem.

Setting the GATEWAY on the dreambox is very important - it has to be the IP of the box that you do the port forwarding on, otherwise it is impossible to resolve the return route for packets.
 
Thanks for the information guys.

I've used Shields up and pretty much every port comes up as 'stealth' until I forward the port in the router, then it turns to 'closed'

I've tried turning the fire wall off on the router but it has no effect on.

I'll check the dm Gateway setting now

Thanks again
 
Dm800 gateway is all good.

I have no idea why this doesn't work. The only ones that open when I forward them in the router are the usual 80,21 etc.
 
A call to your ISP's technical support might be in order. If forwarding works on ports 80, 21 etc. Then it looks like your ISP could be blocking certain ports. They may be able to give you a range of available ports.

There are bound to be ports that they allow for the likes of running PC game servers and what not. You could always use one of those ports.

PS: Sorry if I caused any confusion regarding forwarding of ports on your cable modem. We don't have cable in this part of the world, so I'm not familiar with cable modems. Though, I am surprised that some just allow all inbound traffic through. Thats a bit risky for anyone who doesnt know what they are doing.
 
I have cable in south of england and the provider does not block any ports, or at least none that I have tried, including 12000, 10001, 10003. Cable modems allow all traffic through and are not configurable by the user - the cable companies do configure things such as speed etc from their end. So i doubt it is a port blocked by the provider. I would still think it is a problem on the router. The following configuration is required:

1. Outside IP address: Supplied by the provider and normally cannot be set in simple port forwarding. On higer end routers it is possible to set this when multiple STATIC IPs are given by the provider.
2. Outside Port: Select the port that you wish to expose to the internet. This port can only be used once on the outside.
3. Inside IP address: The IP of the server on your local LAN (e.g. dreambox).
4. Inside port: The port the service is running on on the server e.g. 80 for a webserver default.

Notes: A single port on a server can only take a single port forwarded from the outside. It can, however, be forwarded several ports, provided each has a unique port on the outside and is forwarded to a unique port on the inside. As an example: It will work to forward port 80 outside to port 80 inside and port 8080(outside) to port 91 (inside) with both inside ports to the same IP. It will NOT work to forward both port 80(outside) and Port 8080(outside) to port 80(inside) on the same IP.

So check that this is not happening inadvertently.
What happens when you plug the dreambox straight into the cable modem and run Shields Up?
 
The only thing I'm not familiar with here is the homeplug networking thingy and whether or not you are using DHCP in your router.
For testing purposes I would wire the DM800 directly to the router using a Cat5/6 cable.

See if the router assignes an IP to the 800 automatically.
See if you can ping it from your computer.
Now try the tests you've done previously.
If you're not using DHCP to assign the IP to the DM800 then I highly recommend doing so.

Only 2 issues here for me, No DHCP or Homeplug networking.
 
I use the ethernet through power socket (homeplug thingy) on my DM600 upstairs. It works flawlessly
 
Cheers guys, I really appreciate the help.

In my router I set up the port fowarding as follows

Enable - checked
Description - DM
Inbound port - 12000
Private IP - 192.169.2.5 (Dreambox)
Private Port - 12000

I believe I set the IP address manually, as from what I've read so far, I thought DHCP was a no no as it might change your IP address. I shall reset the DM to pick it up automatically.

I shall also try the direct routes to the cable. Although I won't be able to run Shields Up is the DM800 is plugged directly into the router as I won't be able to access the web.

Thanks again.
 
DHCP is a big NO-NO in your setup. You have to assign a static IP on your dreambox (untick DHCP on the network setup screen so you can enter your IP). However, you have to make sure that the IP you assign does not conflict with DHCP assigned IP addresses (if you have DHCP enabled on other devices). See the "Network Terminology Explained" thread in this forum.

Sorry:o, of course you cannot run Shileds Up. If you have access to a friends PC you can try to telnet to the <internet IP>/port from that PC. Otherwise check with your peers if they can connect.

One other thing to check:
Your dreambox IP = 192.169.2.x - what is the IP of your router internally. It has to be 192.169.2.y if your subnet mask is 255.255.255.0 otherwise they are on different subnets and cannot see each other.
 
Back
Top