Subject: Re: Dialin connections from Windows 95 ???
To: None <port-arm32@NetBSD.ORG>
From: Stefan Voss <voss@yoda.in-berlin.de>
List: port-arm32
Date: 02/02/1997 10:05:39
In message <32F39CA5.5FB7@globalnet.co.uk>,
     Dave Millen wrote:

> 
> Does any one have RiscBSD set up to handle dialin connections from a
> WhineDoze machine?
> 
> I have Apache working well as a web server on my system, using the URL:
> 
> 	http://localhost/****.html
> 
> where '****.html' is the webpage filename.
> 
> All links are followed within the localhost domain and apache seems to
> work well, but I can't seem to make it available externally.

It's not a good idea to use the name "localhost" for network connections.
"localhost" usually resolves to the IP address 127.0.0.1 which denotes the
loopback interface (lo0) on every machine that can do TCP/IP.

Try and give your web server a real IP address and use this IP address to
connect to your web server. If your machine is meant to be visible to the
Internet then you have to get an official IP address from your provider.
If not, you can make up our own IP address (although there are recommended
addresses for such intranets, like the addresses in the class A net
10.0.0.0).

> 
> I have no problems with dialin connections as a terminal, the login
> procedure works and colleagues are able to work on the RiscPC while I am
> on the console with no problems, but all attempts to use a browser or
> ftp are unsuccessful.

Requests to 127.0.0.1 are always local. Connecting to 127.0.0.1 means
connecting to the local machine. When you started your web browser on your
Win95 machine and looked for a page at 127.0.0.1 (localhost) a request was
made to the Win95 maschine, not your web server.

> 
> cheers,
> Dave
> 

Regards,
   Stefan
   
-- 
Stefan Voss
(voss@yoda.in-berlin.de)