|
I've read just about everything about port forwarding and other problems regaruding Linksys WRT54G. I got all three needed ports for web hosting forwarded (I even tried using DMZ to see if I left a port out) and none of those fixed the problem. Also to note, my windows firewall is disabled and there is no other firewall or anti-virus on the machine. Now the problem is that I can view my web page using the hosting service through dyndns. I'm running both the client and having the service run in the router, neither one report any problems. The problem is everyone else outside the network thus far have not been able to view the website I'm hosting. I have yet to figure out what my problem is at the moment and all I have before the router is a DSL router. I've never had this kind of problem before. For additonal info, I'm running on Windows 7 and I do have a static IP setup for the machine within the router and through the connection settings within windows. |
|
If you have the Linksys connected behind a device provided by your ISP, then if it's a router, you will need to forward ports first from the ISP-provided device to your Linksys, and then from the Linksys to your web server. What device have you configured to update your DynDNS hostname? Could you post your hostname here, or - if you're not comfortable with posting your hostname publicly - could you tell us the first two segments of the IP address the hostname currently resolves to? Also see Cry Havok's answer to this question. 66.199 for the ip address and I'm using my Linksys WRT54G router. I used to use no-ip services, until I had some security thing not only blocking outside connections, but even the loopback, but I don't seem to have that problem with dyndns.
Sep 07 at 07:16 PM
nakmeath
I also forgot to mention I've used DMZ mode on my router to TEST if it was a port problem. The same problem occurred. Also yesterday, I've tested a different computer on my home network to access the website I'm hosting and it connected. I've even went as far as disabling windows firewall. Port connections and the firewall were not blocking it. I've even used the port testing tool for port 80 and it reported that it's open.
Sep 08 at 08:06 PM
nakmeath
|
