Hey Jason,
Called in to get the hotfox, noticed however that the status of the hotfix
was already fixed in SP1, which I did have in place.
THe tech at the other end of the support ticket for the hotfix, went thru a
few steps with me on some other KB's to see what was causing the issue.
1) If my local machine had the Proxy Settings in IE disabled, then Frontpage
published just fine. OR
2) If I didn't change IE, and disabled the Prompt for Authentication on
Outgoing Web Requests, then this too would work.
3) We looked into KB 250376 but this was geared to Frontpage 2000 and in my
registry there was not a key as described in the KB to force frontpage to use
proxy settings other than IE, this would have been the ideal way, but did not
work.
Finally the work around that we found was related to opening the rules up to
allow anyone anywhere at anytime...that is for port 80 and 443, since
Frontpage was having authentication issues, it appears that my machine was
attempting to get back out port 80, and yet only the user account was
permitted.
We added a rule for port 80- and 443 like my other rule, but rather than
have users/groups defined, I added client sets to be able to go out.
Works like a charm.
In theory, I guess when the ISP moved our public website from one server to
another, the authentication method changed, perhaps from a unix based server
to a windows 2003 server. While both are supporting Frontpage extensions, it
appears that when the authentication was coming from the ISP, ISA server was
getting confused. The credentials being passed were not the ones that were
expected...and so it started going in a loop, generating 1000's of log
entries for the Author.dll for both the user (me) and an anonymous entry,
which must have been my machine?
Looks to be working!
Thanks
J
"Jason Lu [MSFT]" wrote:
> Hi J,
>
> Thanks for posting.
>
> The 407 error in the error message you posted indicates "Proxy authentication required". It seems there are some authentication issues
> between the client and the proxy server.
>
> In the meantime, I noticed a known issue for such authentication issue when using an Automatic Configuration Script. Please reference the
> article below for the detailed information.
>
> 305204 Clients That Use an Automatic Configuration Script May Not Work Because
> http://support.microsoft.com/?id=305204
>
> If the web server and the client are in the same LAN, you can also try adding the FQDN name and NETBIOS name of the web servre into
> proxy bypass list and then publish to check the results. This can help identify whether this issue is related to proxy configuration.
>
> I hope the information helps.
>
> Regards,
> Jason Lu
> Microsoft Online Partner Support
>
> When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
>
>
Similar Threads
