08-19-04 07:48 AM
FP requires in/out bound port 80 for http publishing.
--
========================================
======
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
http://www.ycoln-resources.com
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
========================================
======
To assist you in getting the best answers for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
"Andrew Harland" <andrew.harland@hudgp.org.au> wrote in message
news:8cc501c485aa$300ba2e0$a401280a@phx.gbl...
> Hi all,
>
> I'm trying to solve a publishing problem with FPSE2002.
> Everytime anyone tries to publish a page to our webserver
> (located in a DMZ), they get the following error:
>
> vermeer RPC packetError
> You are not authorized to view this page
> You do not have permission to view this page using your
> current user account. Please try the following:
> If you have another user account with a higher level of
> permission, click your browser's Back button to try
> again using that account.
> If you believe you should be able to view this page,
> contact the Web site administrator.
> method=open service:4.0.2.4715
> status=
> status=917505
> osstatus=0
> msg=The user '' is not authorized to execute the 'Author
> Pages' method.
> osmsg=
> The Local Security Authority cannot be contacted
>
> The users are able to directly connect to the webserver
> using Frontpage and change files with no problems. The
> above error message only appears when they try to publish
> a webpage or the whole website to the webserver, using
> Frontpage.
>
> All users who publish to this webserver have full Admin
> rights in FPSE2002.
>
> I've checked the configuration of FPSE2002 and it looks
> to be all correct. I'm thinking it may be something to do
> with FPSE2002 needing a specific port open from the DMZ
> to the LAN for it to work.
>
> Does anyone have any ideas on what is causing this error?
> Maybe the port number? A solution?
>
> Any help would be greatly appreciated.
>
> Thanks in Advance,
> Andrew.
[ Post a follow-up to this message ]
|