Association with database fails

[fl...@andrew.seeemmyou.eeedeeyou]

(This was also posted at
http://community.ingres.com/forums/viewtopic.php?t=758
so forgive the duplicate if you've seen it)

Server: W2k3/Ingres 9.0.4
Clients: Mostly windows XP running ingres net of multiple version

I *Think* that it's related to IPSEC reestablishing a connection.
Client errlog.log:
tmc18 ::[II\COMSVR\b0 , 00000000]: Tue Apr 17 15:07:53 2007 E_CL2784_GC_RECEIVE_FAIL An attempted network receive failed
tmc18 ::[II\COMSVR\b0 , 00000000]: socket() failed with operating system error 64 (The specified network name is no longer available.)

Server Errlog.log:
tmc129 ::[II\COMSVR\f8c , 00000002]: Tue Apr 17 15:07:53 2007 E_CL2784_GC_RECEIVE_FAIL An attempted network receive failed
tmc129 ::[II\COMSVR\f8c , 00000002]: socket() failed with operating system error 10054 (An existing connection was forcibly closed by the remote host.)

From the Server system event viewer (for every instance that i've checked) I see an eventID 541 IKE security association established within a second or two.

Am I crazy to think that this might be related?
I'm no ipsec expert, but i think this is what is happening:

client connects to server and negotiates IKE association.
this association is (I think) required to reestablish itself after a time.
ingres is being fussy and not retrying after the first failed connection, (which behind the scenes reestablishes connection)

I'm going to try a periodic ping from the client and see if that keeps
the connection open. If it does, I'll post results here.
(update the ping didn't work)

Alternately, is there a "times to retry" setting for ingres net?

(this all came to head since we recently went to an AIX running OI 2.0
to a Windows2K3 running 9.0.4.... "upgrading"--- HA!)

Any help appreciated...
Thanks!

--
flip
Just on the border of your waking mind, There lies - Another time,
Where darkness & light - are one. And as you tread the halls of sanity,
You feel so glad to be, Unable to go beyond. ELO - Twilight Prologue
In my email replace SeeEmmYou.EeeDeeYou with CMU.EDU

[fl...@andrew.seeemmyou.eeedeeyou]

fl...@andrew.SeeEmmYou.EeeDeeYou writes:
> I'm no ipsec expert, but i think this is what is happening:

Update: Fairly certain my hunch was correct, changing the server to
"client" mode for IPSEC seems to have ended the failing
associations.... Just following up in case someone else has this
problem...

--
flip