I am running FP2003 on XP with IIS5
I have published successfully to my local machine, but I cannot publish to
another machine on the network.
Both machines have the same setup.
When I try to connect to the network machine I get the user/password
dialogue, but the user field is greyed out with INTRANET\Guest in. INTRANET
is the name of the machine.
Can anybody help?

[ Post a follow-up to this message ]

IIS under XP doesn't allow for remote authoring via FP, you can only publish
 to/from with FP when
you are actually using the specific PC.

--
 ========================================
======
Thomas A. Rowe (Microsoft MVP - FrontPage)
 ========================================
======
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
 ========================================
======

"Mark" <mark@iwcoffice.org.nospam> wrote in message
news:19E42F48-633E-467C-B814-ED25E03900E7@microsoft.com...
>I am running FP2003 on XP with IIS5
> I have published successfully to my local machine, but I cannot publish to
> another machine on the network.
> Both machines have the same setup.
> When I try to connect to the network machine I get the user/password
> dialogue, but the user field is greyed out with INTRANET\Guest in. INTRANE
T
> is the name of the machine.
> Can anybody help?

[ Post a follow-up to this message ]

Thanks Thomas - that has saved me pulling my hair out all day...

"Thomas A. Rowe" wrote:

> IIS under XP doesn't allow for remote authoring via FP, you can only publi
sh to/from with FP when
> you are actually using the specific PC.
>
> --
>  ========================================
======
> Thomas A. Rowe (Microsoft MVP - FrontPage)
>  ========================================
======
> If you feel your current issue is a results of installing
> a Service Pack or security update, please contact
> Microsoft Product Support Services:
> http://support.microsoft.com
> If the problem can be shown to have been caused by a
> security update, then there is usually no charge for the call.
>  ========================================
======
>
> "Mark" <mark@iwcoffice.org.nospam> wrote in message
> news:19E42F48-633E-467C-B814-ED25E03900E7@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]