FrontPage and Windows Server 2003 Small Business Server

J

Jeff Teel

I have am trying to update a FrontPage Extended web that is outside of my
local Windows 2003 network. The extensions on the web seem to be working OK
because the pages display correctly and when viewing the different subwebs
they all work fine. I am just not able to update this web with files from my
local copy or I can't setup a web folder in My Network Places using the
wizard because I never get a logon screen. I'm using XP Pro as an OS,
FrontPage 2003 for a web editor. Has anyone had any problems like this?

Thanks
Jeff
 
R

Ronx

Just because you can see the pages does not mean the extensions are running.
FP extensions only come into play when some server side activity is
required - form processing, hit counter, publishing, opening a web in
FrontPage, etc. - displaying a page does not require the extensions unless
it contains an active, browsetime component.

If you give a URL to the web, it can be checked to see if the extensions are
installed, and if the problem with logging on is limited to you or your
network.
 
J

Jeff Teel

Hi Ron.....
Thanks for your response. Here is the URL of the problem web site:
http://teelcountry.com I'm thinking that the extensions are OK because I
have some .asp pages (they are form pages that gather data to post in a
database) that load and I'm able to Open the FrontPage Server extension
administrator pages..(I have them bookmarked in my browser.) At times even
the FP extension pages seem like they don't respond to requests like they
did when my LAN was Per to Per. If I bypass the Windows Server and connect
directly to my router things work fine. I can open the live copy of the web
with FrontPage and I can push a local copy of a fie to the web server OK.
With those symptoms it would point directly to the Windows Small Business
Server but I manage another FrontPage web site that is hosted by the same
company and I can connect to it just fine (the same way I'm trying to do
with the teelcountry.com web). I've been gleaning the web for any answers
that I can find and it seems like an unusual problem since it is not
consistent as far as just not working at all, be it through the Small
Business Server or bypassing the SBS and dialing in!! But hopefully we can
find something to get this resolved. If you question anything else let me
know. I've typed so many things in user groups that I can't remember what
I've said where.

Thanks
Jeff
 
R

Ronx

Note that ASP pages do not use the FrontPage extensions.
Your site does have working extensions, I was asked to login when editing
with FrontPage.

The differences between the authorisation of one site (that works with FP)
to another could be that one uses Basic authorisation, and the other
requires Integrated Windows authorisation, which may be blocked by the SBS.
This authorisation method can be set on individual IIS virtual servers.

Or the SBS firewall might need tweaking.

I suggest posting to one of the windows.server or windows.server.sbs
groups.
 
J

Jeff Teel

Hi Ron

I have posted on the Microsoft.public.windows.server.sbs and have
communicated with Jim Behning about my problem. He suggested setting up one
workstation as a secure NAT client and giving that a try. I followed his
instructions but haven't had any luck getting things to work with the
problem site. I guess the bright side is it didn't affect the site that I
have been able to publish to! Am I correct in thinking that the Web Host
will have to make that change? I don't believe that I've seen anything like
that in the FrontPage server extension Administration pages.

I don't know if you are the person to ask but I'll ask anyway. Would it be
better for me to ask my web host to change the authorization (if that turns
out to be what is causing this) or should I tinker with my network to make
things work. I am using ISA 2000 that came with my SBS system and there may
be something in there that is causing this behavior. I am still green with
Window Server and ISA as well but the SBS news group has been a great
help......along with your assistance.

Thanks
Jeff
 
R

Ronx

I know very little about Windows 2003 or SBS, and nothing about ISA, so I am
not the person to continue this with. Old posts (many months ago) in these
FrontPage groups suggest that ISA is a fickle beast, in that some users have
no problems and others have to turn it off to enable FrontPage

The authorisation method is a setting in the IIS property sheets, so it will
be the host that makes the change.
 
J

Jeff Teel

It does appear to be raising it's ugly head for sure!! I'm not going to give
up easily though. There has to be an answer for this. Hopefully I will find
that it is something easy to fix.
Thank you again for your suggestions. I have contacted my web host and asked
what authentication was being used. I asked if it was the same for both web
sites but they haven't responded to that question. They just asked if I
wanted it changed. It was set for Integrated Windows authentication. I do
know that the two sites reside on different servers so there could be a
difference in how they are set up for authentication. I also know that the
problem site is not actually on the server that my domain name is pointing
to. They moved it to another server at one point because of a problem and
did the routing internally.
Thanks Again
Jeff
 
B

Bazoz

Hi Jeff,

Have you found the answer to your issue? I’m having a similar problem. If I
try to publish to an external website through SBS2003 I get an error ‘Unable
to open URL’ and a list of possible causes. If I bypass the server all is ok.

I manage over 20 websites, and the only ones that I can publish through
SBS2003 are those hosted on Unix boxes.

Regards
Bazoz
 
Top