New Contributor II
•
7 Messages
How do I get port forwarding to work on my Cisco DPC3825
I have set up port forwarding per the instructions on my Cisco DPC3825. I can't seem to get it to work. It seems fairly straight forward, This is what I have;
|
|||||||||||||||||||||||||||||||||
Related Content
Closed
1
0
Closed
4
0
Closed
5
0
Closed
1
0
Closed
3
0
ChrisL
Former Moderator
•
7.1K Messages
0
0
Mark_S_
New Contributor II
•
7 Messages
I tried some different ports and it didn't work. I did a port scan and it showed 80, 8080 and 8081. I know I have 8081 opened to manage my cable modem remotely. I thought Cox blocked 80 and 8080?
0
0
Trikein
Contributor III
•
806 Messages
1. Are the computers(server) connected directly to DPC3825 or is there something in between.
2. Are you able to ssh into your server locally?
3. Does the DPC3825 allow ssh for remote access to itself? That would explain why 8080 is open without you forwarding it, because thats the default. This is more a question for ChrisL then OP.
4. If 80 is forwarded, where is it forwarded to? Are you running a web server on your network too?
5. Might want to try disabling the firewall and see if that works. If it does, then you can go through and isolate what feature of the firewall is blocking the port and disable it instead.
0
0
ChrisL
Former Moderator
•
7.1K Messages
Here's a reference guide with the list of ports that are blocked/filtered:
http://ww2.cox.com/residential/support/internet/article.cox?articleId=cacf82f0-6407-11df-ccef-000000000000
SSH is a bit unusual in that it is commonly used for administrative access to devices. Many devices that have the capability to be accessed via SSH will not correctly forward said traffic. I'm assuming this is a Linux machine of some kind you're trying to access. I would also check to see if you can SSH to it locally from within your home network as well as check any iptables/firewall rules for SSH rules. Don't forget to also check the SSH config on the target machine to see if access is restricted to certain hosts/subnets.
0
0
Mark_S_
New Contributor II
•
7 Messages
I can ssh into it locally
The DPC3825 rejects ssh connections
Port 80 isn't forwarded, I don't have a web server and it doesn't connect to the WAN side of the DPC3825
The firewall is off. Once I get it working I will turn it on though
0
0
Accepted Solution
ChrisL
Former Moderator
•
7.1K Messages
0
0
Trikein
Contributor III
•
806 Messages
Im curious, why are you using a Gateway? I think in your situation you would be much better with a stand alone modem and router, that way you have full control over the router and firmware. Im not a fan of how Cox modifies the firmware/config file without publicly documenting what they changed, and this could be a prime example. Not to mention the firmware isn't Cisco, but old Scientific Atlanta stuff. And they can update the firmware anytime they want and they don't have to notify you. My advice, stay faaaar away from gateways.
0
0
Mark_S_
New Contributor II
•
7 Messages
My first 3 cables modems were stand alone Motorola's since the beginning of Cox internet. This is the first time I opted for the Cisco gateway. I was getting something else at the Cox store and she said that our cable modem was obsolete and we need a new one to get the speed we are paying for. The last modem was 6 years old. I figured I would have one less switch on my network. It did increase my speed though.
0
0
Mark_S_
New Contributor II
•
7 Messages
I set up port 2202 on my Linux machine and forwarded it. That fixed the problem. The Cisco DPC3825 eats port 22!
0
0
Accepted Solution
Mark_S_
New Contributor II
•
7 Messages
I set up port 2202 on my Linux machine and forwarded it. That fixed the problem. The Cisco DPC3825 eats port 22!
0
0
Health_Edge
Valued Contributor III
•
4.2K Messages
Why Cox is pushing bad hardware on it's customers, I will never know. I think the main reason is Verizon gives out gateways so Cox felt it has to give out gateways to compete.
Glad you were able to get around the problem. Makes you wonder what other kind of security vulnerabilities (like a open port 22) Cox missed in the firmware.
0
0