Sorry if this is old hat but I work for an ISP and have not been able
to find an answer through Google searches to help customers out with
this.

FrontPage caches its routes to the host that it had been previously
publishing to and won't let go of them. I have tried adding entries
to the hosts file with no success. I've had dns changed to reflect
host server changes. In each case the machine that's trying to
publish will ping the correct server but frontpage tries to publish to
the old host server.

This behaviour persists through full shutdowns and restarts, it's
really quite frustrating.

Remove the listing for *all* published locations from Network places.

Do a search for *.web ( with FrontPage closed )
and delete all files found.

Open a command window and type: ipconfig /flushdns
and then press enter. This will flush the dns resolver cache
( not the hosts file )


--
Steve Easton
MS MVP FrontPage
95isalive
This site is best viewed..................
...............................with a computer
"Tracy Wilborn" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Sorry if this is old hat but I work for an ISP and have not been able
> to find an answer through Google searches to help customers out with
> this.
>
> FrontPage caches its routes to the host that it had been previously
> publishing to and won't let go of them. I have tried adding entries
> to the hosts file with no success. I've had dns changed to reflect
> host server changes. In each case the machine that's trying to
> publish will ping the correct server but frontpage tries to publish to
> the old host server.
>
> This behaviour persists through full shutdowns and restarts, it's
> really quite frustrating.

now see, that's one i'll drag to the fp tips folder. ;-)

"Steve Easton" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Remove the listing for *all* published locations from Network places.
>
> Do a search for *.web ( with FrontPage closed )
> and delete all files found.
>
> Open a command window and type: ipconfig /flushdns
> and then press enter. This will flush the dns resolver cache
> ( not the hosts file )
>
>
> --
> Steve Easton
> MS MVP FrontPage
> 95isalive
> This site is best viewed..................
> ..............................with a computer
> "Tracy Wilborn" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Sorry if this is old hat but I work for an ISP and have not been able
> > to find an answer through Google searches to help customers out with
> > this.
> >
> > FrontPage caches its routes to the host that it had been previously
> > publishing to and won't let go of them. I have tried adding entries
> > to the hosts file with no success. I've had dns changed to reflect
> > host server changes. In each case the machine that's trying to
> > publish will ping the correct server but frontpage tries to publish to
> > the old host server.
> >
> > This behaviour persists through full shutdowns and restarts, it's
> > really quite frustrating.
>
>

;-)

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer

"chris leeds" <(E-Mail Removed)> wrote in message
news:uTDQs%(E-Mail Removed)...
> now see, that's one i'll drag to the fp tips folder. ;-)
>
> "Steve Easton" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Remove the listing for *all* published locations from Network places.
> >
> > Do a search for *.web ( with FrontPage closed )
> > and delete all files found.
> >
> > Open a command window and type: ipconfig /flushdns
> > and then press enter. This will flush the dns resolver cache
> > ( not the hosts file )
> >
> >
> > --
> > Steve Easton
> > MS MVP FrontPage
> > 95isalive
> > This site is best viewed..................
> > ..............................with a computer
> > "Tracy Wilborn" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > Sorry if this is old hat but I work for an ISP and have not been able
> > > to find an answer through Google searches to help customers out with
> > > this.
> > >
> > > FrontPage caches its routes to the host that it had been previously
> > > publishing to and won't let go of them. I have tried adding entries
> > > to the hosts file with no success. I've had dns changed to reflect
> > > host server changes. In each case the machine that's trying to
> > > publish will ping the correct server but frontpage tries to publish to
> > > the old host server.
> > >
> > > This behaviour persists through full shutdowns and restarts, it's
> > > really quite frustrating.
> >
> >
>
>