Connecting Website to the network

Hello,

Are you using the correct IP or dns name?

First of all, we can find out if you can make a connection. In a cmd prompt
(on the remote computer), write this:

telnet 123.123.123.123 80

replace 123.123.123.123 with the actual IP of the webserver.
Do you get a connection? (if the cmd windows gets blank, you got a
connection).

1.1 If not, then there is something blocking access to the webserver. Make
sure that you have no firewall blocking access.

1.2 If you got a connection, please try to access the website in Internet
Explorer using <a style='text-decoration: underline;' href="http://123.123.123.123" target="_blank">http://123.123.123.123</a> (replace the IP with the IP of the
server). Do you get the website?
1.2.1 If you do, there is no problems, see 1.3.
1.2.2 If you do not, open IIS Manager, right click the Website and click
Properties. Make sure that you do not use any Host Header, and that the
website binds to all IPs. Then try to access the website again, that should
work.

1.3 Okay, so the IP works, but not the dns name. Then we know that IIS is
working fine, and that all ports are okay. But the DNS name is most likely
not correct configured. In a cmd prompt, write this:

nslookup domainname.com

replace domainname.com with the domain name you are using.

Do you get the correct IP?

1.3.1 If yes, then we have to check the host header in IIS. Does IIS accept
that host header? This should however not give you a "The page cannot be
displayed", so you should never be in this step.
1.3.2 If no, then we need to modify the DNS server. If your DNS server is
managed by someone else, tell them what you need, and they will do this for
you. If you manage the DNS server, and do not know how to configure it, i
recommend that you ask in the microsoft.public.windows.server.dns newsgroup.

--
Regards,
Kristofer Gafvert - IIS MVP
Reply to newsgroup only. Remove NEWS if you must reply by email, but please
do not.
<a style='text-decoration: underline;' href="http://www.ilopia.com/" target="_blank">http://www.ilopia.com/</a>


"Ken" <anonymous.DeleteThis@discussions.microsoft.com> wrote in message
news:C86A7E6A-81C8-4E21-9038-03BD8F7C6F1E@microsoft.com...
 > The Default.htm file works fine on the server hosting it. But from a
remote machine, the error message is: "The Page Cannot Be Displayed." Maybe
it's the security on IIS v6, Please help!<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Connecting Website to the network 

Kristofer:

The telnet connection to the server IP 69.106.1.145 or 146 port 80 failed. It must be a firewall issue. I'm still searching for solution.
 >> Stay informed about: Connecting Website to the network 

Yes, it must be a firewall, and is not related to IIS (since it is working
locally, we already know that IIS is listening on port 80).

Either you (or your company) have a firewall somewhere blocking access. Or,
your ISP blocks port 80, making it impossible to run a public webserver.

I hope you find the cause!

--
Regards,
Kristofer Gafvert - IIS MVP
Reply to newsgroup only. Remove NEWS if you must reply by email, but please
do not.
<a style='text-decoration: underline;' href="http://www.ilopia.com/" target="_blank">http://www.ilopia.com/</a>


"Ken" <anonymous.DeleteThis@discussions.microsoft.com> wrote in message
news:B57845C5-BEE7-4A36-8968-3DA429B2AF41@microsoft.com...
 > Kristofer:
 >
 > The telnet connection to the server IP 69.106.1.145 or 146 port 80 failed.
It must be a firewall issue. I'm still searching for solution.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Connecting Website to the network 

Hello Kristofer:

It appears that the router itself has not been properly configured. I'll be working on it during the weekend and post you on progress.
Great guy; thanks for your assistance.

Ken
 >> Stay informed about: Connecting Website to the network 

Kristofer, I read this thread and appreciated your explicit instructions. I think I might be in the same boat but need additional help. I am very new to IIS, but I have been using FrontPage for some time. This is the first time I am trying to let others in my company access a web site that I am "hosting" on my own PC (XP Pro). I can access the site on my own PC and on PCs connected to my LAN. I can not access the site from remote locations (I have tried from a few different locations).

For debugging, I now have my (dumb) DSL Modem connected directly into my PC. I have also turned off the internet connection firewall on all my network connections.

I tried the telnet step from a remote PC and the screen does go blank using port 443, but times out using port 80.

IE reports "Cannot find server or DNS Error" when trying to access via HTTP

Any suggestions would be greatly appreciated. Thanks!

Dru Welburn



"Kristofer Gafvert" wrote:

 > Hello,
 >
 > Are you using the correct IP or dns name?
 >
 > First of all, we can find out if you can make a connection. In a cmd prompt
 > (on the remote computer), write this:
 >
 > telnet 123.123.123.123 80
 >
 > replace 123.123.123.123 with the actual IP of the webserver.
 > Do you get a connection? (if the cmd windows gets blank, you got a
 > connection).
 >
 > 1.1 If not, then there is something blocking access to the webserver. Make
 > sure that you have no firewall blocking access.
 >
 > 1.2 If you got a connection, please try to access the website in Internet
 > Explorer using <a style='text-decoration: underline;' href="http://123.123.123.123" target="_blank">http://123.123.123.123</a> (replace the IP with the IP of the
 > server). Do you get the website?
 > 1.2.1 If you do, there is no problems, see 1.3.
 > 1.2.2 If you do not, open IIS Manager, right click the Website and click
 > Properties. Make sure that you do not use any Host Header, and that the
 > website binds to all IPs. Then try to access the website again, that should
 > work.
 >
 > 1.3 Okay, so the IP works, but not the dns name. Then we know that IIS is
 > working fine, and that all ports are okay. But the DNS name is most likely
 > not correct configured. In a cmd prompt, write this:
 >
 > nslookup domainname.com
 >
 > replace domainname.com with the domain name you are using.
 >
 > Do you get the correct IP?
 >
 > 1.3.1 If yes, then we have to check the host header in IIS. Does IIS accept
 > that host header? This should however not give you a "The page cannot be
 > displayed", so you should never be in this step.
 > 1.3.2 If no, then we need to modify the DNS server. If your DNS server is
 > managed by someone else, tell them what you need, and they will do this for
 > you. If you manage the DNS server, and do not know how to configure it, i
 > recommend that you ask in the microsoft.public.windows.server.dns newsgroup.
 >
 > --
 > Regards,
 > Kristofer Gafvert - IIS MVP
 > Reply to newsgroup only. Remove NEWS if you must reply by email, but please
 > do not.
<font color=purple> > <a style='text-decoration: underline;' href="http://www.ilopia.com/</font" target="_blank">http://www.ilopia.com/</font</a>>
 >
 >
 > "Ken" <anonymous DeleteThis @discussions.microsoft.com> wrote in message
 > news:C86A7E6A-81C8-4E21-9038-03BD8F7C6F1E@microsoft.com...
  > > The Default.htm file works fine on the server hosting it. But from a
 > remote machine, the error message is: "The Page Cannot Be Displayed." Maybe
 > it's the security on IIS v6, Please help!
 >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Connecting Website to the network