Since remote desktop can resolve the name, your hosts file should be
correct. (192.168.1.2 myhost_com should work, although if you're
calling that host server now then you may want to add that at the
end of the line, after a space.)
Silly question: you *did* restart HTTPD after updating its
In the past I just had one machine. I ran apache on it. I modified the
hosts file to point aliases to the local box.
127.0.0.1 mysite_com So in my browser, I could type in: mysite_com
(underscore instead of dot) and bring up the site. Now I have a new box
running windows 7 that will be the
On 1/28/2010 1:15 PM, Matthew Smith wrote:
In the past I just had one machine. I ran apache on it. I modified the
hosts file to point aliases to the local box.
127.0.0.1 mysite_com So in my browser, I could type in: mysite_com
(underscore instead of dot) and bring up the site. Now I have a
I understand that. I should have made myself more clear.
I have modified the windows 7 machine host file to the following:
192.168.1.2 mysite_com
On Thu, Jan 28, 2010 at 1:26 PM, Programmer In Training
p...@joseph-a-nagy-jr.us wrote:
On 1/28/2010 1:15 PM, Matthew Smith wrote:
In the past I
On 1/28/2010 2:08 PM, Matthew Smith wrote:
I understand that. I should have made myself more clear.
I have modified the windows 7 machine host file to the following:
192.168.1.2 mysite_com
Only requests from the Windows 7 machine will resolve mysite_com to
192.168.1.2
Any other machine on
I understand that. I am only trying to access the server from the windows 7
machine.
To clarify:
server, 192.168.1.2, running apache
Windows 7 machine, hosts file modified to:
192.168.1.2 mysite_com
Windows 7 machine unable to load http://mysite_com/ in browser.
On Thu, Jan 28, 2010 at 2:12
On 1/28/2010 2:29 PM, Matthew Smith wrote:
I understand that. I am only trying to access the server from the
windows 7 machine.
Sorry, it sounded like you were trying to access from another machine.
To clarify:
server, 192.168.1.2, running apache
Windows 7 machine, hosts file modified
