Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem to connect client to server.

Status
Not open for further replies.

chrismagic

Technical User
May 10, 2007
2
CA
Dear all,

I contact you because I have a problem with a TSM Client.
I'm not able to connect the client to the server. I have a message of error: connection reject: TCP/IP failure

In the dmserror.log I have got these following lines:

ANS5216E Could not establish a TCP/IP connection with address 'xxx.xx.xxx.xx:1500'. The TCP/IP error is 'Unknown error' (errno = 10060).
ANS4039E Could not establish a session with a TSM server or client agent. The TSM return code is -50.
ANS1017E Session rejected: TCP/IP connection failure

I hope that you will be able to help me.

Christophe
 
What o/s is the client? Is your dsm.opt/dsm.sys (if unix/linux) configured properly?

Do you have sessions disabled on the server?

Need a little more info
 
I think it would be most helpful, if you would send us the contents of dsm.opt and dsm.sys
 
is there a firewall between client and server ?
Can you do a telnet from a tsm client to the tsm server using port 1500 ?

rgds,

R.
 
Hello,

I am sorry for the lack of information in my message but I begin on TSM.

I believe to have found from where the problem can come... indeed, there is a firewall between the client and the server. The default port (1500) is open on the firewall.

On the dsmc of the client, I run this command:

dsmcutil inst scheduler /name:"TSM Client Scheduler" /node:pProdXXXXXX /password:admin /clientdir:"c:\program files\tivoli\tsm\baclient" /optfile:"c:\program files\tivoli\tsm\baclient\dsm.opt" /autostart:yes

TSM Windows NT Client Service Configuration Utility
Command Line Interface - Version 5, Release 4, Level 0.2
(C) Copyright IBM Corporation, 1990, 2007, All Rights Reserved.
Last Updated Feb 21 2007
TSM Api Verison 5.4.0

Command: Install TSM Client Service
Machine: PPRODXXXXXXX(Local Machine)

Installing TSM Client Service:

Machine : PPRODXXXXXXX
Service Name : TSM Client Scheduler
Client Directory : c:\program files\tivoli\tsm\baclient
Automatic Start : yes
Logon Account : LocalSystem

The service was successfully installed.

Creating Registry Keys ...

Updated registry value 'ImagePath' .
Updated registry value 'EventMessageFile' .
Updated registry value 'TypesSupported' .
Updated registry value 'TSM Client Scheduler' .
Updated registry value 'ADSMClientKey' .
Updated registry value 'OptionsFile' .
Updated registry value 'EventLogging' .
Updated registry value 'ClientNodeName' .

Generating registry password ...
Authenticating TSM password for node PPRODXXXXXX ...

Connecting to TSM Server via client options file 'c:\program files\tivoli\tsm\ba
client\dsm.opt' ...

Error 4 establishing TSM API session: A communications error occurred.
Error 4 authenticating password: A communications error occurred.

Starting the 'TSM Client Scheduler' service ..................
The service was successfully started

It would seem that there is a problem of authenfication between the Client and the Server.

The description of my dsm.opt is:


PASSWORDACCESS GENERATE
DOMAIN C:
DOMAIN SYSTEMSERVICES
DOMAIN SYSTEMSTATE
DOMAIN ALL-LOCAL
TCPSERVERADDRESS 172.21.204.46
TCPPort 1500

TCPCLIENTADDRESS 172.21.208.14
TCPCLIENTPORT 1501
SCHEDMODE PROMPTED

TCPADMINPORT 1500

SCHEDLOGNAME "c:\program files\tivoli\tsm\baclient\dsmsched.log"

MANAGEDSERVICES WEBCLIENT SCHEDULE

INCLUDE.IMAGE "c:" imagetype=snapshot
EXCLUDE.BACKUP "*:\microsoft uam volume\...\*"
EXCLUDE.BACKUP "*:\microsoft uam volume\...\*.*"
EXCLUDE.BACKUP "*:\...\EA DATA. SF"
EXCLUDE.BACKUP "*:\IBMBIO.COM"
EXCLUDE.BACKUP "*:\IBMDOS.COM"
EXCLUDE.BACKUP "*:\IO.SYS"
EXCLUDE.BACKUP "*:\...\system32\config\...\*"
EXCLUDE.BACKUP "*:\...\system32\Perflib*.dat"
EXCLUDE.BACKUP "*:\...\system32\dhcp\...\*"
INCLUDE.BACKUP "*:\...\system32\dhcp\backup\...\*"
EXCLUDE.BACKUP "*:\...\system32\dns\...\*"
INCLUDE.BACKUP "*:\...\system32\dns\backup\...\*"
EXCLUDE.ARCHIVE "*:\microsoft uam volume\...\*"
EXCLUDE.ARCHIVE "*:\microsoft uam volume\...\*.*"
EXCLUDE.ARCHIVE "*:\...\EA DATA. SF"
EXCLUDE.ARCHIVE "*:\IBMBIO.COM"
EXCLUDE.ARCHIVE "*:\IBMDOS.COM"
EXCLUDE.ARCHIVE "*:\IO.SYS"
EXCLUDE.ARCHIVE "*:\...\system32\config\...\*"
EXCLUDE.ARCHIVE "*:\...\system32\Perflib*.dat"
EXCLUDE.ARCHIVE "*:\...\system32\dhcp\...\*"
INCLUDE.ARCHIVE "*:\...\system32\dhcp\backup\...\*"
EXCLUDE.ARCHIVE "*:\...\system32\dns\...\*"
INCLUDE.ARCHIVE "*:\...\system32\dns\backup\...\*"
EXCLUDE.DIR "*:\System Volume Information"
EXCLUDE.DIR "*:\...\Temporary Internet Files"
EXCLUDE.DIR "*:\Recycled"
EXCLUDE.DIR "*:\Recycler
 
If you're able to run commands under dsmc on the client there shouldn't be a password problem because if there was he would prompt you for a password a soon as you enter something like "q fi" under dsmc.

Maybe you should open Port 1501 on the firewall as well.

 
And one more thing:

Is the dsmcad process running on the machine ?
 
... and last but not least:

try to put the following into your dsm.opt file:

COMMmethod TCPip
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top