M
mb12036
Hi-
When I attempt to publish a web/subweb/individual files on my
FrontPage server to another web/subweb on the same FrontPage server
using SSL I receive the following error:
Could not find a web server at 'servername' on port 443. Please check
to make sure that the web server name is valid and your proxy settings
are set correctly. If you are sure that everything is correct, the
web server may be temporarily out of service.
Server is running Windows 2000/IIS5/Service Pack 4.
FrontPage server extensions version 5.0.2.2623
Client is FrontPage 2002 SP-2 (similar error occurs with FrontPage
2000).
Using Self-Signed certs generated by Microsoft Certificate Services
The errors always appears in the middle of publishing one web to
another. When I begin the publish process, I authenticate to the
server without any problem, I see a directory listing as I should in
the publish web dialogue box, but invariably, the publish fails
(typically when the publishing status bar says "Processing Web
Updates") usually after copying some/most of the files successfully
from one location to another.
We require SSL to publish through our Firewalls. I am not a network
engineer but I believe the reasoning behind this was that the Cisco
PIX product gets hung up somehow on Microsoft Challenge/Response. I
have confirmed that we are able to publish through our firewalls
successfully (from a machine located on the same network) so I do not
believe them to be the issue. However, there are other network
devices enroute from our desktop user network to our public server
network where our firewalls are located that could be causing
problems.
Has anyone experienced this error message under any circumstances?
Regarding the problem of FrontPage and SSL, I have seen an abundance
of messages regarding older versions of FrontPage and their ability to
handle certificates over 40 bits, etc. This is not the same issue. I
suspect a potential problem with IIS/Certificate Services/the IIS
implemetation of SSL. I tend not to think it is a client issue
because it happens with every client 2002 or 2000 we try, but I can't
rule it out completely.
The icing on the cake is that I can successfully publish one web to
another using SSL internally using the actual server IP's within our
DMZ rather than going taking the long route through our user network
and back into our internet server network. So everything works fine
when you have a direct path to the server. All other FrontPage
functionality works fine over SSL also, by the way.
Sorry for the length of the note. Thanks in advance-
Matt
When I attempt to publish a web/subweb/individual files on my
FrontPage server to another web/subweb on the same FrontPage server
using SSL I receive the following error:
Could not find a web server at 'servername' on port 443. Please check
to make sure that the web server name is valid and your proxy settings
are set correctly. If you are sure that everything is correct, the
web server may be temporarily out of service.
Server is running Windows 2000/IIS5/Service Pack 4.
FrontPage server extensions version 5.0.2.2623
Client is FrontPage 2002 SP-2 (similar error occurs with FrontPage
2000).
Using Self-Signed certs generated by Microsoft Certificate Services
The errors always appears in the middle of publishing one web to
another. When I begin the publish process, I authenticate to the
server without any problem, I see a directory listing as I should in
the publish web dialogue box, but invariably, the publish fails
(typically when the publishing status bar says "Processing Web
Updates") usually after copying some/most of the files successfully
from one location to another.
We require SSL to publish through our Firewalls. I am not a network
engineer but I believe the reasoning behind this was that the Cisco
PIX product gets hung up somehow on Microsoft Challenge/Response. I
have confirmed that we are able to publish through our firewalls
successfully (from a machine located on the same network) so I do not
believe them to be the issue. However, there are other network
devices enroute from our desktop user network to our public server
network where our firewalls are located that could be causing
problems.
Has anyone experienced this error message under any circumstances?
Regarding the problem of FrontPage and SSL, I have seen an abundance
of messages regarding older versions of FrontPage and their ability to
handle certificates over 40 bits, etc. This is not the same issue. I
suspect a potential problem with IIS/Certificate Services/the IIS
implemetation of SSL. I tend not to think it is a client issue
because it happens with every client 2002 or 2000 we try, but I can't
rule it out completely.
The icing on the cake is that I can successfully publish one web to
another using SSL internally using the actual server IP's within our
DMZ rather than going taking the long route through our user network
and back into our internet server network. So everything works fine
when you have a direct path to the server. All other FrontPage
functionality works fine over SSL also, by the way.
Sorry for the length of the note. Thanks in advance-
Matt