GW6.5 SP3 Issues

[marvhuffaker]

Here are some issues I have seen since applying SP3 to my own GroupWise 6.5 installation. I have not installed it at any of my clients.

- Post office used to listen on all bound IP addresses. now it will only bind on the first IP address it detects. I need it to listen on two addresses like it used to.

- If the MTA loads before the POA loads, I have to restart the MTA to get it to recognize that the Post Office is open. Once it is open, it seems to be fine after that.

- Having trouble trying to manually force the listening IP address via the .POA config file.. It seems to ignore the settings and use the ones set in ConsoleOne. It should be the other way around.

Haven't had a lot of chance to mess with it yet...


Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting, Inc.

http://www.redjuju.com/support

 

[bytehd]

Marv,
my upgrade encountered similar issues.

I thought you and Matt had all the super-secret Novell
backdoor developer switches in your toolbag.

I also remembered that you can manually edit the
INETCFG file so the public interface binds first.

INETCFG complains about it when you reopen it, then its
all OK after a restart server, GWIA listens on public intf.

DID you use TCPCON to see if POA is open.

Ive used the delay 15 command in an NCF to let certain
NLMs load first.

my main problem now is that the main management PC's
ConsoleOne sees the wpdomain.db as an invalid database
if its on a novell server, but fine offt eh C: drive.

go figure.
I have the MTA/POA using UNC anyways.
SCSI channel is always faster than 100mbps...


George Walkey
Senior Geek in charge

http://www.insyncva.com

 

[marvhuffaker]

Well, it's not a matter of binding to the Public Ip address.. I need it bound to both private and public.. anyway, I got it fixed..

Rebuilt the databases.. Then I set the post office to listen on 0.0.0.0, which you may know means "All Bound IP Addresses".. (You'll see that in the TCP/IP Management in the Remote Manager web interface). Once I did that, it listens on both and works the way I want it to.

Yes I used TCPCON to see that it wasn't listening on certain addresses.. TCPCON doesn't tell you the POA is closed or open, but it tells you what ports are listening and on which IP addresses. Very useful in troubleshooting Groupwise AND other IP related problems.

Once I got that fixed, the problem with the MTA thinking the POA was closed -- well, it went away. Everything seems to be good now.

Marv

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting, Inc.

http://www.redjuju.com/support

 

[bytehd]

Then I set the post office to listen on 0.0.0.0

how?


George Walkey
Senior Geek in charge

http://www.insyncva.com