Tcpclientport only changes the port for the scheduler.

Use 'httpport' for changing the cad's port, although I am not sure
if the cad is relaying the connection to the scheduler internally or
if it just points out the schedulers port.

You just might need to punch another hole in your firewall for the cad.

-David

--
David Hendén
Storage specialist
Exist AB
+46-(0)70-3992759



Dan Sveen Olsen <dan.olsen AT NO.THALESGROUP DOT COM> 
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
2004-03-30 13:37
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: TSM linux client in the DMZ






Thank you!! :)

It's working now. But why dsmc and not dsmcad?

Dan

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
David Henden
Sent: 30. mars 2004 11:56
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM linux client in the DMZ


Hi Dan,

Do you have to use the cad?
Try running with "dsmc schedule" instead, and verify with netstat -an | 
grep 1501

Also, make sure nothing is blocking 1501by checking dsmerror.log.

-David

--
David Hendén
Storage specialist
Exist AB
+46-(0)70-3992759



Dan Sveen Olsen <dan.olsen AT NO.THALESGROUP DOT COM> 
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
2004-03-30 08:31
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: TSM linux client in the DMZ






Hello and thanks for you answer.

I have checked the HLADDRESS and LLADDRESS values and they are correct. I 
don't know if something is buggy, but when starting dsmcad it won't bind 
to port 1501 even if I use TCPCLIENTPORT or not. The lsof command shows 
this:

dsmcad     3095    root    4u  IPv4     500722                TCP *:41363 
(LISTEN)

If it might be of some help, this a RedHat Linux 9 server.

Dan

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Richard Sims
Sent: 29. mars 2004 15:45
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM linux client in the DMZ


>I have a problem with a linux server in our DMZ. The backup server must
>communicate with the client through a firewall and I have opened up port
>1501 to the client. However, the server is unable to backup the client
>because the client ain't listening on port 1501, even though it is
>configured to do so. I use the following settings:
>
>dsm.sys:
>servername backup
>        nodename                ftp
>        passwordaccess          generate
>        tcpserveraddress        10.1.0.6
>        schedmode               prompted
>        tcpclientport           1501
>        sessioninitiation       serveronly
...

1501 is the default, anyway.  (You can verify what the client is listening
on via the 'lsof' command or equivalent.)

Note that you are using SESSIONINITiation SERVEROnly, which says that the
server will initiate the session according to the node definition
HLADDRESS and LLADDRESS values.  Check those, and inspect the server
Activity Log for anomalies in attempting sessions with that client.
Use DEFine CLIENTAction to experiment and prove session capability
through the firewall.

   Richard Sims   http://people.bu.edu/rbs