telnet localhost 80

hi.

i have a similar problem to the guy that recently posted.
i just bought a d link router and have server 2003 and 2
xp boxes connected. the connection is a comcast cable
modem.

i am attempting to put up a .NET web site but can't get
anybody to see it from the outside. I can't telnet to
192.168.0.1 on port 80 and am wondering if anybody
has a good solution?

I can ping my router
I can ping my cable modem's IP address (assigned by ISP).
I have yet to configure my domain controller but have
configured DNS (could this be the problem?).

anyway. pls. help. thanks in advance.

Hi,

I really hate to ask you, (I'm the guy who has the similar problem), but I have no choice:

Do you have to setup DNS even thought your domain is registered by a domain provider?

I have registered my domain with register.com and they are forwarding any requests to my static IP.

Reading your posted item, you mentioned DNS setup.

Let me know what else have you done?

Thank you in advance.

The 192.168 address is a private IP on your lan, can you telnet in from an outside location? If no, probably you haven't forwarded port 80 through the router to your IIS server.

thanks for your reply.
it isn't obvious to me how to do that.
i imagine it is done in the advanced section
of the routers configuration tools. there is
also a "tools" section with a "remote management"
section where i have added my server's ip address.
the router gave my iis server the IP 192.168.0.100.

i have tried various configurations but when i telnet
from "within" my network i get a hanging black box.
I am told that the same happens when somebody tries
to connect from the outside.

would you mind elaborating a bit?

thanks again.

First things first, from the server you should be able to open your web browser to http://localhost and get a web page served up by IIS. If not, fix this first so you know you have a working web server.

On my XP IIS, if I telnet localhost 80 I get a black empty screen, and after hitting Enter twice, I get the HTTP bad request and some other IIS identification headers back on the screen. If you want more than this via telnet you'll need to carefully type in valid HTTP in your telnet window.

Don't let the router assign your server IP address. Use a fixed IP for the server.

There should be a setting in your router for "port forwarding" or "virtual server" or something similar, with a screen that lets you identify an internal LAN IP address as the destination for incoming port 80 traffic.

One last thing, some cable and dsl ISP's block port 80 from ever getting to your router, if that's the case you're out of luck unless you change your internet plan, or run your web server on a non-standard port.

thanks for your reply.

I have done everything you suggested.

I found the virtual server info that you mentioned and have

forwarded my port 80 to my iis server. my server now has

a static ip and i called comcast and they told me that they

don't block on port 80 and are aware of people running small

web sites from their homes. I am wondering if anybody can

access my port 80 from the outside? my cable modem's IP address

is 68.63.160.161. also, a final question: how do i go about getting
the domain name i registered via network solutions to map to the
web site i created so people outside can simply type www.mydomain.com
and get my site? Apologies for the newbie questinos and thanks inadvance.

I got a "site under construction" page from your IIS no problem.

When you registered your domain, there was a place to identify two name servers that manage your domain name. I hate Network Solutions and I don't know if they offer DNS services or not, I use GoDaddy for registrations and I think GoDaddy does provide DNS service. My web hosting company takes care of the DNS for my domains. All I need to do is go to the registration account for the domain name and enter the DNS nameserver address my hosting company provided.

If you want or need to manage your own DNS you can use services like zoneedit.com that will let you do up to 5 domains free, or if you're really adventureous you can run your own DNS servers.

Now that you're on the air, you need to pay a lot of attention to security. Make sure your windows is up to date and all security patches are in place. Run a good firewall and Antivirus.

Doug, thanks a ton for your help. that is encouraging
news. THe router I have has a firewall, IIS has a firewall,
and the OS has Norton on it so, i am hoping that does the trick.
As for DNS name servers, I am using a small local ISP (www.cshore.com) and am
not doing it myself. The guy at cshore wants to be able to telnet to port
80 on my IIS server to be able to set me up. According to him, my box still
is rejecting his telnet requests. my cable modem is IP 68.63.160.161, my router
is IP 192.168.0.1 and my IIS Server is IP 192.168.0.100. I assume his telnet request
looks like this: "telnet 68.63.160.161 80". According to Comcast, they don't block on
Port 80. The the telnet service is alive and running under "services". And, I have forwrded
port 80 to the IIS box per our recent exchange. Do you have any idea what i might need to
do to allow outside telnet requests to be successful on port 80? Thanks again for your help.

Maybe there is some other proxy in between that prevents telnet. How about a web browser, does that connect to your IIS?

Doug,
Thanks for your help on this. I finally got it working -
Port 80 finally opened up (I think it was an IP naming prob)
and i got the ISP to set me up.
Thanks again for your help.

I'm glad you got it going.