hallo ADSM-experts,
is there anybody using the ADSM Netware Client in a Netware 4.1x-LAN and has
problems with the SMS-Interface of
Novell-Netware. We observed 'hanging' connections at remote NW-Fileservers
(respectively over WAN-links). We
tried the newest SMS-Modules from Novell (July 96), but no approvement could be
recognized.
It's very difficult to reconstruct the problem, because you never know whether
it's going to occur or not. We
never managed to show this problem in the lab (obviously there was no
LAN-traffic and heavy
server-utilization).
Error description:
If specified (-dom=remote-fileserver/VOL:) the ADSM-client connects via
TSA-Modul (target service agent) to a
remote File-Server. This connection is visible in the connection-list at the
remote FS (two connections: one
'not-logged-in' of SMDR-NLM and one 'ADSM-Client'-connection). After the backup
this connections should be
cleared. But sometimes one of connection stays 'til reboot of the remote server.
There are two kinds of 'hanging' connections:
a) the connection remains under the name of adsm-client (occured with older
versions of SMS-modules)
b) the connection is kept as 'not-logged-in' in the connection list /
service-connection /smdr-connection.
(since SMSUP5 and newer).
Case 'a)' isn't the worst, because you can have as many connections as
permitted in the user-profile and you
can evade to other users; but the not-logged-in'- SMDR-Connection is nasty,
since every tool using TSA to
connect to this file-server will fail, regardless to the user-account.
I don't know how to clear this connection, merely by rebooting the fileservers.
Obviously it has to be a Novell problem, but in coherence with other
backup-products, using the SMS-API of
Novell, such problems aren't mentioned.
Maybe someone can help me ...
regards
markus
*********************************************************************
* sent by: M. Dombrowski Phone : +49 (0)6130 945371 *
* Fax : +49 (0)6130 945373 *
* Mainzer Str. 37 E-Mail : dombrowski.m AT metronet DOT de *
* 55271 Stad.-Elsheim *
*********************************************************************
|