Subdomain log-in problem

[FoulFoot]

I'm trying to create a subdomain web with Frontpage. I'm running into a
problem when the user attempts to log in to the subdomain, in order to
publish his web... when entering his username and password, the box simply
pops up again with the password field blank.

Using my root username and password, I'm able to access the subdomain fine.
It's simply the client usernames which aren't able to log in. FP extensions
have been set up on the subdomain, the subdomain has been created in the
control panel, the DNS entries are set properly, etc. Matter of fact, since
I'm able to log in and publish just fine using my root username and password,
I'm figuring that the problem rests solely with the FTP user account.

I created an FTP user in the control panel -- let's say "test". "Test" has
access only to mysite.com/sub.

Now, the instructions in the control panel indicate that to log in to an FTP
account, you need the whole username, in this case "(e-mail address removed)". I've
tried every combination I can think of with this username -- using just
"test", using "(e-mail address removed)", using the full domain path
("http://www.mysite.com/test", which is what one person suggested), etc etc.
No dice. Again, I can log in fine with the root account, just not this FTP
user.

One other individual over on the FrontPage Talk forums suggested that the
problem was that FP can't digest the "@" symbol in the username. His
solution: switch to Dreamweaver.

I'd like to avoid such a step. I'm open to suggestions here; I've been
reading about subwebs and the like, but they don't seem to address the core
of the problem, which is that I need to be able to have users (not just me)
logging in to their own webs.

Thanks for any help,

Scott

 

[FoulFoot]

Alrighty. I have just solved my own problem.

When Frontpage attempts to publish via "Frontpage or Sharepoint Services"
(as opposed to straight FTP), it doesn't give a rat's behind about what FTP
users you have or have not created. What you need to do:

Open the *main* site (http://www.mysite.com) *live* from the server: File /
Open Site / enter web address of the main site. You'll need to use your root
username and password.

Once the site is open, go to Tools, Server, Administration Home. This will
open your site administration screen (which, btw, I never knew existed until
now). If you've created your subdomain correctly via your website control
panel, you should see the subdomains (subwebs) listed at the bottom of the
screen. If you don't, you have other problems.

Click on the subweb name that you want to manage. It will open the
administration screen for that subweb. Select Manage Users, then *add* the
user(s) that you wish to have access to this subweb. Not knowing any better,
I've made my user an "Advanced Author", which seems to encompass doing
anything he needs to do to publish his website.

Now you can close all these screens. When the user attempts to publish his
web site, he should enter the URL as "http://www.mysite.com/sub" (some people
swear that "http://www.sub.mysite.com" will not work; others swear that it
does... I haven't tried it). Username is whatever you designated it as --
WITH NO "@" or domain name trailing it. Again, this is completely separate
from any FTP user you may have set up via your website control panel.

You're good to go. What may trip up many people attempting to replicate
this: you need to have FP extensions installed on the *subdomain* as well,
not just your main site. Many web hosts don't allow this or have the
capability to do this.

Scott

 

[Thomas A. Rowe]

Subdomains and FP Subwebs/sites are completely different functions and with no relationship to each
other. Subdomains are created with a DNS entry, whereas a FP subweb/site is a function of the FP
extensions.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WebMaster Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
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.
==============================================

 

[FoulFoot]

Subdomains and FP Subwebs/sites are completely different functions and with no relationship to each
other. Subdomains are created with a DNS entry, whereas a FP subweb/site is a function of the FP
extensions.

Partially true. The problem is that Frontpage itself doesn't understand the
difference, as evidenced by the fact that on the Administration Home page,
your subdomains (created by you via website control panel) are listed as
"subwebs", when in fact they're not FP subwebs at all. Both subwebs and
subdomains are really just *subdirectories*. Subwebs have the capability of
maintaining relative links to the main site. Subwebs (and correct me if I'm
wrong) do *not* have the capability of maintaining web space quotas, which is
particularly critical in my application. Also, the subweb must be created
(initially) by the web admin, not by the user.

Whatever the definition, for those people who are trying to make FP work
with *subdomains* (of which there's quite a few, going by the posts I've
read), the above steps should help.

Scott

 

[Thomas A. Rowe]

Correct FP doesn't work with subdomains, so the normal approach is the always publish to a subweb
under the root web, and then use DNS to point the subdomain to the subweb folder.

A subweb must be created by the admin/author account for the rootweb, which if the web host allows,
account holder can create subweb as needed, however some web host do not allow account to create or
have subwebs, and others will have to create the subwebs for the account holder.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WebMaster Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
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.
==============================================