Cannot get web server through my DIR-655

[sh0rty]

This is driving me crazy and I cannot figure it out, so anyone that has done this successfully please let me know. Here is what I got...

Cox cable modem to DIR-655
Web server hard-wired to DIR-655

zonedit DNS pointing to my DIR-655 IP
virtual server with port 8080 (both) open and pointing to web server IP

webwerver is running win2k3 and the website is visible by IP only on network
I cannot get to the website outside the router.


I have tried opening ports for http, https, etc and nothing
I have tried using the virtual server option to the web server (still currently) and nothing
I have triple checked the IP that zoneedit has listed and it is right for the DNS



FYI - Although server is next to my PC, there is no monitor, mouse, etc...I only remote into it via remote desktop. It is a file server as well and all files are accessible with no problems. Additionally I can remote into and then open a web browser on the server and it works fine as well

almost forgot -- it worked great with same config but linksys router...I only changed everything to reflect the 192.168.0 subnet for the dlink


I am totally stumped...
If you need more info please let me know, but any help is appreciated.

 

[sh0rty]

anyone?

 

[ckrieger]

You said something about DNS...do you have a domain name that you're trying to route to your home server?

Also, have you been typing the port number after the domain/IP? Like example.com:8080 or 12.34.5.67:8080?

 

[sh0rty]

You said something about DNS...do you have a domain name that you're trying to route to your home server?

Also, have you been typing the port number after the domain/IP? Like example.com:8080 or 12.34.5.67:8080?

Yes I have a Domain name that points to my home server via zoneedit (free dns). This was a nobrainer on my old linksys, but added a Dir-655 and even upgraded to the new firmware to see if that fixed it..nada.

Like I said above the domain name points (via DNS) to my router (DIR-655). The router will not let anything through so you can see it. I added a virtual server entry (via router admin) which had the server IP and port 8080. In my opinion that should be all that is needed. It is almost like the router doesnt acknowledge the server. Funny thing though...from within my network it works no problem. So I type mywebpage.com from any computer within my network, the website comes up. I type mywebpage.com from any other computer, it times out. I dont even get that ILS default, so I think it is a setting that I am missing.

 

[annaconda]

If you can access from inside you network then you have to configure router correctly.

Did you have port forwarded to your server, make sure the port you are forwarding is also have access in your firewall.

First You can always turn off the firewall of your router to make sure firewall is not blocking it. Second are you assigning the correct WAN IP to your free dns ?

 

[sh0rty]

If you can access from inside you network then you have to configure router correctly.

Did you have port forwarded to your server, make sure the port you are forwarding is also have access in your firewall.

First You can always turn off the firewall of your router to make sure firewall is not blocking it. Second are you assigning the correct WAN IP to your free dns ?

In the DIR-655 there are 2 options, a Port forward (by application/IP) and a virtual server (by IP and port). I tried to port forward for http, https, ftp, etc to IP of server with respective ports....would not work. THe Virtual server is supposed to allow all server apps via that port/IP designated...that didnt work. Finally the IP on my free DNS points to the IP of the router on the web, not the 192.168.0.1, so I would say yes all that is configured correctly.
I read on another forum that someone had to make an IP reservation for their server in the admin and then dhcp instead of static IP. They mentioned that the router and server were not talking until he did that. Well..you guessed it, I tried that and it didnt work. I will try a full reboot on it tonight again, but win2k3 takes foooorrreeevvveeeerrr to reboot.

 

[Keiichi]

Did you set the Schedule option to "always" and the inbound filter to "allow all"?

 

[sh0rty]

Did you set the Schedule option to "always" and the inbound filter to "allow all"?

Sure did...

 

[Traze]

Well, I have to ask, are you only putting out the page on port 8080? I ask because port 80 is typical HTTP port, and 8080 is HTTPS. (Not that that should stop you)

I would also ask if it has a full NAT option. Forward your external address completely to your internal server. (Kinda sounds like the Virtual server option might be doing this, but not quite.)

"Also, are you trying to connect from inside the same connection? Does this new router perhaps have a no hairpinning option? Is it on? (Might be on and not changeable. Meaning you can't go out to an external DNS, etc. server, then be pointed back to your network and come back in on the same session.)"
Read some more, and saw this wasn't it.

 

