|
| Help, after apply idm351Adir2, can not connect to RL |
 |
Mon, 12 May 2008 14:46:02 GMT |
Hello everyone:
I applied idm351 engine patch 3 and idm351adir2 last week. Now 2 of my
ad drivers can not connect to remote loader. The strange thing is that
I have 5 drivers in my environment and 3 of them are working properly.
I am thinking it should not be an engine problem, otherwise non of the
AD drivers would work. My environment is idm351 on red hat linux.
Remote loader and Ad driver shim are on window 2003. Any help is
appreciated.
Thanks
====Here is the error I got from remote loader==============
DirXML: [05/12/08 16:22:19.54]: Loader: Verifying command port...
DirXML: [05/12/08 16:22:20.88]: Loader: Verifying driver can be
loaded...
DirXML: [05/12/08 16:22:21.24]: ADDriver: Driver::destroy
DirXML: [05/12/08 16:22:21.58]: ADDriver: Driver::~Driver()
DirXML: [05/12/08 16:22:21.94]: Loader: Initializing SSL encryption...
DirXML: [05/12/08 16:22:40.18]: Loader: Waiting for DirXML to connect
on 'TCP server socket, port 8993, address XX.XXX.XX.XXX, using SSL'...
DirXML: [05/12/08 16:23:05.36]: Loader: OpenSSL socket: AES256-SHA
SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1
DirXML: [05/12/08 16:23:05.71]: Loader: Authenticating with DirXML...
DirXML: [05/12/08 16:23:05.71]: Loader: Received 'handshake' document
DirXML: [05/12/08 16:23:05.86]:
DirXML Log Event -------------------
Thread = Connection Monitor
Level = warning
Message = Handshake timeout: closing connection
DirXML: [05/12/08 16:23:06.41]: Loader: XML Document:
DirXML: [05/12/08 16:23:06.77]: Loader: null document
DirXML: [05/12/08 16:23:07.11]: <handshake version="1.0">
<password><!-- content suppressed --></password>
</handshake>
DirXML: [05/12/08 16:23:07.47]: Loader: Authentication handshake
failed: Wrong command type
DirXML: [05/12/08 16:23:08.18]:
DirXML Log Event -------------------
Thread = Subscriber Channel
Level = error
Message = Authentication handshake failed: Wrong command type
==========Here is partial error from engine with level 3
trace===========
[05/12/08 09:23:04.688]:AD_EA PT:Remote Interface Driver: Opening
connection...
[05/12/08 09:23:04.689]:AD_EA PT:Remote Interface Driver: Client socket
parameters: hostname = 'XXX.com' port = 8993 KMO = 'IDMAD' SSL mode =
server
[05/12/08 09:23:04.690]:AD_EA PT:Remote Interface Driver: Creating an
NTLSSocket
[05/12/08 09:23:05.300]:AD_EA PT:Remote Interface Driver: NTLS Socket:
AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256)
Mac=SHA1
[05/12/08 09:23:05.302]:AD_EA PT:Remote Interface Driver: Connection
established...
[05/12/08 09:23:05.302]:AD_EA PT:Remote Interface Driver: Sending...
[05/12/08 09:23:05.303]:AD_EA PT:
<handshake version="1.0">
<password><!-- content suppressed --></password>
</handshake>
[05/12/08 09:23:05.304]:AD_EA PT:Remote Interface Driver: Document
sent.
[05/12/08 09:23:05.313]:AD_EA :Remote Interface Driver: Waiting for
receive...
[05/12/08 09:23:05.666]:AD_EA ST:SubscriptionShim.execute() returned:
[05/12/08 09:23:05.667]:AD_EA ST:
<nds dtdversion="3.5" ndsversion="8.x">
<output>
<status level="retry" type="remoteloader">No
connection to remote
loader</status>
</output>
</nds>
[05/12/08 09:23:05.669]:AD_EA ST:Requesting 30 second retry delay.
[05/12/08 09:23:05.669]:AD_EA ST:
DirXML Log Event -------------------
Driver: \PRODIDVTREE\esc\idm\driverset\AD_EA
Channel: Subscriber
Status: Retry
Message: Code(-9006) The driver returned a "retry" status
indicating that the operation should be retried later. Detail from
driver: No connection to remote loader
[05/12/08 09:23:05.696]:AD_EA ST:Received state change event.
[05/12/08 09:23:05.698]:AD_EA ST:Transitioned from state
'%+C%14CStarting%-C' to state '%+C%14CRunning%-C'.
[05/12/08 09:23:05.699]:AD_EA ST:Successfully processed state change
event.
[05/12/08 09:23:05.700]:AD_EA ST:Submitting identification query to
subscriber shim:
[05/12/08 09:23:05.701]:AD_EA ST:
<nds dtdversion="3.5" ndsversion="8.x">
<source>
<product version="3.5.11.20080307 ">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<query event-id="query-driver-ident" scope="entry">
<search-class class-name="__driver_identification_class__"/>
<read-attr/>
</query>
</input>
</nds>
[05/12/08 09:23:06.706]:AD_EA ST:SubscriptionShim.execute() returned:
[05/12/08 09:23:06.707]:AD_EA ST:
<nds dtdversion="3.5" ndsversion="8.x">
<output>
<status level="retry" type="remoteloader">No
connection to remote
loader</status>
</output>
</nds>
--
vivianfeng
------------------------------------------------------------------------
vivianfeng's Profile: http://forums.novell.com/member.php?userid=1654
View this thread: http://forums.novell.com/showthread.php?t=327525
|
| Post Reply
|
| Re: Help, after apply idm351Adir2, can not connect to RL |
 |
