| MyndPhlyp 2004-11-30, 6:21 pm |
| I'm finally getting back to working with ASP pages and fired up Visual
Interdev v6 (from Visual Studio). I have it installed on both a Win2K Server
and a Win2K Workstation. SP5 has been applied to both and the VS Extensions
were installed on the Server.
I also have FrontPage 2003 installed on both machines with the FrontPage
2002 extensions on the Server. Using the FrontPage Server Extensions
Administrator web interface I've added myself as an Administrator for the
site in hopes of working around the problem. (I can always tighten security
later.)
I've also put on top of all that, somewhere along the line, SharePoint 'cus
MS isn't doing the FrontPage extensions any further than 2002. And just to
add a little more spice to the mix, there's also Office Server Extensions.
Running Visual Interdev from the Server, I can connect to the local web
services with no problems even as a mere mortal (non-Administrator).
Creating new subwebs is no problem. Editing existing ones is no problem.
Life is good ... except that I'm working at the Server and not at the
Workstation.
Over on the Win2K Workstation, I can't get Visual Interdev to authenticate
no matter who I log on as - local Administrator, Domain Administrator, or
the Domain Mere Mortal. (I'm usually running as a Domain User on the
Workstation rather than as a local user, but have Power User permissions.)
When creating a new project from the Workstation, I can select the web
server and get to the point where I can either create a new subweb or use an
existing one. When I try to get past that point I get challenged for a User
ID/Password and nothing will get me past that point.
The IIS logs show a 401 error, but not much else.
Here's the really funny part - I can access the local web with no problems
from the workstation if I use FrontPage 2003.
The local web site is actually a mirror of the Default Web Site. This was
necessary for using the FrontPage Server Extensions Administration tool. The
mirror points to the same wwwroot as the Default Web Site. It still runs on
Port 80, just with a different IP address.
Anybody out there with ideas on where the security needs to be tweaked so
that I can use Visual Interdev from my workstation?
|