Rob, Thanks for the reply. Thru some playing around and also breaking some things in the process I found out that DIIOP is some how tied to the "Fully qualified Internet host name" field on the server doc. On both of our Domino servers, this field had been set to the host name of the box. I changed DomApps and there was no longer a conflict. As a side note, I had also changed the field for our DomMail server. This broke some mail accounts that our ISP forwards to us. Thanks, Scott email@example.com Sent by: To: firstname.lastname@example.org domino400-admin@mi cc: drange.com Subject: Re: DIIOP on iSeries 12/21/2001 12:47 PM Please respond to domino400 Did you check the NOTES.INI on both servers? For example, let's pretend that domMail is 10.10.1.1 and domApps is 10.10.1.2. In the notes.ini for domMail you should see TCPIP_TcpIpAddress=0,10.10.1.1:1352 and in the notes.ini for domApps you should see TCPIP_TcpIpAddress=0,10.10.1.2:1352 On your 400's host table entries you should see: 10.10.1.1 domMail.yournotesdomain.COM 10.10.1.2 domApps.yournotesdomain.COM Server Doc, Internet Protocols, HTTP, Host name: domMail.yournotesdomain.COM Server Doc, Internet Protocols, HTTP, Bind to host name: enabled But most of this is for HTTP and it sounds like you have that beat into submission. There is an option in the server doc to pick different ports for IIOP. I hate using different ports - makes it nasty to configure clients. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.