How to test Groupwise POA SOAP connectivity

To test your Groupwise POA for SOAP connectivity, type the following from a workstation command prompt:  

telnet POAserverIP 7191
where POAserverIP is the IP address or FQDN of your post office agent.
You should receive a response similar to:
HTTP/1.0 500
Date: Mon, 09 Feb 2009 09:13:20 GMT
Server: Windows GroupWise POA 7.0.3
Content-Type: text/html
Pragma: no-cache
Connection to host lost
If the Telnet session does not connect, review the SOAP setup instructions for Groupwise.
You can also check SOAP connectivity via a web browser by viewing http://POAserverIP:7191/soap

3 Responses to “How to test Groupwise POA SOAP connectivity”

  1. Joshua Ostrom Says:

    Great blog.

    We’re a K-12 school district in northern Indiana running groupwise. We’re getting up and running w/SOAP + GW.

    When I navigate to http://OURGWIP:7191/soap, I get the following…

    HTTP/1.1 200 Date: Fri, 20 Mar 2009 09:55:03 GMT Server: NetWare GroupWise POA 8.0 Content-Type: text/xml; charset=utf-8 Content-Length: 268 Pragma: no-cache 59905 Bad parameter passed to a NCSP function.

    My concern is the 59905 error – is this typical to see when navigating to :7191/soap ?

    • Julie Says:


      Yes, that’s the normal response you’ll see when hitting that URL.


  2. Matt Says:

    When testing soap with telnet it response correctly. When testing with URL I am redirected to the POA’s web status page. Anybody know why it is doing this?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: