Newcamd clients not connected

[Macaz]

Hi
I've been away for a while.
When I updated with the newest patch (March 12) today on my HD9000, my Newcamd clients don't show as connected.
Can anyone help please?
Thanks

[echelon]

better check your networking is on, that the box has a lan ip address same as before, and ideally check it has internet access by checking the g*ft works

[Macaz]

All my network settings seem fine. When I updated with the March 29th patch i had to re-insert my IP settings. I'm receiving as a client via Cccam and newcamd. My newcamd clients are not connected to me. I've checked my router settings and all seems fine there too.

[echelon]

make sure you have used the same ip as before and the port forwarding is forwarded to that ip address using the correct port you selected for newcamd

also check the card is decoding locally too and seen in the menu

[Macaz]

I've checked it all again.
My IP in my Spiderbox is 192.168.000.003 and it's the same in my router firewall settings
The port is the same in the box and the router also but they are still not connecting to me

[echelon]

better check your host has your current ip address too

also reboot the box

and did you factory reset after installing the new patch ?

[Macaz]

My host has my dyndns address
i've rebooted
I'll however try another factory reset

[echelon]

My host has my dyndns address
i've rebooted
I'll however try another factory reset

I actually said check that your host has your current ip address, meaning that your personal dyndns host has resolved your current isp ip address

your clients will already have that dyndns address, but if it hasnt got your isp ip address resolved they wont connect

[Macaz]

Sorry echelon
I have been away too long
I'm a bit confused and lost now i'm afraid

[echelon]

my point is that the dns host you use to distribute to clients has to have your current isp ip address which is either updated by your router or by a tool on your pc desktop or something similar
your clients lines point at this host , and the host redirects them to your router (after resolving your ip), which forwards the port to your spiderbox ip address if you have setup the port forwarding in the router correctly using the port you use for distribution. your spiderbox opens the port when newcamd is switched on (newcamd server setup) and allows you to send to the clients over the network I described above, from the spiderbox, using the port, through the router, to the host dns, then to the clients

the client has the dns host address, the port, the name and the password

port forwarding is not used to receive which is why your incoming lines work ok (when you are receiving)

[Macaz]

My dns host has the same IP address as my isp IP
My router port forwarding is correct (Port, IP etc)
It worked before the update and none of the settings have changed with the patch

[echelon]

so in the menu is the card being detected in the setting below common interface and above keyedit ?

if so , and as I asked you earlier but you did not answer me, is the card decoding locally (on the spiderbox itself) ?

is newcamd set to ON in newcamd server setup ? is the deskey also correct ?

have you allowed the spiderbox mac code into the lan settings of the router ?

[Macaz]

I've had a look and to be honest it was last year when I put the details of my card into the setting below common interface and above key edit. It seems to have cleared what was put there apart from an N*S serial number. My whole box seems to be screwed up after the patch update

Sorry about that but I've done the boxkey trick and my card is being read and decoded locally in my spiderbox