After applying BM3.8.5_ir1: "IKESetupSocket: Unable to bind socket!", IKE not loading

Question

Hello,
I just applied the Interim Release 1 BM3.8.5 and rebootet the server after at
least several months of uptime when the patch files were applied - so it might be
related to 385_ir1; Or something went wrong during the last months of uptime that
way; that a reboot just caused the trouble to be revealed.
Well, on the next reboot after applying BM3.8.5_ir1 I got this on the IKE screen:
-------------------------- IKE SCREEN ----------------------------------
3-19-2008 12:53:41 pm IKESetupSocket: Unable to bind socket!
[snip empty lines]
<Press any key to close screen>
-------------------------- IKE SCREEN ----------------------------------
At this state these TCP NLMs were loaded:
TCP.NLM
Loaded from [SYS:SYSTEM\] on Mar 19, 2008 12:35:40 pm
(Address Space = OS)
Novell TCP/IP Stack - Transport module (Domestic)
Version 6.91.05 October 25, 2007
Copyright 1994-2007 Novell, Inc. All rights reserved. Patent pending.
TCPIP.NLM
Loaded from [SYS:SYSTEM\] on Mar 19, 2008 12:35:40 pm
(Address Space = OS)
Novell TCP/IP/IPSec Module (Domestic) NICI Enabled
Version 6.91.10 October 25, 2007
Copyright 1994-2007 Novell, Inc. All rights reserved
Patent pending Portions Copyright 1986-1995, RSA Data Security, Inc.
BSDSOCK.NLM
Loaded from [SYS:SYSTEM\] on Mar 19, 2008 12:35:40 pm
(Address Space = OS)
Novell BSDSOCK Module (Domestic)
Version 6.91.04 October 25, 2007
Copyright 1994-2007 Novell, Inc. All rights reserved.
As it's a socket error I thought that applying the latest TCP patch might help
out:
TCP681K, another reboot, but no change at all.
As IKE isn't loading server side all VNP functions are not operational.
PKIDIAG is without errors, if these certificates should interact with IKE as well
(I honestly have to state, that I don't know, if or if not these Certs interact
with IKE ...)
Anybody a quick solution? Otherwise I'll try to backrev to BM3.8.5 and the prior
TCP version.
Thanks for any input.
Regards, Rudi.
IT-Beratung Rudolf Thilo
Schweinfurter Str. 131
97464 Niederwerrn
t: +49 (0)9721/6464840
f: +49 (0)9721/6464841
m: +49(0)171/685 9 685

Answer 1

Hello,
after investigating in a totally wrong direction for many hours <doh!> I finally
back-rev.ed the lib files from c:\nwserver\!backup.lib and
sys:system\!backup.lib, after that was done the IKE had no trouble any more.
In the load sequence of the server's reboot NMAS had a load error that pointed in
that direction... (several DS*.NLMs in the LIB patch files)
I have a looger screen save file of both, a "trouble boot" and a clean boot after
removing the patch files. What I missed was to draw a config.txt of the trouble
state. :(
Quite interesting is the fact, that after may be 30 - 60 Minuntes of uptime the
BM had difficulties to access the C: drive:
----------------------------Logger Screen ------------------------------------
NetWare Configuration File Transfer Cache to DOS Error: 0x4
Registry rolling back to last known good registry file.
----------------------------Logger Screen ------------------------------------
Then no NLMs could be loaded any more at all: Neither DOS side, nor sys:system or
from anywhere else. Funny fact: With the already loaded toolbox a "DIR" was
presenting everything absolutely normal, DOS and SYS: side....
Well, the NBM-Rule-Container is restored now from tape, the filters.txt is as it
was before (seveal reboots) and with my 2nd. BM install I was painfully
remembered that there can be just one BM per container <grrr> ;) (nice design...)
Patches applied when the trouble showed up
NW6.5SP6
BM3.8SP5
plus the hotfixes available till Dec 2007
Finally I applied these (many hours ago >-O~ )
LIBCSP6B
NWLIB6K
WSOCK6N
TCP681K
BM3.8.5_ir1
.... in the timed order they were given to the public (I didn't check right now,
the order above isn't necessarily the right order I used.)
If someone should be interested in the logger.txt of both states, they are too
large for *one* posting here, drop me an email.
Regards, Rudi.
IKESetupSocket: Unable to bind socket!
IKE not loading any more
NMAS error in boot sequence
Error accessing registry files,
NLM load from all search paths impossible
IT-Beratung Rudolf Thilo
Schweinfurter Str. 131
97464 Niederwerrn
t: +49 (0)9721/6464840
f: +49 (0)9721/6464841
m: +49(0)171/685 9 685