Print

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

[cpirie]

I'm trying to get a few forwards going to a wired pc on the DIR-645 (http, https, rdp). Unfortunately nothing I seem to try works! The PC is set to a static IP and the virtual server is set to point to that IP. The static IP is out of the range of the dhcp selections (though I have tried a dhcp reservation and that didn't help).

I've also tried just using the Port Forwarding to no avail.

When I connect the PC directly to the Internet (remove the router) everything is fine and dandy so it has to be an issue with the router (not the pc).

Any help/clues as to how to get this working would be great!

[FurryNutz]

What ISP Service do you have? Cable or DSL?
What ISP Modem do you have? Stand Alone or built in router?
What ISP Modem brand and model do you have?
If this modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems.

Ensure DNS IP addresses are being filled in under Setup/Internet/Manual?
Turn off QoS options.
Turn off Advanced DNS Services if you have this option under Setup/Internet/Manual.
Turn on DNS Relay under Setup/Networking.
Setup DHCP reserved IP addresses for all devices on the router.
Ensure devices are set to auto obtain an IP address.
Set Firewall settings to Endpoint Independent for TCP and UDP.

[cpirie]

What ISP Service do you have? Cable or DSL?

Cable

What ISP Modem do you have? Stand Alone or built in router?

Built in router (but disabled)

What ISP Modem brand and model do you have?

Cisco DCP-3825

If this modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems.

The modem is bridged (wireless reception was terrible)

Ensure DNS IP addresses are being filled in under Setup/Internet/Manual?

Router has two proper DNS server address

Turn off QoS options.

Have never been turned on

Turn off Advanced DNS Services if you have this option under Setup/Internet/Manual.

Advanced DNS Services was found under Setup -> Parental Control and is set to "None: Static IP or Obtain Automatically From ISP" (from 4 choices, one being Advanced DNS)

Turn on DNS Relay under Setup/Networking.

DNS Relay is on

Setup DHCP reserved IP addresses for all devices on the router.

I really hope this isn't a requirement else it would be a rather large flaw in the router. I gave it a try anyways.

Ensure devices are set to auto obtain an IP address.

No static IP's set.

Set Firewall settings to Endpoint Independent for TCP and UDP.

This has been set

One other thing to note is I have PPTP checked under ALG Configuration as I couldn't get outbound vpn connections working until I had this option checked (one would think this would be on by default since any other router I've had has never required special configuration just to allow an outbound vpn connection). Unchecking did not resolve the issue either.

Another issue as I just tried a reboot on the device to see if that would change anything; I have to reset my ISP modem every time I reboot the dlink for it to get an IP from the ISP. I have to say so far I'm very disappointed in this product. My 5 year old WRT54G seems vastly superior to this device in every aspect minus offering wireless-N. Really wishing it hadn't died.

Anyways, these changes did not get the virtual server settings working. Any other ideas?

[FurryNutz]

Are you getting a public IP address under Status/Device Info/Wan section? or a private IP like 192.168?

Does the Cisco have a DMZ by chance?
Seems like if you have to reboot the ISP modem to be an IP address to the router, that the ISP modem could be a place to start. Do you get any phone service thru the ISP modem? If not, I recommend getting into a Motorola SB 6121 cable modem. These are great modems and this would all you would really need.

Reserving IP addresses on routers is not a flaw of any router. Yes they do work automatically however when using options and rules, it's always been known to set up reserved IP addresses on routers for devices, so that each devices has it's own IP address that never changes and also any options or rules you set up on the router will not break if the devices IP address happens to change while having a DHCP assigned address. Reserving IP addresses is part of the routers job and is preferred to use it this way specially when you start connecting a lot of devices.

Can you post what your virtual server options look like? Might a configuration issue here. Trying to help narrow down the issue and see if we can help you find the cause. What are you using for VS? Any application information and port information would be helpful.

[cpirie]

Are you getting a public IP address under Status/Device Info/Wan section? or a private IP like 192.168?

Public IP address. After resetting the router I end up with 0.0.0.0 until I reset the cable modem.

Does the Cisco have a DMZ by chance?
Seems like if you have to reboot the ISP modem to be an IP address to the router, that the ISP modem could be a place to start. Do you get any phone service thru the ISP modem? If not, I recommend getting into a Motorola SB 6121 cable modem. These are great modems and this would all you would really need.

I don't have any access to the Cisco when it's flashed into bridged mode. The ISP (Shaw) offers two modes for the modem; a wireless router which you have access to as a normal wireless router for configurations and whatnot, or "bridged" mode which makes it act like a standard cable modem (wireless and administration functionality is disabled). I don't have any phone service through them at the moment and if I did the phone is routed through another modem. I don't use any voip services either. Also, I don't think I'm allowed to choose what modem to use with the ISP. They provide one with the service for free.

Reserving IP addresses on routers is not a flaw of any router. Yes they do work automatically however when using options and rules, it's always been known to set up reserved IP addresses on routers for devices, so that each devices has it's own IP address that never changes and also any options or rules you set up on the router will not break if the devices IP address happens to change while having a DHCP assigned address. Reserving IP addresses is part of the routers job and is preferred to use it this way specially when you start connecting a lot of devices.

I didn't mean the option was a flaw, I meant if this was a requirement to have the forward work was a flaw. On my other routers I just assigned the one computer I need to access remotely as a static IP while the rest of the devices stayed DHCP. I actually love the feature since I don't have to reconfigure TCP/IP if I take the computer to another location. This wasn't an option at all on some of the routers.

