Separate names with a comma.
Discussion in 'DIRECTV Tips and Resources' started by tomasmk2003, Aug 19, 2012.
Great question and would be nice to know the answer to it once everything is resolved.
The OP is planning to have DirecTV run a coax near the router and go with a BB DECA, so we may never know.
Oh well. As long as he gets fixed up that's all that really matters for the purposes of this thread.
Being basically clueless about all the features & functions in a router, this may be completely off the wall, "but" instead of trying to open a port in the router, "I wonder" if there is a protocol or feature that should be turned off?
Could there be something in the default settings that the WCCK doesn't like?
Could this be why the secondary IP is being set to one from the router?
That's why I recommended DMZ zone. It is a totally wide open connection to that port it is applied on.
"But what if" it isn't a port that is blocking/closed, but instead a port open/feature enabled, that causes the problem?
I'm just wondering if we've been looking at this backwards. :shrug:
My actual suggestion would be to setup port forwarding, but that is nothing I want to tackle over the phone.
A feature of the router conflicting with the WCCK is a possibility too. Would have to know what advanced features the router has first.
Here's where there is a link to the comcast user's manual:
After looking through all 54 pages:
I'm not sure the router had a factory reset last night. [since the laptop WiFi wasn't lost]
There's a whole section for parental controls and I have no idea of what the defaults are.
What I don't like about the whole thing is it seems the router grants the CCKW an IP address via DHCP like it should but then appears to refuse to forward traffic back and forth... It would be nice to know what the CCKW is doing differently then the receiver plugged direct to router.
And to put a slightly sharper point on this:
What is the router doing/not doing over WiFi that isn't a problem with the BB DECA [HR21 to DECA to BB DECA to ethernet port on router], that was connected and worked?
Another thing could be the type of wireless signal being used. Is it A,B,G or N and what is the WCCK using in that regards? The router might be on wireless B or N and the WCCK needs wireless G. There are just way to many variables to go through without having access to both devices simultaneously.
The WCCK will connect to both G & N routers.
Now "if there was" a problem, wouldn't it show up trying to log into the WCCK over the WiFi connection, which worked fine?
I was just giving it as an example of a simple thing that it could be. My brain hurts trying to remember everything from this thread.
I would say if the problem is with the Comcast router itself with HDCP protocol not giving out proper IP addresses it may just be simply defective. Maybe a firmware reset or upgrade would resolve the issue.
"You know you're getting tried when"....
an HDMI protocol is mixed up with a router's. :lol:
The DHCP seemed to have been passing out a "reasonable" IP address, subnet, and gateway/DNS. Everything within the LAN reacted to requests from other devices. The router simply wouldn't let the WCCK have access to the internet, which didn't matter if it was from a DVR or a laptop connected to the WCCK.
Lol sorry DHCP. My fingers have dyslexia. Dynamic Host Connection Protocol
What happened when you tried to ping the unknown device's IP address? I'm sure you answered this already but I really don't want to go back through the thread to find it.
Actually "pinging" was never tried, nor thought would be needed, as logging into the WCCK's GUI was done a few times to test/proved connectivity.
I have a couple/few unknown on my router and one is this:
If he has an 802.11n capable router/gateway, might be worth looking to see if WMM is enabled or disabled. I've seen strange things happen with WMM disabled, especially on 5GHz wireless devices.
It has b/N capabilities, but looks to be a 2.4 GHz only WiFi.