Joe Geiser wrote:
> Yes - this line could be the culprit, but based on what was said
> earlier, it sounds like the system does not have a host.domain
> name, which is only configurable with NMMGR.  To use the system
> in any type of network capacity, it needs an IP address and a
> host.domain name assigned to it via NMMGR.

Depending on exactly how httpd gets it's own hostname, it can be in
several places:

* DNS name in NMMGR (this is NOT the host.domain.org HP-style name,
  but the DNS name in the initial NS configuration screen),
* HOSTS.NET.SYS,
* reverse DNS from gethostbyaddr() call,
* etc

but the universal fix is /WWW/WWW/httpd_1.3/conf/httpd.conf file entry
for ServerName.

Jeff Kell <[log in to unmask]>