Secure web page viewable internally but not externally

Hello,

I have IIS 6.0 with one CGI application on the default web site.
We are using Windows 2003 Server. The page is viewable from
within the company network, but not by the general public.
An identical system using Windows 2000 Server is viewable
by the general public. I'm fighting with the network people
on this. I think port 443 isn't allowed to the server.
The page has an SSL Certificate and all other validation
turned off. What else could cause this to happen?

David

Re: Secure web page viewable internally but not externally

"Eagle" wrote in message
news:rOdGr40LMPU3-pn2-pd51Hd0PxNXh@localhost...
> Hello,
>
> I have IIS 6.0 with one CGI application on the default web site.
> We are using Windows 2003 Server. The page is viewable from
> within the company network, but not by the general public.
> An identical system using Windows 2000 Server is viewable
> by the general public. I'm fighting with the network people
> on this. I think port 443 isn't allowed to the server.
> The page has an SSL Certificate and all other validation
> turned off. What else could cause this to happen?
>
> David

How many IPs are you using for these two sites on this server? You realize
that you can only have certificate per IP address right? [ONE IP, ONE
virtual web, ONE certificate. If you want more you need TWO IPs, TWO
virtual webs, TWO certificates.. and so on.]

Well if it's viewable internally from a different machine and you have two
IPs on the network card and using one each per web with certificate, that
rules out the server being the problem.

You either dont have port 443 open on that IP (you would have to have one IP
open with 443 for the other server) on the Firewall, or there is some sort
of other problem with network address translation.

Can you view the file externally on that site in HTTP mode?

The network guys are wrong, this is not a server problem, it's a network
problem.

Re: Secure web page viewable internally but not externally

On Thu, 31 Jan 2008 16:07:12 UTC, ".._.." <.._..@yourmom.mil> wrote:

> The network guys are wrong, this is not a server problem, it's a network
> problem.

They finally agreed it was on their end. Only port 80 was open to
the server, even though I told them only an HTTPS conversation
would be active.

Thank you,

David