04-24-2014 10:50 AM
About a month ago I upgraded to Uverse, from DSL and have been pretty happy with the speed upgrade (Ya ya I know, DSL was about as slow as you could go). Anyways, I have a security camera system (Qsee) tied into the network and everything seems to work fine. Meaning, the Port Forwarding is set up correctly. I know this because I can view my cameras via the Iphone app, and from a buddy of mines home computer; he can type in my WAN address and the Webclient Login box pops up. So, that is showing that remote access is available.
So, my issue is peculiar. I cannot view my camera system from my desktop at work. I try typing in my DDNS address and that just times out. I try typing my WAN address and it also times out. Now, my cubemate has the same camera system, but with Comcast, and I can log into his system, from my computer with NO issues. To log into his system I merely type in his IP address and away I go. A second co-worker has the same set up as well, but again with a Comcast router at home, and I can view his system from my PC too. So, I know its not my PC or a Firewall issue. What else could this be????
I am STUMPED! Any ideas?
04-29-2014 3:10 PM
Just trying to wrap my head around this one still. I guess I just don't know enough about IP tracing to understand why, with the exception of the final destination address, everything is the same; however, I cannot gaini access to my Router from my office. I attached a clearer tracert for my friends DVR and Mine. Again, his I can gain access to, but mine I cannot. Could there be something in the Router Firewall that doesn't allow this IP address to tap into its gateway?
Below is the traces for both. Again, I can access my DVR cameras via my phone, so everything is working as it should. Well, I guess not really since I cannot gain access via my PC.
04-30-2014 1:41 PM
Apparently some router is blocking ICMP just beyond the last hop that reports back.
Unfortunately, this renders the Traceroutes unhelpful as a mechanism for determining your issue. If your phone can reach the cameras while outside your home's WiFi range, then your home RG and network are configured properly for external access. You could confirm this another way by using a public computer in a library, or your phone in a WiFi hotspot (such as Starbucks).
I'm assuming there's no one in your corporate setting who would be "helpful" if you mentioned this issue.
04-30-2014 2:22 PM - edited 04-30-2014 3:08 PM
No, the IT guys are too busy to worry about this issue.
Its bizarre, I sent these same IP addresses to my brother and he got the same results. One worked, but mine did not. Could it be Port 85 is being the stubborn issue? I am wondering if I try and change it to Port 80 to see if this clears up the issue. Maybe the firewalls have a problem with this port being non-standard? Well, wait...I think I read somewhere that Port 80 is used by the 589 for something else.
Just reaching for some rashionale.
04-30-2014 3:33 PM
I don't think the 589 intercepts external requests to port 80 (as it does for port 443 if you have a wireless IPTV receiver). Using port 80 may help you around corporate firewalls and the like.
04-30-2014 3:54 PM
Welcome to the AT&T TV Hub!We have some helpful articles located under TV Hot Topics.On the left you will see DIRECTV and U-verse TV links. Click on those links for more information regarding Apps, Billing, and TV troubleshooting tips.
© 2017 AT&T Intellectual Property.This link will open a new window All rights reserved. AT&T, Globe logo, Mobilizing Your World and DIRECTV are registered trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. All other marks are the property of their respective owners.
Congratulations! You earned the Liz badge!