I'm not sure I understand this procedure correctly...
We are currently running (or attempting to!) run ADSM 2.1.0.12 on NT =
using
TCP/IP. According to the documentation, ADSM cannot run as a service by
itself on NT, and requires NT Scheduler to do this. We can get NT
Scheduler to open, using the at command we can schedule a job, the ADSM
window comes up and hangs. We then get the error "Session rejected: =
TCP/IP
connection failure."
You recommended that the properties in the ADSM Central Scheduler =
service
need to be changed. How/where is this done? Can we even do this with =
our
version? I assume that changing it to run under a specific ID with
appropriate privileges is the equivalent of starting up ADSM using an
administrative account in NT? What are the necessary privileges to be
associated with that account?
We have actually performed adding the authority to logon as a service to
the administrative account. It's not immediately apparent where to =
provide
the account name and password in the Service properties.
Any help you could give would be greatly appreciated! Thanks in advance
for your help!
Bonnie
kmedcalf AT DESSUS DOT COM on 09/27/97 05:40:43 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc: (bcc: Bonnie Goins/Headquarters/USX)
Subject: Re: NT Scheduler Service
In <199709271505.AA09879 AT gatekeeper.research.natpower.co DOT uk>, on
09/27/97 at 04:05 PM,
Phil Chissell <phil.chissell AT RESEARCH.NATPOWER.CO DOT UK> said:
>I am running ADSM 2.1.0.13 on Windows NT and am using the named pipe
>mechanism for the backup client on the server. This works fine when
>performing an interactive backup.
>However, when used in conjunction with the ADSM scheduler service it
>always fails with the message in the dsmched.log file saying "Session
>rejected: TCP/IP Connection Failure". I have removed and reinstalled
>the scheduler service but I still get this error. The only way to
>get this to work is to change the "commmethod" option in the dsm.opt
>file back to "tcpip".
>Has anybody else experienced this problem or know how to resolve
>this?
You need to go into the properties of the ADSM Central Scheduler
service and change it to run under a specific ID, which must have the
necessary priviledges.
The problem you are experiencing is due to the fact that the
LocalSystem account (the default account under which services run),
does not have network priviledge.
Create an account with Administrator privilidges, give it authority to
Log on as a Service, and lock it so it can only log on from the
server/workstations running the scheduler. You will also have to
disable password expiry since no one will ever actually "log on" in
this account.
Then provide the account name/password in the Service properties.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Keith Medcalf (416) 410-5791 http://www.dessus.com/ IBM
OS/2, LAN Server, DB2, TCP/IP, DOS, Windows 95, Windows NT
Finger or email kmedcalf-pgp AT dessus DOT com for my PGP Public Key
|
