Compass Server, Robots, Binding to IP address

Question

Hello,
We're running iPlanet Compass server on top of iPlanet web server. We have been using the product for years now (back when it was called Catalog server). Anyway, we would really like the robot to bind to a specific IP address and use it when doing crawling.
For example, our machine may have a primary IP address of 1.2.3.4. However, using IP aliasing, we may also have an IP address of 1.2.3.5 on it (same subnet). We would like to have the robot use the IP alias address instead of the primary address when doing crawling.
Many servers allow for this ability (BIND and Postfix come to mind). This allows us to separate the 'service' from the server providing the service. If we need to move the service on to a different server, we simply migrate the IP address over to it the new server. The old server keeps its original IP address because it never had any connection to the service.
Does this capability exist for the robots? Please note that I am NOT referring to the web server portion; I understand that the web servers can be configured to bind to a specific IP address, and we do that with great success. However, the crawlers (robots) all seem to want to use the primary address of the machine.
I'm hoping there might be a setting in process.conf that we could add to enable this functionality.
Thanks for any pointers,
--Dave
Argonne National Laboratory

Answer 1

On other server (not problematic one) try;
netstat -ano
verify in the list if the ports 137, 138 and 139 are listed and listening or at least have
*.* in foreign column. If not make sure File and Printer Sharing
is bound to the connection.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.