Mon, 12 May 2008 15:48:20 GMT |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Does it connect w/out SSL? Have you verified the certs for this
particular driver if they are different from the drivers that do work?
Good luck.
vivianfeng wrote:
| Hello everyone:
|
| I applied idm351 engine patch 3 and idm351adir2 last week. Now 2 of my
| ad drivers can not connect to remote loader. The strange thing is that
| I have 5 drivers in my environment and 3 of them are working properly.
| I am thinking it should not be an engine problem, otherwise non of the
| AD drivers would work. My environment is idm351 on red hat linux.
| Remote loader and Ad driver shim are on window 2003. Any help is
| appreciated.
|
| Thanks
|
| ====Here is the error I got from remote loader==============
| DirXML: [05/12/08 16:22:19.54]: Loader: Verifying command port...
| DirXML: [05/12/08 16:22:20.88]: Loader: Verifying driver can be
| loaded...
| DirXML: [05/12/08 16:22:21.24]: ADDriver: Driver::destroy
| DirXML: [05/12/08 16:22:21.58]: ADDriver: Driver::~Driver()
| DirXML: [05/12/08 16:22:21.94]: Loader: Initializing SSL encryption...
| DirXML: [05/12/08 16:22:40.18]: Loader: Waiting for DirXML to connect
| on 'TCP server socket, port 8993, address XX.XXX.XX.XXX, using SSL'...
| DirXML: [05/12/08 16:23:05.36]: Loader: OpenSSL socket: AES256-SHA
| SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1
| DirXML: [05/12/08 16:23:05.71]: Loader: Authenticating with DirXML...
| DirXML: [05/12/08 16:23:05.71]: Loader: Received 'handshake' document
| DirXML: [05/12/08 16:23:05.86]:
| DirXML Log Event -------------------
| Thread = Connection Monitor
| Level = warning
| Message = Handshake timeout: closing connection
| DirXML: [05/12/08 16:23:06.41]: Loader: XML Document:
| DirXML: [05/12/08 16:23:06.77]: Loader: null document
| DirXML: [05/12/08 16:23:07.11]: <handshake version="1.0">
| <password><!-- content suppressed --></password>
| </handshake>
| DirXML: [05/12/08 16:23:07.47]: Loader: Authentication handshake
| failed: Wrong command type
| DirXML: [05/12/08 16:23:08.18]:
| DirXML Log Event -------------------
| Thread = Subscriber Channel
| Level = error
| Message = Authentication handshake failed: Wrong command type
|
|
| ==========Here is partial error from engine with level 3
| trace===========
| [05/12/08 09:23:04.688]:AD_EA PT:Remote Interface Driver: Opening
| connection...
| [05/12/08 09:23:04.689]:AD_EA PT:Remote Interface Driver: Client socket
| parameters: hostname = 'XXX.com' port = 8993 KMO = 'IDMAD' SSL mode =
| server
| [05/12/08 09:23:04.690]:AD_EA PT:Remote Interface Driver: Creating an
| NTLSSocket
| [05/12/08 09:23:05.300]:AD_EA PT:Remote Interface Driver: NTLS Socket:
| AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256)
| Mac=SHA1
|
| [05/12/08 09:23:05.302]:AD_EA PT:Remote Interface Driver: Connection
| established...
| [05/12/08 09:23:05.302]:AD_EA PT:Remote Interface Driver: Sending...
| [05/12/08 09:23:05.303]:AD_EA PT:
| <handshake version="1.0">
| <password><!-- content suppressed --></password>
| </handshake>
| [05/12/08 09:23:05.304]:AD_EA PT:Remote Interface Driver: Document
| sent.
| [05/12/08 09:23:05.313]:AD_EA :Remote Interface Driver: Waiting for
| receive...
| [05/12/08 09:23:05.666]:AD_EA ST:SubscriptionShim.execute() returned:
| [05/12/08 09:23:05.667]:AD_EA ST:
| <nds dtdversion="3.5" ndsversion="8.x">
| <output>
| <status level="retry" type="remoteloader">No
connection to remote
| loader</status>
| </output>
| </nds>
| [05/12/08 09:23:05.669]:AD_EA ST:Requesting 30 second retry delay.
| [05/12/08 09:23:05.669]:AD_EA ST:
| DirXML Log Event -------------------
| Driver: \PRODIDVTREE\esc\idm\driverset\AD_EA
| Channel: Subscriber
| Status: Retry
| Message: Code(-9006) The driver returned a "retry" status
| indicating that the operation should be retried later. Detail from
| driver: No connection to remote loader
| [05/12/08 09:23:05.696]:AD_EA ST:Received state change event.
| [05/12/08 09:23:05.698]:AD_EA ST:Transitioned from state
| '%+C%14CStarting%-C' to state '%+C%14CRunning%-C'.
| [05/12/08 09:23:05.699]:AD_EA ST:Successfully processed state change
| event.
| [05/12/08 09:23:05.700]:AD_EA ST:Submitting identification query to
| subscriber shim:
| [05/12/08 09:23:05.701]:AD_EA ST:
| <nds dtdversion="3.5" ndsversion="8.x">
| <source>
| <product version="3.5.11.20080307 ">DirXML</product>
| <contact>Novell, Inc.</contact>
| </source>
| <input>
| <query event-id="query-driver-ident" scope="entry">
| <search-class class-name="__driver_identification_class__"/>
| <read-attr/>
| </query>
| </input>
| </nds>
| [05/12/08 09:23:06.706]:AD_EA ST:SubscriptionShim.execute() returned:
| [05/12/08 09:23:06.707]:AD_EA ST:
| <nds dtdversion="3.5" ndsversion="8.x">
| <output>
| <status level="retry" type="remoteloader">No
connection to remote
| loader</status>
| </output>
| </nds>
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIKGbD3s42bA80+9kRAnVnAJ47yaganAxKsRPXcLMN6bHwvulxlQCfQH2X
9Q0MK1+YZgsoJGVXVxIPRVM=
=jzY2
|
| Post Reply
|
| Re: Help, after apply idm351Adir2, can not connect to RL |
 |
