Question : GroupWise: Unable to open connection, no response

Hi,

I am pretty new to NetWare and GroupWise, so if you need more information, just ask.  I am using NetWare 6 sp5, GroupWise 6.5.1 and eDirectory 8.7.3.

I have 1 Domain set up with 3 Post Offices (OfficeA + OfficeB + OfficeC), 3 POA's, an MTA and 1 Gateway (OfficeIA)

When I start up the server, I receive the following error message in the MTA NLM screen:

  DIS: MTA configuration loaded
  OfficeA: Post office now closed
  OfficeB: Post office now closed

On further examination, the log file displays:

  OfficeA: Post office now open
  OfficeB: Post office now open
  OfficeC: Post office now open
  MTP: OfficeA-ipS0: Unable to open connection, no response.  Address = [ip address], Port = 7101
  OfficeA: Post office now closed
  MTP: OfficeB-ipS0: Unable to open connection, no response.  Address = [ip address], Port = 7102
  OfficeB: Post office now closed

Please note, Office C appears to be starting up and working correctly.  This is one that has just been recently added to the system after OfficeA and OfficeB began to start playing up.  It is using the port number 7101.

Is there any way I can get these back online please?  I am not sure exactly how to do it.

One other thing as well, could you possibly tell me where to find the IMAP port number for each Post office? I am developing an application that connects to each post office through IMAP.

Thanks

Garry

Answer : GroupWise: Unable to open connection, no response

OK, I think I found your problem. But first, let me recommend that you NOT use the SYS: Volume to store GroupWise Domain databases or PO files. You should create a separate Volume for these things. The only GroupWise files that should reside on a SYS: Volume are the NLMs and the startup files (*.POA, *.MTA).

I've seen your problem when trying to get multiple agents running on a single machine using the same IP address for all agents. There's no technical reason you have to do it that way.

I would approach your issue from another direction. Create secondary IP addresses on your NIC. For example, you have 10.10.10.17, so add 10.10.10.18, 10.10.10.19 and 10.10.10.20...one IP address per agent.

Then, force each agent to bind to its specific IP address. Specifically, in each POA startup file (e.g. A.POA, B.POA, whatever), put the switch --> /IP-10.10.10.xx

where xx is the appropriate last octet of the IP address to which you want that specific agent bound. The settings in the NDS properties of the POA are *not* sufficient for this. You need to use this switch in the .POA file.

Same thing for the MTA.

Then change all the port numbers back to defaults.