Re: Frontpage98

Misha (mishainsync.net)
Fri, 11 Jun 1999 23:42:08 -0500 (CDT)

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Next message: Ge' Weijers: "Re: potential ssh attack"
• Previous message: Di Phelan: "Blocking Offensive Material(??) with Firewall"
• Next in thread: Frank W. Keeney: "RE: Frontpage98"

Front Page Explorer uses port 80 for publishing in most cases (unless you
go the ftp route, which doesnt work very well). As long as you have
outbound HTTP allowed everything should work fine. Authentication is based
on NTLM though, and does not work through HTTP proxies. If the Firebox
does indeed have an HTTP proxy, you will need to add a bypass for your
ISP's server. Bypassing the proxy may only work for us though, because we
bypass it at the Foundry ServerIron switch that does layer 4 redirection
to the Cacheflow proxy.

I have seen some people overcoming the NTLM problem, under some voodoo
circumstances, by playing with proxy settings in Front Page Explorer.
Also, try logging on with "domain\user" rather than "user". This will
require knowing which NT domain or machine name your ISP is using.

Misha

On Mon, 7 Jun 1999, Colin Horsington wrote:

> Hello,
>
> Does anyone know what ports Frontpage 98 requires. We have recently
> installed a new Firewall (Watchguard Firebox II) and now cannot update
> our remote web page (hosted by an ISP). It stops at the authentication stage
> and so I can only assume that the ports it requires are blocked.
>
> Any suggestions....
>
>
> Cheers,
>
> Colin
>

• Next message: Ge' Weijers: "Re: potential ssh attack"
• Previous message: Di Phelan: "Blocking Offensive Material(??) with Firewall"
• Next in thread: Frank W. Keeney: "RE: Frontpage98"

This archive was generated by hypermail 2.0b3 on Sat Jul 17 1999 - 07:19:00 CDT