Problem publishing

[Guest]

I published my first web. However there is a problem, (naturally). I
couldn't get the site to publish to the server with an http: url from my
remote computer, so after it was published (copied)to the server, I published
it again using http://localhost. It published with a http:// address, and
the search feature on my home page worked. However, when I tried to open it
from my remote computer using the url http://localhost address the page was
not available, but when I called it up from the server using that address it
came up.

What did I do wrong? We are using FrontPage2000, with FP2000 server
extensions on Windows XP Professional, version 2002, with service pack 2, and
IIS

Ron

 

[Guest]

Responses (which are questions, mostly) interspersed...

I published my first web. However there is a problem,
(naturally). I couldn't get the site to publish to the
server with an http: url from my remote computer, so after
it was published (copied)to the server,

Whoah! You were sitting at the remote computer, right?

And you tried publishing from there to the server's http:// URL?

And that failed? If so, how? What was the messge?

But if publishing failed, how did you copy it to the server?

I published it again using http://localhost.

Using http://localhost how?

Sitting at the remote computer and opening http://localhost ?

Sitting at the server and publishing to http://localhost ?

Something else?

It published with a http:// address, and the search
feature on my home page worked.

Again, sitting where, and publishing from what location to what location?

However, when I tried to open it from my remote computer
using the url http://localhost address the page was
not available, but when I called it up from the server
using that address it came up.

So, sitting at the remote computer, you browsed http://localhost plus a path
and filename, and the exact error message was "Not Available." Is that right?

And then you sat at the server and browsed http://localhost plus the same
path and filename and the page appeared. Is that right?

What did I do wrong?

You described the problem in very unclear terms. Please answer the questions
or try again from scratch.

We are using FrontPage2000, with FP2000 server extensions
on Windows XP Professional, version 2002, with service
pack 2, and IIS

Ron

Jim Buyens
Microsoft MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Windows SharePoint Services Inside Out
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

 

[Guest]

When I first published, I was sitting at the remote computer. I typed
http:// and browsed to a file on the server, and clicked publish. It
published, but not to a http:// URL, instead it published to our network with
a \\ address. The FP server extensions did not work. I then republished the
web from the server using http://localhost. It published with the
http://localhost URL, the FP server extensions worked and I can reach it on
the browser using that address from the server, but I can't reach it from my
remote computer, I get a page not available message.

 

[Tom Pepper Willett]

You don't browse to a file on the server to publish. You use the full
http:// path to the server you are publishing to.

For example, if you are publishing to a computer that has the server
extensions installed, such as yours, you use the address http://localhost or
http://mycomputername


--
===
Tom "Pepper" Willett
Microsoft MVP - FrontPage
---
About FrontPage 2003:
http://office.microsoft.com/home/office.aspx?assetid=FX01085802
FrontPage 2003 Product Information:
http://www.microsoft.com/office/frontpage/prodinfo/default.mspx
Understanding FrontPage:
http://msdn.microsoft.com/office/understanding/frontpage/
===
| When I first published, I was sitting at the remote computer. I typed
| http:// and browsed to a file on the server, and clicked publish. It
| published, but not to a http:// URL, instead it published to our network
with
| a \\ address. The FP server extensions did not work. I then republished
the
| web from the server using http://localhost. It published with the
| http://localhost URL, the FP server extensions worked and I can reach it
on
| the browser using that address from the server, but I can't reach it from
my
| remote computer, I get a page not available message.
|
| "Jim Buyens" wrote:
|
| > Responses (which are questions, mostly) interspersed...
| >
| > "ron b" wrote:
| >
| > >
| > > I published my first web. However there is a problem,
| > > (naturally). I couldn't get the site to publish to the
| > > server with an http: url from my remote computer, so after
| > > it was published (copied)to the server,
| >
| > Whoah! You were sitting at the remote computer, right?
| >
| > And you tried publishing from there to the server's http:// URL?
| >
| > And that failed? If so, how? What was the messge?
| >
| > But if publishing failed, how did you copy it to the server?
| >
| > > I published it again using http://localhost.
| >
| > Using http://localhost how?
| >
| > Sitting at the remote computer and opening http://localhost ?
| >
| > Sitting at the server and publishing to http://localhost ?
| >
| > Something else?
| >
| > > It published with a http:// address, and the search
| > > feature on my home page worked.
| >
| > Again, sitting where, and publishing from what location to what
location?
| >
| > > However, when I tried to open it from my remote computer
| > > using the url http://localhost address the page was
| > > not available, but when I called it up from the server
| > > using that address it came up.
| >
| > So, sitting at the remote computer, you browsed http://localhost plus a
path
| > and filename, and the exact error message was "Not Available." Is that
right?
| >
| > And then you sat at the server and browsed http://localhost plus the
same
| > path and filename and the page appeared. Is that right?
| >
| > > What did I do wrong?
| >
| > You described the problem in very unclear terms. Please answer the
questions
| > or try again from scratch.
| >
| > > We are using FrontPage2000, with FP2000 server extensions
| > > on Windows XP Professional, version 2002, with service
| > > pack 2, and IIS
| > >
| > > Ron
| >
| > Jim Buyens
| > Microsoft MVP
| > http://www.interlacken.com
| > Author of:
| > *----------------------------------------------------
| > |\---------------------------------------------------
| > || Microsoft Windows SharePoint Services Inside Out
| > || Microsoft Office FrontPage 2003 Inside Out
| > ||---------------------------------------------------
| > || Web Database Development Step by Step .NET Edition
| > || Microsoft FrontPage Version 2002 Inside Out
| > || Faster Smarter Beginning Programming
| > || (All from Microsoft Press)
| > |/---------------------------------------------------
| > *----------------------------------------------------
| >
| >
| >

 

[Guest]

Can you use http://localhost if you are publishing from a remote computer?
If not, how do you find the computer name? There is a network identification
number on the server but that doesn't seem to work.

 

[Guest]

The host name "localhost" points to the special IP address 127.0.0.1, which
*always* means "this computer" (the one you're sitting at).

The DNS name to use for publishing is the same one you use for browsing. So,
if you can browse the page http://www.example.com/myweb/myfolder/mypage.htm,
and http://www.example.com/myweb is a FrontPage-based Web site, then you
would publish to http://www.example.com/myweb.

If you don't know the server's DNS name, you can sometimes publish to its IP
address, such as to http://192.168.1.1/myweb. However, this will fail if the
server is using hostnames to differentiate multiple virtual Web servers.

If you know the server's IP address but not the corresponding DNS name, open
a command window, then type nslookup <enter> 192.168.1.1 <enter> where
192.168.1.1 is the IP address. Here are some typical results

C:\>nslookup

192.168.1.1

Server: myserver.example.com
Address: 192.168.1.1

exit

C:\>

If you still can't figure out the correct name, you'll probably need to
contact your server or network administrator.

Jim Buyens
Microsoft MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Windows SharePoint Services Inside Out
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------