Listen 192.168.223.40:80> Listen 192.168.223.41:8080­>

<Virtualhost 192.168.223.40:80>>­ servername www.domain1.com> serveralias domain1.com, *.domain1.com> </Virtualhost>>

<Virtualhost 192.168.223.41:8080­>> servername www.domain2.com> serveralias domain2.com, *.domain2.com> </Virtualhost>

I intended have nothing listed for the Documentroot, since is only the> configuration phase, and it defaults the Apache documentation page.

I get successfully retrievet the default Apache page for DOMAIN1. VIA its> local address, as well as outside the LAN. But thus far haven't had any> success "seeing" my DOMAIN2 internally or otherwise.>

Does IP Aliasing require that another "network" address be used? (ie.> 192.168.223.40 & 192.168.224.40)

I suspect my issue lies within the IP> Aliasing.> I can successful ping the IP Alias address 192.168.223.41 locally. And> netstat reveals that both addresses/port are up & listening.

On Thu, 25 Dec 2003, David wrote:>

This is basically correct, except that the ServerAlias lines don't do> anything. They are only relevant in the case of name-based virtual hosts.>

You should put a DocumentRoot in both vhosts, even if it is the same as> the main server DocumentRoot.>

No.>

If that gives you the page, then apache is working fine. Try the same> thing again from another machine on the LAN to see if it is a networking> issue.>

Joshua.>

-------------------­--------------------­--------------------­----------> The official User-To-User support forum of the Apache HTTP Server Project.> See <URL:http://httpd.a­pache.org/userslist.­html> for more info.> To unsubscribe, e-mail: users-unsubscribe@h­ttpd.apache.org> " from the digest: users-digest-unsubs­cribe@httpd.apache.o­rg> For additional commands, e-mail: users-help@httpd.ap­ache.org