Hmmm. It's resolved. Not sure why, but I used the YaST interface in Suse
to walk through the "HTTP Server" configuration. No changes were made.

Apparently, it wasn't aware that I started the service by hand on the
command line, so the interface walked me through the entire
configuration. That's it, however. It seems as though there are some
reverse hooks between suse/yast into apache to get it running. Perhaps
it automatically makes a configuration change in the firewall?



Greg Tracy wrote:
>
> I just installed SuSe 10.1 with Apache 2.2, and right out of the box I
> am unable to connect to the web server from any machine other than
> localhost.
>
> For example, from the linux machine I can...
> - use 'wget http://localhost'
> - use 'http://192.168.x.x' from a browser running on the local machine
>
> I cannot use a browser for 'http://192.168.x.x' on a different machine
> on the LAN, however. It simply can't connect, and there is no evidence
> in the error log or access log.
>
> I do not believe this to be a router/connection issue. I have no problem
> connecting via SSH from other machines on the LAN.
>
> This seems so simple, yet why would the default configuration lock it down?
>
> Thoughts?
>