| Author |
Can't acces Site Administration
|
|
|
| Re: Windows 2003 Server, IIS 6.0 FPSE 2002
PROBLEM ENCOUNTERED:
When I click the Site Administration link, not matter what username or
password I enter whether it be the top lever admin SERVER\ADMINLOGIN or
www.mydomaine.com/ADMINLOGIN
http://www.mydomaine.com/_vti_bin/_...ge=webadmin.htm
Page Can Not Be Displayed
Sometimes I go back to click "Go to Site administration for
http://www.mydomaine.com ; again an instead of getting prompted for a login
it
goes directly to the browser
"Page Can Not Be Displayed"
I have many websites with FPSE and have not ever had this problem. I can
successfully access other site admin sections ok but just not this site or
any new ones I am trying to create.
PROCEDURE FOLLOWED:
I just installed FPSE on a new website from IIS and got the normal password
prompt for my SERVER\ADMINLOGIN account where I enter the password.
I am then properly sent to the "Extend virtual server with FrontPage Server
Extensions 2002" page where I successfully submit the same
SERVER\ADMINLOGIN.
Now from the "Server Administration" page I click on the "Administration"
link for the site I just extended and then go to the top of the page to
access the "Go to Site administration for http://www.mydomaine.com (Example
domain)
Thanks - Jody
| |
| Pier Paolo Ronzino 2005-04-28, 8:57 pm |
| I have the same problem.
Any ideas?
Pier Paolo Ronzino
"Jody" wrote:
> Re: Windows 2003 Server, IIS 6.0 FPSE 2002
>
> PROBLEM ENCOUNTERED:
> When I click the Site Administration link, not matter what username or
> password I enter whether it be the top lever admin SERVER\ADMINLOGIN or
> www.mydomaine.com/ADMINLOGIN
>
> http://www.mydomaine.com/_vti_bin/_...ge=webadmin.htm
>
> Page Can Not Be Displayed
>
> Sometimes I go back to click "Go to Site administration for
> http://www.mydomaine.com ; again an instead of getting prompted for a login
> it
> goes directly to the browser
> "Page Can Not Be Displayed"
>
> I have many websites with FPSE and have not ever had this problem. I can
> successfully access other site admin sections ok but just not this site or
> any new ones I am trying to create.
>
>
> PROCEDURE FOLLOWED:
> I just installed FPSE on a new website from IIS and got the normal password
> prompt for my SERVER\ADMINLOGIN account where I enter the password.
>
> I am then properly sent to the "Extend virtual server with FrontPage Server
> Extensions 2002" page where I successfully submit the same
> SERVER\ADMINLOGIN.
>
> Now from the "Server Administration" page I click on the "Administration"
> link for the site I just extended and then go to the top of the page to
> access the "Go to Site administration for http://www.mydomaine.com (Example
> domain)
>
>
> Thanks - Jody
>
| |
|
| Not sure what the issue was but what a frustrating problem! I was FINALLY
was able to create a new site and transfer all my files and I can now login
ok. The only thing that I did was stop and restart the "World Wide Web
Publishing Service". I have NO idea if that was the fix or not.
The really interesting thing is when I went to login, if I was prompted with
SERVERNAME\ADMINLOGIN I knew I would get the "Page cannot be displayed"
error. If the login was blank and just typed in my ADMINLOGIN I got in to
Site Administration just fine. Go figure!
I am VERY nervous about these kinds of flaky issues that seem to
mysteriously fix themselves. I really hated the idea that I might have to
uninstall and reinstall the FPSE for the entire server and muck up all my 20+
sites that were working just fine as that was what was suggested for me to do
by my tech staff. If any one has any input on this I am all ears! - Jody
"Pier Paolo Ronzino" wrote:
[vbcol=seagreen]
> I have the same problem.
> Any ideas?
>
> Pier Paolo Ronzino
>
> "Jody" wrote:
>
| |
| Pier Paolo Ronzino 2005-04-29, 6:06 pm |
| I'm trying this fix:
http://support.microsoft.com/defaul...kb;en-us;896861
"Jody" wrote:
[vbcol=seagreen]
> Not sure what the issue was but what a frustrating problem! I was FINALLY
> was able to create a new site and transfer all my files and I can now login
> ok. The only thing that I did was stop and restart the "World Wide Web
> Publishing Service". I have NO idea if that was the fix or not.
>
> The really interesting thing is when I went to login, if I was prompted with
> SERVERNAME\ADMINLOGIN I knew I would get the "Page cannot be displayed"
> error. If the login was blank and just typed in my ADMINLOGIN I got in to
> Site Administration just fine. Go figure!
>
> I am VERY nervous about these kinds of flaky issues that seem to
> mysteriously fix themselves. I really hated the idea that I might have to
> uninstall and reinstall the FPSE for the entire server and muck up all my 20+
> sites that were working just fine as that was what was suggested for me to do
> by my tech staff. If any one has any input on this I am all ears! - Jody
>
> "Pier Paolo Ronzino" wrote:
>
| |
|
|
| Sterling 2005-05-03, 5:52 pm |
| Did you install W2K3 SP1?
What version of FrontPage Extentensions?
5.0.2.5012 or 5.0.2.6738
"Jody" wrote:
> Re: Windows 2003 Server, IIS 6.0 FPSE 2002
>
> PROBLEM ENCOUNTERED:
> When I click the Site Administration link, not matter what username or
> password I enter whether it be the top lever admin SERVER\ADMINLOGIN or
> www.mydomaine.com/ADMINLOGIN
>
> http://www.mydomaine.com/_vti_bin/_...ge=webadmin.htm
>
> Page Can Not Be Displayed
>
> Sometimes I go back to click "Go to Site administration for
> http://www.mydomaine.com ; again an instead of getting prompted for a login
> it
> goes directly to the browser
> "Page Can Not Be Displayed"
>
> I have many websites with FPSE and have not ever had this problem. I can
> successfully access other site admin sections ok but just not this site or
> any new ones I am trying to create.
>
>
> PROCEDURE FOLLOWED:
> I just installed FPSE on a new website from IIS and got the normal password
> prompt for my SERVER\ADMINLOGIN account where I enter the password.
>
> I am then properly sent to the "Extend virtual server with FrontPage Server
> Extensions 2002" page where I successfully submit the same
> SERVER\ADMINLOGIN.
>
> Now from the "Server Administration" page I click on the "Administration"
> link for the site I just extended and then go to the top of the page to
> access the "Go to Site administration for http://www.mydomaine.com (Example
> domain)
>
>
> Thanks - Jody
>
| |
| Pier Paolo Ronzino 2005-05-03, 5:52 pm |
| yes SP1
The newly created are 5.0.2.6738
"Sterling" wrote:
[vbcol=seagreen]
> Did you install W2K3 SP1?
> What version of FrontPage Extentensions?
> 5.0.2.5012 or 5.0.2.6738
>
> "Jody" wrote:
>
| |
| Sterling 2005-05-03, 5:52 pm |
| The new Frontpage Extensions is what is causing the issue.
I've already reported this to Microsoft, until they resolve this problem
this is what needs to be done.
The following is how I discovered to fix the issue.
This is my reply to the newsgroups.
The fix:
Download Microsoft's IIS 6.0 Resource Kit.
Open "Metabase Explorer" (Use Metabase Explorer at your own risk)
Browse to W3SVC
Click on the ID number for the website containg the FrontPage Extensions
i.e (/LM/W3SVC/1)
On the right side of the split screen, right click on an empty row at the
bottom,
choose "New String Record" >>
Record Name or Identifier = NTAuthenticationProviders
Click OK
Right click on the new record and choose "Properties"
On the "Value" Tab input the following:
Value Data: NTLM
On the "General" Tab Input the following:
UserType: File
Attributes: Inheritable
Close "Metabase Explorer", open "IIS", goto the FrontPage Administration for
the current website you just edited. You can now login w/ user credentials.
Evidently this is an issue with the new version of FrontPage Extensions.
Until MS resolves this, I guess we can update manually until then.
Sterling S
"Pier Paolo Ronzino" wrote:
[vbcol=seagreen]
> yes SP1
> The newly created are 5.0.2.6738
>
>
> "Sterling" wrote:
>
| |
| Pier Paolo Ronzino 2005-05-03, 8:47 pm |
| Can you explane the difference between the fix I've found and yours?
"Sterling" wrote:
[vbcol=seagreen]
> The new Frontpage Extensions is what is causing the issue.
> I've already reported this to Microsoft, until they resolve this problem
> this is what needs to be done.
>
> The following is how I discovered to fix the issue.
> This is my reply to the newsgroups.
>
> The fix:
> Download Microsoft's IIS 6.0 Resource Kit.
> Open "Metabase Explorer" (Use Metabase Explorer at your own risk)
> Browse to W3SVC
> Click on the ID number for the website containg the FrontPage Extensions
> i.e (/LM/W3SVC/1)
> On the right side of the split screen, right click on an empty row at the
> bottom,
> choose "New String Record" >>
> Record Name or Identifier = NTAuthenticationProviders
> Click OK
>
> Right click on the new record and choose "Properties"
> On the "Value" Tab input the following:
> Value Data: NTLM
>
> On the "General" Tab Input the following:
> UserType: File
> Attributes: Inheritable
>
> Close "Metabase Explorer", open "IIS", goto the FrontPage Administration for
> the current website you just edited. You can now login w/ user credentials.
>
> Evidently this is an issue with the new version of FrontPage Extensions.
> Until MS resolves this, I guess we can update manually until then.
>
> Sterling S
>
>
> "Pier Paolo Ronzino" wrote:
>
| |
| Sterling 2005-05-03, 8:47 pm |
| No difference, they both accomplish the same goal.
There is always more than one way to skin a cat.
"Pier Paolo Ronzino" wrote:
[vbcol=seagreen]
> Can you explane the difference between the fix I've found and yours?
>
> "Sterling" wrote:
>
| |
|
| Is there a posting somewhere as to what was added/fixed in the new FPSE
5.0.2.6738 version that comes with SP1? Is there any updates directly from MS
support as to the status on the issues from SP1 on 2003 server with IIS6 and
FPSE 2002?
Thanks
"Pier Paolo Ronzino" wrote:
[vbcol=seagreen]
> yes SP1
> The newly created are 5.0.2.6738
>
>
> "Sterling" wrote:
>
| |
| Michael Middleton 2005-05-06, 5:57 pm |
| The Registry change (KB896861) makes the whole server universally stop
checking the loopback adapter for a domain name to match the web site's
domain name (clearly not meant for a public web server with many virtual
domains).
The Metabase change is a webroot-by-webroot tweak telling a given site
to use NT Lan Manager auth (which doesn't check the loopback as part of
Kerberos calculations since it ain't Kerberos).
If you have a handful of webs defined on a server, probably the Metabase
solution is safest (it lets other things use Kerberos, especially if the
box is part of an AD). If you have a few hundred there and the box does
nothing else and is not part of AD ... (my situatation)... then probably
http://support.microsoft.com/defaul...kb;en-us;896861
Mike
http://www.m13.net
[vbcol=seagreen]
> Can you explane the difference between the fix I've found and yours?
>
> "Sterling" wrote:
>
>
| |
| Douglas Ward 2005-05-09, 7:47 am |
| Thank you for this information. The only IIS Resource Kit I can find is
version 6.0 for Windows 2003 Server. Is there a version available for
Windows 2000 Server? Will we know when Microsoft patches this? I can't
create new websites unless I uninstall the server extensions and go back
to FPSE 2000. Thanks for all of your help!
Sterling wrote:[vbcol=seagreen]
> No difference, they both accomplish the same goal.
> There is always more than one way to skin a cat.
>
> "Pier Paolo Ronzino" wrote:
>
>
|
|
|
|