dish remote access port??

[gtjr92]

Ok I am trying to use the new remote access feature but cannot get it to work. I am able to get an ip address on the dvr box. I can even ping it from my desktop.
I do have a real firewall not some linksys box, what ports does this feature use?
Also is it possible to access the box directly without going through dishnetwork.com? I tried putting the ip of my dvr in my browser to no avail.

[Jim5506]

No, you've got to go through the Dish website.

There is no software on the box for direct access.

[gtjr92]

that answers one of my questions. What about the ports anyone know what port(s) this uses so I know what to forward on my firewall??

[JayStil]

I'm seeing ports between 604xx and 605xx.

[gtjr92]

This morning the remote access feature was down for a bit. After it came back up I was able to access my dvr with remote access. I did not have to open any ports. SO it was a tech issue on their end.

[Pepper]

There are no ports. Your dish box establishes an outbound connection to their server and periodically asks it if there's anything to do. If web browsing works on your local network their stuff will work.

[tnsprin]

There are no ports. Your dish box establishes an outbound connection to their server and periodically asks it if there's anything to do. If web browsing works on your local network their stuff will work.

No input ports. Essentially the outbound ports are the same ones you need for http and https (80 and 443) plus normal UDP port 25 for address lookup. Most firewalls will have these open.

[kcoriginal]

No input ports. Essentially the outbound ports are the same ones you need for http and https (80 and 443) plus normal UDP port 25 for address lookup. Most firewalls will have these open.

Gentlemen, I couldn't let this go uncorrected... sry.

Port 25 is for outbound email. It works on TCP.

Port 53 is for Name look-ups, also known as DNS, Domain Name Service.
Port 53 is classically a udp service, however, lately it is advised to open udp/tcp for port 53, as many new tech uses tcp for a more reliable look-up.


udp communication is broadcast like one way, ie: radio.
Fire and forget.


tcp communication is broadcast, then verified by the receiver, ie: airport control tower talking to the pilot.

Flight 123 head 090 at 5000, over.
Roger tower, this is 123 changing to a heading of 090 at 5000 ft. thank-you.
Have a good trip 123. Tower out.

TCP sends, the receiver acknowledges, then the sender acknowledges the acknowledgment. For every single 1500 character packet.

If you have a firewall in place, you will NEED to understand these details.

You will need to identify the receiver, preferrably give it a static IP address or a DHCP reservation so it shows as the same IP all the time.

Then, you enter a firewall rule allowing for 192.168.0.x to send traffic on port xxxx to destination x.y.z.q.

My Dish receiver is always trying to talk to 8.7.94.155 on port 30123. I think this is going to be required on ALL recievers as I have no remote DVR features in use at this time.

What other port numbers are required for remote DVR features?

Perhaps port 80 and port 443, OUTbound, as these are VERY common ports used for surfing the internet (http and http-secure, respectively). It would be understandable if Dish configured those to be needed. However, how about the INbound ports to actual control the DVR?

Chances are, Dish will send that signal through the satellite stream. I wouldn't be suprised if NO INbound ports are needed, as Dish has some MASSIVE bandwidth available to send back TO YOU... it's just that they need you to connect your internet so YOU can communicate to them, tell them you received their TCP packet, etc.


HTH someone.


kc