Re: Can't use "www" url to webserver on LAN?
From: Ohmster (bigbigkitty_at_ohmster.com)
Date: 02/27/04
- Next message: Ohmster: "Re: Can't use "www" url to webserver on LAN?"
- Previous message: Ohmster: "Re: Can't use "www" url to webserver on LAN?"
- In reply to: Rich Grise: "Re: Can't use "www" url to webserver on LAN?"
- Next in thread: Ohmster: "Re: Can't use "www" url to webserver on LAN?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 26 Feb 2004 23:13:56 GMT
"Rich Grise" <null@example.net> wrote in
news:p9r%b.11430$921.4715@nwrddc02.gnilink.net:
> When you use www., you're telling the browser to go look for host (or
> virtual host) www on domain <myfqdn>. Try putting the hostname of the
> web server box in front of the fqdn. (e.g., I'd have
> thunderbird.myfqdn.net, vehicle.myfqdn.net, and entheos.myfqdn.net.)
> I've found that sometimes omitting the www in IE, it picks it up,
> presumably because that's what the server calls itself.
>
> It sounds like, in this case, things are opposite of what we've all
> come to expect - i.e. IE is doing exactly what it's told, and your
> other browsers "take care of it for you." ;-)
>
> Good Luck!
> Rich
Hmmm, the machine name before the FQDN does not work in either lynx or IE. If
I try to do this with IE, I get page not found. If I try this with lynx on
win32, I get "looking for "www.<machine name>.<FQDN>.com", "guessing", and
then a dial up prompt appears, asking me if I would like to dial out to try
this. WTF, I am on a LAN fer Chrissakes, what the heck do I want to dial out
for?
Look here:
http://ohmster.com/~ohmster/test/snap011.gif
(You can probably use the www prefix for this URL, I cannot on my LAN since
switching to PPPoE) This is the setup page at no-ip.com for my domain. See
how www.ohmster.com points to my current IP. Also the domain itself, the
prefix "mail", and the prefix "ftp" all point to my current IP.
Look here:
http://ohmster.com/~ohmster/test/snap013.gif
This is what I sometimes see if I use the "www" prefix when viewing my site
from my LAN on IE. That is an MS server page and not an apache page, I am
almost sure of it unless IE is generating the page, it might be.
Look here:
http://ohmster.com/~ohmster/test/snap014.gif
This is the current site as it should appear and probably would appear if you
do it from your location with the www prefix as in:
http://www.ohmster.com
If I try http://ohmster.ohmster.com with IE or anything else from my LAN (The
actual hostname of the machine is "ohmster", the domain is "ohmster.com".), I
get a 400 error, page not found. If I try this with win32 lynx, lynx
indicates that "www.ohmster.ohmser.com" cannot be found, and then starts
"guessing" with www.ohmster.ohmster.com, www.ohmster.ohmster.net,
www.ohmster.ohmster.edu, etc. and finally dumps me at "yeah.net" and give up.
Also while all of this guessing is going on, I get windows prompts for me to
use my dial up to connect to the internet. This never, ever happend with
bridged ethernet. Man this PPPoE really does suck.
Don't get me wrong, I am not whining to the newsgroup, I am really puzzled by
this and some of the finest networking brains in the world can be found in
comp.os.linux.networking (This is very true). It would be really neat to
figure this out and try to find out what is really going on here. Oh sure, I
can just shup up and drop the www prefix but what is really important to me
is the learning process and the "how come this is happening". I hope that
some of you would like to come along for the ride to see if we can beat this
bugger down and figure it out or is it just that PPPoE really does suck the
big one and I have to live with it or dump my ISP and pay the extra 10 bucks
a month to swith to a decent provider in my area that gives a static IP
address, real bridged ethernet, and really does not care what you do with it
as long as you don't but the hell out of everyone running spam factory, etc.
I have never had this issue before in years of running the same setup, the
only difference now is that I no longer have a bridged ethernet connection
and have to run Roaring Penguin now to connect with linux. The Westell
Wirespeed 2100 modem will log in for me and act as a router if I wish but
then I will get stuck with a NAT address and cannot run servers anymore.
There is another option in that the modem will also offer an IP
passthrough/DMS (whatever that means) but I am not sure how this would work.
The modem setup that is done with http://launchmodem or http://192.168.1.254.
This is done in XP by setting your TCP to DHCP, fully automatic. For some
reason, this never works in linux with any browser. Clicking on the IP
passthrough will offer to set this up on the current PC (drop down box lists
corrent PC or "User configured PC" and offers this message:
"NOTE: If “User Configured PC” is selected, a local PC must be manually
configured to have the Passthrough IP address."
I dunno if this will "fix" this issue, I really do like having full control
of the network connection directly from linux. This is a bitching modem
though, you can do all sorts of port forwarding and routing with this modem.
Thanks for jumping in there and offering this explanation Rich, I really do
appreciate it and this oppertunity to discuss this with my peers and my
mentors. Thank you all for such wonderful support and discussions. You guys
are the *best* in the whole world!
-- ~Ohmster
- Next message: Ohmster: "Re: Can't use "www" url to webserver on LAN?"
- Previous message: Ohmster: "Re: Can't use "www" url to webserver on LAN?"
- In reply to: Rich Grise: "Re: Can't use "www" url to webserver on LAN?"
- Next in thread: Ohmster: "Re: Can't use "www" url to webserver on LAN?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
