Hi ASDM'ers

I'm slowly but surely despairing getting the NT client
properly prompted by our ADSM Server.

Server details:
==============

OS:      AIX 4.1.4
Version: ADSM Server 2.1.5.10
Host:    RS/6000-590 with 256MB

Client details:
==============

OS: Windows NT 4.0 (Service pack 3) US-English
Version: ADSM Client 2.1.0.6g
Host:    PPro 200MHz with 64MB Memory
dsm.opt:
--------------------------------------------------------
commmethod      tcpip
commmethod      tcpip
DOM C: E:
Exclude *:\...\pagefile.sys
Exclude *:\...\SYSTEM32\CONFIG\*.*
Exclude *:\...\SYSTEM32\CONFIG\...\*

NODENAME PCAND7.MPI-STUTTGART.MPG.DE
TCPSERVERADDRESS adsmserv1.mpi-stuttgart.mpg.de

schedlogname c:\Win32app\Ibm\Adsm\baclient\dsmsched.log
schedlogr 7 days
schedmode prompted
password ********
--------------------------------------------------------
Symptoms:
Symptoms:
========
         Dsm and Dsmadm run without problem, the difficulties are in the
         Scheduler Service. After getting prompted by the Server, the session
         is PENDING and later on FAILED and I do not get a dsmsched.log file.
         The service starts properly (according to the event log and the
         Control Panel/Services). There were no problems during the service
         installation.

Error Messages:
===============

dsmerror.log:
09/09/1997 10:28:50  FioGetOneDirEntry(): *** Access to NTFS file security 
information denied, file/dir skipped ***
09/09/1997 10:29:46  TransWin32RC(): Win32 RC 32 from HlOpen(): CreateFile
09/09/1997 10:29:47  TransWin32RC(): Win32 RC 32 from HlOpen(): CreateFile
09/09/1997 10:35:50  ANS4111E Invalid option/value: '-CommMeth=D'
09/09/1997 10:46:46  ANS4111E Invalid option/value: '-CommMeth=D'
09/09/1997 10:58:27  ANS4111E Invalid option/value: '-CommMeth=D'

The last line repeats for every start of the service. I verified that the
dsm.opt file is used, but somehow this CommMeth=D is showing up after installing
the service. I repeated this on a second machine with the same operating
system level NT4.0 SP3. A client installed from the very same sources runs
fine (server prompted) on a NT4.0 SP1 (german) box. This tells me, the problem
is on the client, not the server side. Removing every ADSM-related key from
the registry and reinstalling the client on the NT4.0 SP1 boxes
did not help as well.


Is anyone out there running the 2.1.0.6 client on NT 4.0 Service-Pack 3
(English) and gets a proper response to a server prompt ?

Sorry for the detailed introduction and thanks for any hint

Armin
--
 ------------------------------------------------------------------------------
 ------------------------------------------------------------------------------
|Armin Burkhardt               | Heisenbergstrasse 1 | Phone: (49) 711-6891563 |
|MPI fuer Festkoerperforschung | D-70569 STUTTGART   | FAX  : (49) 711-6891632 |
 ------------------------------------------------------------------------------
|Internet:  burkhard AT and.mpi-stuttgart.mpg DOT de                            
      |
 ------------------------------------------------------------------------------