Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[munnge]

have a dir-655 and comcast cable

the router is set to dhcp for both WAN and LAN

i also have a dcs-920(camera) set with a static IP and port 8029. i have set a virtual server setup for to the dcs-920 IP and port 8029 for both private and public.

the above setup was set for the past several months and allowed me to go to the WAN IP plus port 8029(XXX.X.XXX.XXX:8029) from any external IP and i could view the webcam.

all of a sudden this past weekend it stopped working. i cannot get any port to open up on the router now regardless of how i set it up. port forwarding, virtual server i even tried DMZ and still couldn't get a port to open. i had an old firmware so i thought i'd upgrade to the latest, that didn't help. i've reset the router to factory specs and redone the entire wan/lan/virtual server setup and i still can't get any port i choose to open up much less see my camera externally.

help?

[alessiocesar]

I have somehow the same settings, but witha TW-IP422W port 1025...Funy thing theIP camera is set up under virtual server, and my sftp, ssh2 servers ruuning on a linux box under port fwd...The later ones never worked under virtual server...I cannot say why they put 2 similar things doing the same things (or almost the same things)..With my old WRT54G I had only por fwd, very straight fwd...You do DDNS on your DIR-655 to access your camera by hostname not a dynamic IP?

I don't see why it worked and now not, unless your ISP started blocking that port...

-ac

[munnge]

no one can help with this?

[munnge]

nice forum. thanks for all the helpful replies.

[davevt31]

nice forum. thanks for all the helpful replies.

This is a user's forum, not everyone has the same setup as you.  If someone knows what to tell you to help you out they will.  Did you contact Comcast to see if maybe something has changed on their end, or DLINk telephone support to see if maybe something hardware related is wrong with the router.

Getting sarcastic with other users will only lead to help not being given.

[munnge]

This is a user's forum, not everyone has the same setup as you.  If someone knows what to tell you to help you out they will.  Did you contact Comcast to see if maybe something has changed on their end, or DLINk telephone support to see if maybe something hardware related is wrong with the router.

Getting sarcastic with other users will only lead to help not being given.

i wasn't expecting anyone to have the same setup as i do. i did expect someone with a 655 and comcast though to have had a similar experience and/or have some insight.

yes i contacted comcast - they said nothing has changed on their end and pointed to it being "my network" causing the problem. 

haven't contacted d-link support other than posting in here. i'm not expecting it to be the router... unless it decided to crap out overnight i don't see how it could be.

i also have tried a totally different router - i have an old netgear laying around and set it up. same issue - can't get any port to open. this leads me to believe it's comcast - this is where i'm out of my element though - unless comcast decided to wholly block my IP from any internal connections on ANY port - i just don't see how that could be.

[davevt31]

All I can tell you is that if it was working and you didn't make any changes on your end and the second router did the same thing, I would lean toward something with Comcast.  I know some of the cable companies have talked about throttling down users, this may included blocking of some ports.