Re: Frontpage 2003 publish web from remote iis 6.0 server to remote iis 6.0 server slow

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Thomas A. Rowe (tarowe_at_mvps.org)
Date: 02/09/05 

Date: Wed, 9 Feb 2005 09:22:40 -0500

Working with remote folder via drive letters or via FTP, and is not the same as working via http.
This is not an FP client issue, but a network issue. However since I noticed that you are using
Windows 2003 Server with the FP extensions, it is most likely a FP extensions configuration issue.
Drop me an email, if you have physical Admin. access on this server. 

-- 
==============================================
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
"Lloyd" <lloydholman@gmail.com> wrote in message 
news:af882ce0.0502090106.ef9e673@posting.google.com...
> Thomas,
>
> Thanks for your response, but I don't see how this can be a network
> issue, as I mentioned I have tried copying files both with FTP and
> using standard windows copy between shares, also all machines are
> within the same subnet and we are experiencing no other network issues
> in general. However one thing I have noticed is when the developers
> edit the production site live (as the development environment is not
> in place) using FP2003 and opening the site as a 'Local Site' they
> often complain of performance degredation in simply traversing the
> file structure and editing files, it's not unsual for them to wait
> minutes for FP to return the folder contents.
> This seems to "magically" sort itself out come around 17:30 when the
> majority of users have gone home, can general web server high usage
> impact FP editing as both methods are over HTTP?
> If so what is the best method to prevent this, is it simply a number
> of concurrent connections/connection timeout issue?
> Can FP Server Extensions be restarted or inactive connections be
> flushed?
> Do you think this could be manifesting the same issue I am having with
> publishing?
>
> Any guidance would be much appreciated
>
> Many Thanks,
>
> Lloyd
>
> "Thomas A. Rowe" <tarowe@mvps.org> wrote in message news:<ukas0HgDFHA.628@TK2MSFTNGP15.phx.gbl>...
>> This would be a network issue, suggest you post to the appropriate Windows newsgroup.
>>
>> When you publish a FP web from one server to another or from one location to another on the same
>> server, the process pass thru the client PC that initiated the publishing process.
>>
>> -- 
>> ==============================================
>> 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
>>
>> "Lloyd" <lloydholman@gmail.com> wrote in message
>> news:af882ce0.0502080430.150a8cf1@posting.google.com...
>> > All,
>> >
>> > I am experiencing transfer speed issues when attempting to publish
>> > from an IIS 6.0 website to another IIS 6.0 website running on a remote
>> > Windows 2003 server.
>> > The environment configuration/process I am trying to achieve is as
>> > follows (please be aware this is an Intranet environment):
>> >
>> > A number of web developers connect remotely from their XP Professional
>> > machines using the Frontpage 2003 'File>Open Site' dialog to a
>> > development website hosted on the development/staging server (Windows
>> > 2003 Server Standard, IIS 6.0).  Two websites are running on the
>> > development/staging server hosted with individual IP addresses, e.g.
>> > http://intranetdevelopment (192.168.9.182) and http://intranetstaging
>> > (192.168.9.188).
>> > When the developers try and publish their updates to the Staging
>> > website (hosted on the same server) publishing remotely from their
>> > machines using the 'Remote Web Site' and 'Remote Web Site Properties'
>> > options in Frontpage 2003 the transfer speed rarely increases from
>> > around 1KB/s, obviously this is completely unworklable and times out
>> > before completion, which is predicted at some 11+ hours.
>
>    <snip>
>    ....
>    </snip>
>
>> >
>> > Kind Regards,
>> >
>> > Lloyd H

Relevant Pages

  • Re: Hey Ronx are you available
    ... files...like a folder but with special other junk to make it work as a web. ... I guess one I figure this issue out then frontpage will start to work. ... install on Windows XP Pro with IIS 5 I must have missed the message the ... web server you cannot publish to the web server - there is no need to ...
    (microsoft.public.frontpage.programming)
  • Re: FP2003 Authoring problem
    ... > installed for Windows XP Pro and all Windows 2003 Servers, ... > Thomas A. Rowe ... > FrontPage Resources, WebCircle, MS KB Quick Links, etc. ... I copied that on to the new server. ...
    (microsoft.public.frontpage.client)
  • Re: FP2003 Authoring problem
    ... It you want to have a backup, use NTBackup, which is automatically installed for Windows XP Pro and ... Thomas A. Rowe ... FrontPage Resources, WebCircle, MS KB Quick Links, etc. ... I copied that on to the new server. ...
    (microsoft.public.frontpage.client)
  • Re: PWS - Adding a Db to my website
    ... Windows XP is not a suitable OS for hosting a website, ... If you are hosted on Linux then ... > set this up on XP, it would function as a Windows Server and I could ... >> Microsoft MVP - FrontPage ...
    (microsoft.public.frontpage.client)
  • Re: Publishing Error FP2003 to Remote site
    ... I have 2 machines running Windows XP Pro SP2, with automatic updates. ... Ron Symonds (Microsoft MVP - FrontPage) ... Created a new vurtual server ...
    (microsoft.public.frontpage.extensions.windowsnt)