OK... will try that when I get back to the office... Will this IP need 
to be in my hosts file as well? That is, instead of (or in addition to):

127.0.0.1 localhost
127.0.0.1 www.VideoFortWorth.com
127.0.0.1 www.ProSportsResumes.com

I should have:

127.0.0.1 localhost
192.168.x.x www.VideoFortWorth.com
192.168.x.x www.ProSportsResumes.com

??

Christian Buczek wrote:
>
> *Von:* Joseph Morgan [mailto:josephmmor...@hotmail.com]
> *Gesendet:* Donnerstag, 26. März 2009 03:21
> *An:* users@httpd.apache.org
> *Betreff:* [us...@httpd] Mangled my Virtual Hosts
>
> I have somehow mangled my virtual hosts.. or so I think. I have two web
> sites http://www.ProSportsResumes.com, and
> http://www.VideoFortWorth.com, among others hosted on the same machine.
> If you visit http://www.VideoFortWorth.com, you'll see
> "ProSportsResumes" in the title, but the content of both are correct.
>
> My host machine is behind a router with port forwarding turned on. All
> incoming traffic on port 80 is forwarded to this machine.
>
> The "hostname" command returns "WEBHOST"
>
> My hosts file has entries like:
>
> 127.0.0.1 localhost
> 127.0.0.1 www.VideoFortWorth.com
> 127.0.0.1 www.ProSportsResumes.com
>
> My httpd.conf has this line as it should:
>
> # Virtual hosts
> Include conf/extra/httpd-vhosts.conf
>
> And my httpd-vhosts.conf has:
>
> NameVirtualHost 127.0.0.1:*
>
> ServerAdmin ad...@prosportsresumes.com
> DocumentRoot X:/webs/ProSportsResumes
> ServerName www.ProSportsResumes.com
>
>
>
> ServerAdmin ad...@videofortworth.com
> DocumentRoot X:/webs/VideoFortWorth
> ServerName www.VideoFortWorth.com
>
>
> Any ideas are appreciated.
> Joe Morgan
>
> ----------------------------------------------------------------------------------------------------------------
>
> ----------------------------------------------------------------------------------------------------------------
>
> Hi Joe,
>
> I´m not sure, but I mean you must enter another IP for your 
> NameVirtualHost.
>
> So your Domain has the public IP .64.202.189.170. That’s the router 
> with port forwarding to your webserver in a non-public net (like 
> 10.0.0.x / 192.168.0.y / ..)
>
> If your webserver have the IP 10.0.0.5, for example, you has to be 
> entered this IP for NameVirtualHost.
>
> Another idea is to catch all incoming requests on this webserver like 
> in this config:
>
> ..
>
> DocumentRoot (anyPath)
>
> ServerName www.ProSportsResumes.com
>
> ServerAdmin (anyMailAddy)
>
> ErrorLog (anyPath)
>
> CustomLog (anyPath)
>
> ..
>
> Hope one of these ideas works,
>
> Greats,
>
> Christian Buczek
>


_________________________________________________________________
Hotmail® is up to 70% faster. Now good news travels really fast.
http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_70faster_032009

Reply via email to