Connecting to my webserver with ISP restrictions

kronos299

Beta member
Messages
1
I'm running Windows Server 2003 and I want to get a webserver going. So I installed Apache and it works on localhost but when I access it from my domain name from dyndns.com it doesn't work. I later found out that my ISP blocks ports 80 and 8080. I tried switching to the best of my ability to port 81 but I can't seem to get it right. Could someone explain how to do it if it is even possible.
I've tested ports 81 and 443 and they are opened.
I'm using TrendNet TEW-432BRP router.
 
I'm not sure about dyndns, but no-ip (http://www.no-ip.com/services/managed_dns/free_dynamic_dns.html) definitely allows you to specify a different port for the URL to point to - that's one half of the problem solved :)

Next you need to edit your httpd.conf file in your apache installation, and change two lines:

-"Listen 80" should be changed to "Listen 81"
- From memory there's a line starting with servername that ends in your port number, you'll need to change that as well.

That should do it - you should then have a web server running on port 81. :)
 
1st of all if you are using windows server 2003 why don't you just use IIS?

at any rate you can do it the way berry showed you OR where ever you purchased your domain go into the DNS records for
(www)or(root domain)[i'd do both]
http:// is root and http://www is (www)
and tell it to point it to an IP when you do this type in xxx.xxx.xxx.xxx:81 you can put whatever port after the colon just make sure its not used by another protocol THEN go into your router and tell it to look out for traffic from port 81 and forward it to my webserver
(also making sure the FW on the server is open to traffic on that port)


if your ISP is really hardcore about you not running a webserver they'll wonder why you are getting alot of incoming HTTP to your ipaddress.
 
user12, there is nothing wrong with running apache on Server 2003. In fact a personal feeling is that it is more secure than IIS.

Other than that I have to agree with everything that berry120 is saying.
 
nothing wrong with running apache, but IIS was just sitting their ready.

as far as personal feeling we'll keep it as just that.
 
Haha, to me that's like finding your Windows ME disk's and installing that on your brand new, top of the range machine instead of getting a newer operating system :p
 
Back
Top Bottom