Web Hosting Talk







View Full Version : FrontPage and ISP's


jgriff64
03-26-2002, 06:53 PM
Hello, does anyone have or has had problems with their ISP's not supporting publishing with FrontPage. I am trying to find out if this is a big problem or not. If it is a big problem I would like to compile a list of ISP's that do not support this.
ISP's do not seem to know themselves that there is a problem.
Also can anyone confirm if (UK) NTL support publishing with frontpage. (Any one using NTL and manage to publish with frontpage)
Many thanks in advance.

tazd9t9
03-27-2002, 03:55 AM
Hi, your webhost should tell you whether they support FrontPage extensions or not as part of basic package information when you sign up.
If you mean isp's free space then i know that AOL for one doesnt support the extensions.
However don't forget that you can use frontpage without extensions at all, which is what i sometimes use. This only gets rid of a few of the dynamic site content options.

jgriff64
03-27-2002, 04:45 AM
Sorry I think you have missunderstood me. What i mean is some ISP's do not allow transmission over the port needed to authenticate FrontPage publishing. Hence people not being able to publish using FrontPage http:// publishing to their webhost.

tazd9t9
03-27-2002, 04:54 AM
oh ok, sorry about that. well i am pretty sure AOL UK block it

SI-Chris
03-27-2002, 06:44 AM
Originally posted by jgriff64
Sorry I think you have missunderstood me. What i mean is some ISP's do not allow transmission over the port needed to authenticate FrontPage publishing. Hence people not being able to publish using FrontPage http:// publishing to their webhost.
FrontPage publishes on port 80 (unless your Web server has some screwy configuration to publish on another port, which would be a circumstance I've yet to encounter).

I'm not sure what Internet Service Providers are blocking port 80, but if yours is you aren't getting your money's worth.

jgriff64
03-27-2002, 06:56 AM
It is actually the NTLM authentication port which the ISP's do not allow access to not port 80.
This can be sorted by changing the authentication type needed by the server.
Our webservers do not have screwy configuration