Trying to run Microsoft Web Server 2008
RetiredGuy
Newbie

I have a computer running Microsoft Web Server 2008 and cannot login from the Internet.

Everytime I try I keep getting the Actiontes Control Panel.

I am using the WAN IP address, and DHCP and have tried Port Forwarding via Actiontec Control Panel.

I am new at this and trying to set up an ecommerce site to sell my Daughter's Homemade Jewelery.

Help, I don't know where to turn to next. I also signed up with ZoneEdit.com for Domain Name Service.

0 Likes
Re: Trying to run Microsoft Web Server 2008
nospeedinternet
Enthusiast - Level 3

You have to set a static ip for your server and port forward to it. Then you use your wan ip with port numer on the end. 000.000.000:80  You shouldn't be seeing your router unless you have remote login turned on or are in DMZ mode.

If you have residential service you are not aloud to run a server on it. It is in the TOS.

Re: Trying to run Microsoft Web Server 2008
RetiredGuy
Newbie

I am using residential service, but the server should only be hit at most 10 times a week.

Would that still be not allowed????

Could I still try to set up per your instructions and at least see if I can get the server working and try out the nopCommerce web site software?????

Thank you so much for replying, I am not sure I understand all your instructions but I would like to give it a try.

0 Likes
Re: Trying to run Microsoft Web Server 2008
nospeedinternet
Enthusiast - Level 3

The port you would want to use is 80 but it is blocked by verizon. That is the port you use for http web server.

The next one you could use to get around that  is 443 and that uses https.

So you forward 443 to the static ip you give your server. By not having port 80 you are not going to get it to work the way you are wanting to. Port 80 is blocked for your protection.Smiley Wink

0 Likes
Re: Trying to run Microsoft Web Server 2008
dslr595148
Community Leader
Community Leader

That is 100% normal as you are on the LAN and type your WAN IP into your Browser Address Bar. When I am on the LAN side and type my Public WAN IP Address into the Browser, I get the same result as you. That is because I am on the LAN (trusted) side and not requesting from the WAN (untrusted) side. Now try it from a Web Proxy (Guardster.com) using your Public IP and see if you even get a response from your Public IP on Port 80.

0 Likes
Re: Trying to run Microsoft Web Server 2008
RetiredGuy
Newbie

Guardster.com says unable to connect to my WAN IP Address. Darn, world really like to learn more about how all of this works.

I have tried commercial hosting service to no avail, they only seem to work with very simple web sites. When I try to load nopCommerce software they poop out, or I don't know enough.

Tried GoDaddy and SoftSys and their tech support is not one that I can understand.

I'm about to give up......

thanks for the help, I least now I understand a little bit more. Trouble is I don't have much extra $$$$ to spend experminting..

0 Likes
Re: Trying to run Microsoft Web Server 2008
Mikhail
Enthusiast - Level 3

You don't need to have a static IP address. You can go with DynDNS.com -- look an appropriate topic in FIOS -- there is no difference how to set up DynDNS for DSL or FIOS. And you don't need to run your server on a port 80. You can chose any port you want in range 1025 - 65535 (1-1024 is a little bit problematic, but you can do it also, t least for some of them). So, if you setup your DynDNS as RetiredGuy.endofinterne.net and port to use is 12345 then you can reach you server using http://retiredguy.endofinternet.net:12345/

Tell me if you need to configure your router to open port.

Re: Trying to run Microsoft Web Server 2008
nospeedinternet
Enthusiast - Level 3

Has to have static IP address on his lan DynDNS will only see his wan ip and not his servers lan ip. If you don't set it static how is he going to port forward to a DHCP that will change ip addresses on restart?

Then when he does get it to work on a port other than 80 he will have to setup a webhop on DynDNS.

0 Likes
Re: Trying to run Microsoft Web Server 2008
Mikhail
Enthusiast - Level 3

@nospeedinternet wrote:

Has to have static IP address on his lan DynDNS will only see his wan ip and not his servers lan ip. If you don't set it static how is he going to port forward to a DHCP that will change ip addresses on restart?

Then when he does get it to work on a port other than 80 he will have to setup a webhop on DynDNS.


A little bit offtop. DHCP has two timeouts: one is for renewing of IP address, and another one is specifying how long to keep IP address if it's has not been renewed. Many companies have first one set to 4 hours and the second one set to a month. Moreover, there is static DHCP which means that IP address is allocated according to MAC address but the rest of configeration is going to be setup through DHCP, e.g. default gateway, DNS, WINS, etc (theere much more for DHCP protocol).

Now having said it, most home routers do not expose ssecond timeout but many of them have static DHCP.

DynDNS uses record of type "A" in DNS DB to resolve a heman readable format to IP, e.g. http://google.com to one of four:

72.14.204.99
72.14.204.104
72.14.204.103
72.14.204.147

Since DNS has 4 entries a simple method of round roibin could be used (and it's used) to balance load on four google webserveers. And name has nothing to do with ports. Notice, that URL starts with specification of protocol -- http://www.google.com. By default each protocol that could be specified there has a default port associated with it. You can find all well known associations at http://www.iana.org/assignments/port-numbers (this is ifficial registry), or, if you windows user then in %windir%\system32\driver\etc\services, or if you are *nix person then in /etc/services.

So, in reality, when you specifyng http://www.google.com it meams http://www.google.com:80/ and if specify ftp://www.google.com it would mean ftp://www.google.com:21, https://www.google.com means https://www.google.com:443. So you have always a way to specify non default port using :port syntax.

So, one solution is  http://mtweb.dyndns.org:12345. This solutution would work even if VZ filter out port 80. At the router you can map 12345 port to any other since most of current router implements PNAT (Port Network Address Translation) and not a pure NAT.