Mon, 12 May 2008 16:36:01 GMT |
Yes, I tried to uncheck the ssl and using the cert from the working
driver. I was getting the same error message for both.
Thanks
ab@novell.com;1555471 Wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Does it connect w/out SSL? Have you verified the certs for this
> particular driver if they are different from the drivers that do work?
>
> Good luck.
>
>
>
>
>
> vivianfeng wrote:
> | Hello everyone:
> |
> | I applied idm351 engine patch 3 and idm351adir2 last week. Now 2 of
> my
> | ad drivers can not connect to remote loader. The strange thing is
> that
> | I have 5 drivers in my environment and 3 of them are working
> properly.
> | I am thinking it should not be an engine problem, otherwise non of
> the
> | AD drivers would work. My environment is idm351 on red hat linux.
> | Remote loader and Ad driver shim are on window 2003. Any help is
> | appreciated.
> |
> | Thanks
> |
> | ====Here is the error I got from remote loader==============
> | DirXML: [05/12/08 16:22:19.54]: Loader: Verifying command port...
> | DirXML: [05/12/08 16:22:20.88]: Loader: Verifying driver can be
> | loaded...
> | DirXML: [05/12/08 16:22:21.24]: ADDriver: Driver::destroy
> | DirXML: [05/12/08 16:22:21.58]: ADDriver: Driver::~Driver()
> | DirXML: [05/12/08 16:22:21.94]: Loader: Initializing SSL
> encryption...
> | DirXML: [05/12/08 16:22:40.18]: Loader: Waiting for DirXML to
> connect
> | on 'TCP server socket, port 8993, address XX.XXX.XX.XXX, using
> SSL'...
> | DirXML: [05/12/08 16:23:05.36]: Loader: OpenSSL socket: AES256-SHA
> | SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1
> | DirXML: [05/12/08 16:23:05.71]: Loader: Authenticating with
> DirXML...
> | DirXML: [05/12/08 16:23:05.71]: Loader: Received 'handshake'
> document
> | DirXML: [05/12/08 16:23:05.86]:
> | DirXML Log Event -------------------
> | Thread = Connection Monitor
> | Level = warning
> | Message = Handshake timeout: closing connection
> | DirXML: [05/12/08 16:23:06.41]: Loader: XML Document:
> | DirXML: [05/12/08 16:23:06.77]: Loader: null document
> | DirXML: [05/12/08 16:23:07.11]: <handshake
version="1.0">
> | <password><!-- content suppressed --></password>
> | </handshake>
> | DirXML: [05/12/08 16:23:07.47]: Loader: Authentication handshake
> | failed: Wrong command type
> | DirXML: [05/12/08 16:23:08.18]:
> | DirXML Log Event -------------------
> | Thread = Subscriber Channel
> | Level = error
> | Message = Authentication handshake failed: Wrong command type
> |
> |
> | ==========Here is partial error from engine with level 3
> | trace===========
> | [05/12/08 09:23:04.688]:AD_EA PT:Remote Interface Driver: Opening
> | connection...
> | [05/12/08 09:23:04.689]:AD_EA PT:Remote Interface Driver: Client
> socket
> | parameters: hostname = 'XXX.com' port = 8993 KMO = 'IDMAD' SSL mode
> =
> | server
> | [05/12/08 09:23:04.690]:AD_EA PT:Remote Interface Driver: Creating
> an
> | NTLSSocket
> | [05/12/08 09:23:05.300]:AD_EA PT:Remote Interface Driver: NTLS
> Socket:
> | AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256)
> | Mac=SHA1
> |
> | [05/12/08 09:23:05.302]:AD_EA PT:Remote Interface Driver: Connection
> | established...
> | [05/12/08 09:23:05.302]:AD_EA PT:Remote Interface Driver: Sending...
> | [05/12/08 09:23:05.303]:AD_EA PT:
> | <handshake version="1.0">
> | <password><!-- content suppressed --></password>
> | </handshake>
> | [05/12/08 09:23:05.304]:AD_EA PT:Remote Interface Driver: Document
> | sent.
> | [05/12/08 09:23:05.313]:AD_EA :Remote Interface Driver: Waiting for
> | receive...
> | [05/12/08 09:23:05.666]:AD_EA ST:SubscriptionShim.execute()
> returned:
> | [05/12/08 09:23:05.667]:AD_EA ST:
> | <nds dtdversion="3.5" ndsversion="8.x">
> | <output>
> | <status level="retry" type="remoteloader">No
connection to remote
> | loader</status>
> | </output>
> | </nds>
> | [05/12/08 09:23:05.669]:AD_EA ST:Requesting 30 second retry delay.
> | [05/12/08 09:23:05.669]:AD_EA ST:
> | DirXML Log Event -------------------
> | Driver: \PRODIDVTREE\esc\idm\driverset\AD_EA
> | Channel: Subscriber
> | Status: Retry
> | Message: Code(-9006) The driver returned a "retry" status
> | indicating that the operation should be retried later. Detail from
> | driver: No connection to remote loader
> | [05/12/08 09:23:05.696]:AD_EA ST:Received state change event.
> | [05/12/08 09:23:05.698]:AD_EA ST:Transitioned from state
> | '%+C%14CStarting%-C' to state '%+C%14CRunning%-C'.
> | [05/12/08 09:23:05.699]:AD_EA ST:Successfully processed state change
> | event.
> | [05/12/08 09:23:05.700]:AD_EA ST:Submitting identification query to
> | subscriber shim:
> | [05/12/08 09:23:05.701]:AD_EA ST:
> | <nds dtdversion="3.5" ndsversion="8.x">
> | <source>
> | <product version="3.5.11.20080307
">DirXML</product>
> | <contact>Novell, Inc.</contact>
> | </source>
> | <input>
> | <query event-id="query-driver-ident"
scope="entry">
> | <search-class
class-name="__driver_identification_class__"/>
> | <read-attr/>
> | </query>
> | </input>
> | </nds>
> | [05/12/08 09:23:06.706]:AD_EA ST:SubscriptionShim.execute()
> returned:
> | [05/12/08 09:23:06.707]:AD_EA ST:
> | <nds dtdversion="3.5" ndsversion="8.x">
> | <output>
> | <status level="retry" type="remoteloader">No
connection to remote
> | loader</status>
> | </output>
> | </nds>
> |
> |
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - 'Enigmail: A simple interface for
> OpenPGP email security' (http://enigmail.mozdev.org)
>
> iD8DBQFIKGbD3s42bA80+9kRAnVnAJ47yaganAxKsRPXcLMN6bHwvulxlQCfQH2X
> 9Q0MK1+YZgsoJGVXVxIPRVM=
> =jzY2
> -----END PGP SIGNATURE-----
--
vivianfeng
------------------------------------------------------------------------
vivianfeng's Profile: http://forums.novell.com/member.php?userid=1654
View this thread: http://forums.novell.com/showthread.php?t=327525
|
| Post Reply
|
|
|
|
|
|
|
|
|
|