• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1260
  • Last Modified:

Webaccess not able to make tcp connection to POA

Have a webaccess server with lots of connects to various POA. They all work. Created 2 new POA's, but webaccess cannot connect to these new ones.

On webaccess login screen error shows:

Your post office is unavailable. Please contact your system administrator.

With verbose logging enabled on webaccess agent the error during that login is:

unable to connect to poa using (ip xx.xx.xx.xx:1677)

Verfied configuration of agent settings good. Rebuilt po database.

Used gwip.nlm tool to test connectivity. Connections on 1677 good on all other poa's, the 2 new ones fail.

The GW clients can access the POA using 1677 and I verfied used TCPCON it is listening.
1 Solution
Sounds like you've checked all the basics.
You don't mention what version of GW + service packs are running so my answer may be generic:

What database versions are displayed on the new post offices?
(Open ConsoleOne. Under GroupWise System View, right click the Domain Object and POst Office Object and take Properties. Check the Database Version and it should be the same as your WA gateway)


Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now