Forum OpenACS Q&A: Response to Failure to connect to AOLServer from another PC

Surely the "enterprise" solution is not modifying config files every
time you move a notebook!  It is to use common standard services to
ensure you don't have to do that.

If you have 5000 employees, you probably have the resources to
implement split horizon DNS and integrate that with your DHCP servers,
so that as you move that notebook around it is given a new internal IP
address and then both internal and external DNS get modified to make
the server relocation 100% invisible to both internal and external
users, who continue to use the same FQDN for it as before.

In other words, solving this once properly will solve it not just for
that one machine, but for all machines in your enterprise.

This is not really an OpenACS issue, or even a Linux issue.  Step back
and improve the underlying network architecture, rather than relying
on ad hoc workarounds.