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
configuration?
Is there anything interesting in HTTPD's logs? If it thinks it should
be named "server" but couldn't resolve "server" then it may be having
some sort of identity crisis. Come to think of it, you don't mention
whether you defined "myhost_com" or "server" in etc/hosts *on the server*.
Does the server have a firewall configuration that lets remote desktop
through but not HTTP?
Does 'netstat -a -p tcp' show a listener on 192.168.1.2:80?
--
Mark H. Wood, Lead System Programmer mwood@xxxxxxxxx
Friends don't let friends publish revisable-form documents.
Attachment:
pgpvMYDk7TC6Y.pgp
Description: PGP signature
|