Link problem

[Retired]

I have run a site called alongthewapsie.com on my own Windows XP machine
for about 5 years running Apache 1.3.12
DNS to the machine was 167.142.192.105
I decided to switch to my service provider's webhosting service.
I am familiar with their service since I am already hosting 3 other sites
through them.
I uploaded all the files, did the necessary paperwork. The propogation is
complete and everything is working fine.
But I still want to be able to link to my own machine.
If I type in http://167.142.192.105 it will indeed bring up my home page
on the old machine. But any of the links to folders on my machine will
fail and wind me up at google.
Example: http://167.142.192.105/fairbank fails (redirects)
If I type in a non existant name like http://167.142.192.105/joeblow then
I will get a 404 error.
So if I use a real folder name I get redirected to google but if I use a
phony name it yields a 404
http://alongthewapsie.com/fairbank works on the present hosting
But now... get this.
If you type in http://167.142.192.105/fairbank/index.html will work.
Why should I need the "index.html"?

I had no such problems the years I hosted it when DNS was pointing the
site to my IP. Why should it be any different when I access the machine
directly by IP?

Feel free to click on any of the above links to see what I'm talking
about.

The reason I want to be able to do this is so that I can put large movie
files (which would exceed my provider's capacity limit) on my own machine
and then link people to the directory the files are in.

For what it's worth, FTP will work but most people don't have FTP clients
nor understand FTP.

It's not the end of the world. Mainly I'd just like to know what caused
it to quit working by IP?

Also, in httpd.conf I have tried changing ServerName from
ServerName www.alongthewapsie.com to
ServerName http://167.142.192.105/
(As suggested in commented line just abobe ServerName)

No difference.

[Retired]

Post by Retired
I have run a site called alongthewapsie.com on my own Windows XP
machine for about 5 years running Apache 1.3.12
DNS to the machine was 167.142.192.105
I decided to switch to my service provider's webhosting service.
I am familiar with their service since I am already hosting 3 other
sites through them.
I uploaded all the files, did the necessary paperwork. The propogation
is complete and everything is working fine.
But I still want to be able to link to my own machine.
If I type in http://167.142.192.105 it will indeed bring up my home
page on the old machine. But any of the links to folders on my machine
will fail and wind me up at google.
Example: http://167.142.192.105/fairbank fails (redirects)
If I type in a non existant name like http://167.142.192.105/joeblow
then I will get a 404 error.
So if I use a real folder name I get redirected to google but if I use
a phony name it yields a 404
http://alongthewapsie.com/fairbank works on the present hosting
But now... get this.
If you type in http://167.142.192.105/fairbank/index.html will work.
Why should I need the "index.html"?
I had no such problems the years I hosted it when DNS was pointing the
site to my IP. Why should it be any different when I access the
machine directly by IP?
Feel free to click on any of the above links to see what I'm talking
about.
The reason I want to be able to do this is so that I can put large
movie files (which would exceed my provider's capacity limit) on my
own machine and then link people to the directory the files are in.
For what it's worth, FTP will work but most people don't have FTP
clients nor understand FTP.
It's not the end of the world. Mainly I'd just like to know what
caused it to quit working by IP?
Also, in httpd.conf I have tried changing ServerName from
ServerName www.alongthewapsie.com to
ServerName http://167.142.192.105/
(As suggested in commented line just abobe ServerName)
No difference.

I have now turned off the http server

[Harrie]

Retired said the following on 2012-04-02 09:26 (+0100):

<snip>

Post by Retired
But I still want to be able to link to my own machine.
If I type in http://167.142.192.105 it will indeed bring up my home page
on the old machine. But any of the links to folders on my machine will
fail and wind me up at google.
Example: http://167.142.192.105/fairbank fails (redirects)
If I type in a non existant name like http://167.142.192.105/joeblow then
I will get a 404 error.
So if I use a real folder name I get redirected to google but if I use a
phony name it yields a 404
http://alongthewapsie.com/fairbank works on the present hosting
But now... get this.
If you type in http://167.142.192.105/fairbank/index.html will work.
Why should I need the "index.html"?

I don't know, but try to fix your ServerName first (see below)

Post by Retired
I had no such problems the years I hosted it when DNS was pointing the
site to my IP. Why should it be any different when I access the machine
directly by IP?

Maybe cause the server is not configured to listen to an IP?

Post by Retired
Feel free to click on any of the above links to see what I'm talking
about.

Neither:

http://167.142.192.105/fairbank

.. nor:

http://167.142.192.105/fairbank/index.html

.. seem to work for me, that is, in both cases I get an empty page (no
redirect to google), but that might be because you you've turned of your
server.

Post by Retired
The reason I want to be able to do this is so that I can put large movie
files (which would exceed my provider's capacity limit) on my own machine
and then link people to the directory the files are in.
For what it's worth, FTP will work but most people don't have FTP clients [..]

Every windows box has an FTP client (type ftp in a Command Promt),
although I doubt that a lot of people use a command line ftp client. In
that case I recommend WinSCP.

Post by Retired
[..] nor understand FTP.

That might be true, but you could educate them. WinSCP is a simple
program, put up a page with instructions so people can make the right
session, that should solve it.

Post by Retired
It's not the end of the world. Mainly I'd just like to know what caused
it to quit working by IP?

Like I said, i think it's configured to listen to a name, not an IP address.

Post by Retired
Also, in httpd.conf I have tried changing ServerName from
ServerName www.alongthewapsie.com to
ServerName http://167.142.192.105/
(As suggested in commented line just abobe ServerName)
No difference.

Try: ServerName 167.142.192.105, but I guess that won't solve the
problem. Have a look into Apache IP-based Virtual Host Support:

http://httpd.apache.org/docs/current/vhosts/ip-based.html

[Harrie]

Post by Harrie
That might be true, but you could educate them. WinSCP is a simple
program, put up a page with instructions so people can make the right
session, that should solve it.

"session" should be "settings".