[MrGuvernment]

your ISP could be blocking hosting on port 80 since alot of home ISP connection forbid http/ftp servers on home connections, if that is what you have...

if your ping the domain name does it resolve to your IP?

 

[sh0rty]

Well, I have to ask, are you only putting out the page on port 8080? I ask because port 80 is typical HTTP port, and 8080 is HTTPS. (Not that that should stop you)

I would also ask if it has a full NAT option. Forward your external address completely to your internal server. (Kinda sounds like the Virtual server option might be doing this, but not quite.)

"Also, are you trying to connect from inside the same connection? Does this new router perhaps have a no hairpinning option? Is it on? (Might be on and not changeable. Meaning you can't go out to an external DNS, etc. server, then be pointed back to your network and come back in on the same session.)"
Read some more, and saw this wasn't it.

I didnt look at the NAT options until you mentioned it. Here are my settings/disc that I am using now (default)
Firewall Settings

SPI is enabled

NAT Endpoint filtering with UDP endpoint address restricted
NAT Endpoint filtering with TCP port and address restricted

I might poke around with this one for a bit, but I dont want to open the floodgates either

 

[sh0rty]

your ISP could be blocking hosting on port 80 since alot of home ISP connection forbid http/ftp servers on home connections, if that is what you have...

if your ping the domain name does it resolve to your IP?

I thought that too, but it does point to the right IP.

 

[nessus]

This is how I'm serving my web pages on my DI-655. I have 24 virtual servers defined for different items with no issues.

If you can't see the image, my virtual server for my setup isn't working, if you can see it, its working. If yours is set up like this, but isn't reachable across the Internet, your ISP is blocking the port.

 

[Fryguy8]

1. 8080 isn't HTTPS as someone alluded to earlier
2. When setting up port forwarding/virtual server on the router, you need to use the local internal IP. It sounds to me like you are using your external IP in the port forwarding configuration.

 

[griffinhart]

Your ISP is blocking port 80. Many, many, many ISPs block common ports like 80. I know both Verizon and Comcast both block ports. i just did a quick google and Cox does indeed block port 80.

My ISP does the same thing but I use a work around. I use EasyDNS as a domain provider and they allow me to forward URLs. I can create a host name such as

my.domain.com and have it forward to
my.domain.com:1234 in "stealth mode" so users don't even see the URL address change.

Then my DIR-655 listens for traffic on port 1234 and then forwards it to my web server on port 80.

 

[exstyle]

Your ISP is blocking port 80. Many, many, many ISPs block common ports like 80. I know both Verizon and Comcast both block ports. i just did a quick google and Cox does indeed block port 80.

My ISP does the same thing but I use a work around. I use EasyDNS as a domain provider and they allow me to forward URLs. I can create a host name such as

my.domain.com and have it forward to
my.domain.com:1234 in "stealth mode" so users don't even see the URL address change.

Then my DIR-655 listens for traffic on port 1234 and then forwards it to my web server on port 80.

He is using port 8080 and already stated it works with a link sys router. Can we see a screenshot of what you have setup on the router?

 

[sh0rty]

I will try to post a screenshot when I get home from work

thnx for all the insight too...

 

[sh0rty]

Your ISP is blocking port 80. Many, many, many ISPs block common ports like 80. I know both Verizon and Comcast both block ports. i just did a quick google and Cox does indeed block port 80.

My ISP does the same thing but I use a work around. I use EasyDNS as a domain provider and they allow me to forward URLs. I can create a host name such as

my.domain.com and have it forward to
my.domain.com:1234 in "stealth mode" so users don't even see the URL address change.

Then my DIR-655 listens for traffic on port 1234 and then forwards it to my web server on port 80.

I finally tried to webforward to differnt port and walla!!! Freakn stoked. I guess they just started blocking port 80 coincidentally right when I got a new router, but redirecting traffic did the trick..many thnx to all the replies

 

[sh0rty]

He is using port 8080 and already stated it works with a link sys router. Can we see a screenshot of what you have setup on the router?

I had to webforward from my dns "zoneedit" to point to port 8080 to make it work. Before I guess once it hit the router it pushed it through, but i had to manually config with this one.