Can you post what your virtual server options look like? Might a configuration issue here. Trying to help narrow down the issue and see if we can help you find the cause. What are you using for VS? Any application information and port information would be helpful.

The setting is actually quite dummy proof, except that it doesn't seem to work Yes, the computer it's forwarded too is set to 192.168.10.101 (checked ipconfig). I would like to set up more forwards (https, and some other private software as I'm a programmer) but I am just trying with these two at the moment. If I telnet to port 80 I do get a connection but no response, but if I telnet to 3389 it's closed. My assumption here would be the web listener on the router for configuration is getting the connection. If I hit it with a web browser it times out.

[FurryNutz]

You can specify DNS addresses under Setup.Internet.Manual

Just seems like the modem isn't handing off DNS addresses correct after the router is reset or the router isn't picking them up after the reset.

[cpirie]

Not sure why DNS would have anything to do with the router picking up an IP address. I could see issues occuring if its mac address were getting changed but I'm sure this is not the case. It worked fine with the WRT54G. So did port forwarding.

Either way, having to reset the cable modem isn't such a big deal as the uptime on the device is usually months. My biggest concern is the port forwarding as I have to remote into my computer from other locations to do my job. If I can't get this working I'll have to return the router and try something else!

[Hard Harry]

Hmm, first thing I would do is test to make sure the gateway is still in bridge mode. Are you getting a private 192? Or a public 72.x.x.x (or what ever)? What is your gateway? Alot of times those devices CAN be in bridge mode, then the ISP does a firmware update that resets it to factory. I say this because your symtoms really sound like a double NAT issue.

Second, try enabling remote management on the router and try to access it from work/friends house. That will test port 8080 to the router's WAN. Then disable remote management after testing.

Next, try disabling anything that might conflict with your forwarding rules. QoS, UPnP, anything you can think of. Besure to save the config file before doing it though.

Last, do you have Shaw Buisness? Because according to this, they block port 80? Different Shaw?

[cpirie]

Hmm, first thing I would do is test to make sure the gateway is still in bridge mode. Are you getting a private 192? Or a public 72.x.x.x (or what ever)? What is your gateway? Alot of times those devices CAN be in bridge mode, then the ISP does a firmware update that resets it to factory. I say this because your symtoms really sound like a double NAT issue.

IP Address : 68.151.x.92
Subnet Mask : 255.255.252.0
Default Gateway : 68.151.x.1
Primary DNS Server : 204.194.232.200
Secondary DNS Server : 204.194.234.200

The device is definitely still in bridged mode else I would be getting 192.168.100.x.

Second, try enabling remote management on the router and try to access it from work/friends house. That will test port 8080 to the router's WAN. Then disable remote management after testing.

Next, try disabling anything that might conflict with your forwarding rules. QoS, UPnP, anything you can think of. Besure to save the config file before doing it though.

I enabled remote management and set it to port 8080. Connected fine!

I tried turning off everything I could find but with still no success. One thing I did notice was there's nothing in the router log files at all about the connection attempt. I think I saw a post on a forum somewhere else (different dlink router though) showing the connection. Should I be seeing these attempted connections in the log? As it stands I see various DHCP messages but that is it.

Last, do you have Shaw Buisness? Because according to this, they block port 80? Different Shaw?

Same company, but that must be a sub-company specific to a region. http://www.shaw.ca is the company I'm with (residential) and there are no port blocks (except maybe 25 to help prevent spam). If I connect the PC directly to the cable modem there are no issues with connecting to web server or remote desktop.

[cpirie]

In case anyone finds this thread I talked with dlink support and they have marked the router as defective.

[FurryNutz]

Can you elate more to what they said about it? Who did you talk to? Did they say the marked this device as defective or was it the firmware?
Did you submit for RMA?

Where are you located? Which support number did you call?

If your interested, maybe someone can review your router settings with you using teamviewer.

[FurryNutz]

Sent you a PM.

[cpirie]

Can you elate more to what they said about it? Who did you talk to? Did they say the marked this device as defective or was it the firmware?
Did you submit for RMA?

I don't recall the name of the person I talked too (not that it would be the persons real name anyways since it was obviously a call center out of India) but basically it was your standard "reset device to factory using the button, and re-configure". It was a very long drawn-out process that should of taken 5 minutes but I could tell the computer with his step-by-step instructions on his end was being quite slow.

After doing the setup the forwarding still did not work so he "marked the device as defective" and did offer an RMA. I turned down the RMA as I've only had the device for a couple days and decided to return it to the place I bought it from.

Where are you located? Which support number did you call?

I'm located in Western Canada and called the 1800 number on the support page for my region (glad to see they're 24/7!)

If your interested, maybe someone can review your router settings with you using teamviewer.

This won't be necessary as I decided to just return the device to the store before it went out of return range. I'm not one to hold a grudge (I realize there can be a bad apple in a bunch of good) and have been recommended to try the dir-655 so I'm going to give that router a shot. I would of been willing to try another dir-645 but I can't get one locally and the turn-around for newegg.ca is horrid (5-7 business days to ship back, 2-3 business days to process return, 3-5 business days to get replacement).

[FurryNutz]

Ok man, sorry you had to return it. The 655 should be good for you. Come visit us there.