D-Link Forums
D-Link VPN Router => DSR-500N => Topic started by: CaseyJanke on March 12, 2017, 04:38:16 PM
-
I'm trying to setup a port forward for a camera system. I want any external ip address hitting our public ip address on port 81 to go to our camera server.
I'm not sure what, if anything I'm doing wrong, but it's not working. If it were you should get a login page.
I setup a custom service defined on port 81 and then a custom firewall wall as show here: http://mytechco.com/dlinkforum
Any suggestions on what I'm not doing right?
-
Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)
- What Hardware version is your router? Look at sticker under the router case.
- Link>What Firmware (http://forums.dlink.com/index.php?topic=47512.0) version is currently loaded? Found on the routers web page under status.
- What region are you located?
Internet Service Provider and Modem Configurations
- What ISP Service do you have? Cable or DSL?
- What ISP Modem Mfr. and model # do you have?
Does the Enable PF slider button need to be in the ON position?
How about disabling uPnP and testing...
-
I'm not onsite, so can't look at stickers, is that available through the interface?
Firmware is: 2.11B201C_WWFirmware
Serial is QB5F1E1000032 (maybe that tells you the HW versions)
I'm in New York
Cable internet service 100 by 10
Not sure of the modem model
-
IF you can get modem Mfr and model #. Just checking for NAT here is all.
-
Ok thanks. Not sure when I will get back out to that site. I've just never had a problem port forwarding at any of my clients regardless of teh modem they were using. However who knows, I actually tried this same 500 at another client and it couldn't even get an address and internet with that modem. The thing has been a bit funky from the start. I tried to configure it in my home office and was having trouble getting an internet connection, then all of a sudden poof it worked. So I took it onsite thinking it was ready to go and I couldn't get it to connect to the modem. I even talked to tech support that day and couldn't get it to connect. So I decided then, at that client I would order the DIR-655 and use that (we had a long conversation about that experience as well). In the end, and I hate to say this here because I know you are trying to help and all, but in the end I went and bought a R6220 and it connected to the internet fine, I was able to port forward fine and I was able to setup QOS fine and the client hasn't had any issues since. I decided to give this 500 another shot at this other new client. I did connect to the internet ok, but now having trouble with port forward. So at this point I think I'm just giving up and going with something else. Short term probably the R6220 since it works at my one client. Long term maybe pfSense. Thanks again for trying to help with all of this it just all seems to quirky to me, but who knows, maybe its just me. Thanks
-
See one other mention that the DSR was very finicky about connecting to modems. So would be good to get some details on this modems the DSR is being connected too.
Only other thing I would check on is swap out LAN cables.
Use good quality CAT6 cabling.
If the DSR has a menu feature for WAN port speed, check this out and try manually setting the WAN port speed from AUTO to 100Mb or 1000Mb.
These reports of not getting connected to a ISP modem, means there usually is a bad cable, handshaking problem or not getting a IP address from ISP modem. Also some ISP Modems have built in routers already so this can be a factor. There could be an IP address conflict between the ISP modem using 192.168.0.1 and the DSR using same.