Harold,

I didn't have the TCPCLIENTPORT Line in the DSM.OPT but I added that
 
Note: I also have the webports option not sure I need it but it can't hurt 
right?

Here is the partial DSM.OPT file

LANG AMENG
DOMAIN ALL-LOCAL
TCPSERVERADDRESS spg.acf.xxx.xxx
PASSWORDACCESS GENERATE
TCPCLIENTADDRESS 246.4.4.187
webports 1500 1501 
tcpclientp 1581
NODENAME sphinex349


I stopped/started the schedule service then 

The netstat -a -n now shows 1581 (that's the value I choose)

TCP    0.0.0.0:1501           0.0.0.0:0              LISTENING
TCP    0.0.0.0:1581           0.0.0.0:0              LISTENING

Thanks

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Vandeventer, Harold [BS]
Sent: Thursday, November 17, 2011 11:18 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Windows 2008 client ..TSM schedule won't run

The listening port number is your choice; 1501 is the default for the TSM 
client.

Look at your DSM.OPT file, it should have a line similar to: TCPCLIENTPORT 1501.

Then, stop/start the schedule service in Windows services to get it to read the 
option.

The netstat -a -n should then display the 1501 (or whatever value you 
specified).

I think I'd then reopen the client GUI to force a connection back to the server 
to update the server side with that listening port value.

When you have the port listening, you should be able to TELNET <nodeIP> 1501 
(or your value) and get a "blank screen" on that command window.

------------------------------------------------
Harold Vandeventer
Systems Programmer
State of Kansas - Department of Administration/COMPACT
Harold.Vandeventer AT da.ks DOT gov
(785) 296-0631


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Hughes, Timothy
Sent: Thursday, November 17, 2011 9:04 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Windows 2008 client ..TSM schedule won't run

Thanks again Harold

I don't see that 1501 listening

C:\>NETSTAT -A -N

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1581           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2103           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2105           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2107           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5250           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:32843          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:32844          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:42510          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:47001          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49168          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49183          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49190          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49192          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:53201          0.0.0.0:0              LISTENING
    TCP    [::]:80                [::]:0                 LISTENING
  TCP    [::]:135               [::]:0                 LISTENING
  TCP    [::]:445               [::]:0                 LISTENING
  TCP    [::]:2103              [::]:0                 LISTENING
  TCP    [::]:2105              [::]:0                 LISTENING
  TCP    [::]:2107              [::]:0                 LISTENING
  TCP    [::]:3389              [::]:0                 LISTENING
  TCP    [::]:32843             [::]:0                 LISTENING
  TCP    [::]:32844             [::]:0                 LISTENING
  TCP    [::]:42510             [::]:0                 LISTENING
  TCP    [::]:47001             [::]:0                 LISTENING
  TCP    [::]:49152             [::]:0                 LISTENING
  TCP    [::]:49153             [::]:0                 LISTENING
  TCP    [::]:49154             [::]:0                 LISTENING
  TCP    [::]:49168             [::]:0                 LISTENING
  TCP    [::]:49183             [::]:0                 LISTENING
  TCP    [::]:49190             [::]:0                 LISTENING
  TCP    [::]:49192             [::]:0                 LISTENING
  TCP    [::1]:1801             [::]:0                 LISTENING

Best regards

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Vandeventer, Harold [BS]
Sent: Wednesday, November 16, 2011 3:30 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Windows 2008 client ..TSM schedule won't run

On the node side, open a command prompt and issue NETSTAT -A -N

Do you see the port number listening?  The TSM default is 1501, I believe.

In my case: 'TCP 0.0.0.0:1501 0.0.0.0:0 LISTENING' is displayed.

If the port is listening and you can't TELNET to it (assuming you have TELNET 
allowed through your network), it's most likely the firewall IS blocking the 
traffic.

If not, stop/start the scheduler service as David recommends.

Like others, we've been round-n-round this issue with firewall managers saying 
"we never change" only to find they did.

------------------------------------------------
Harold Vandeventer

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Ehresman,David E.
Sent: Wednesday, November 16, 2011 1:46 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Windows 2008 client ..TSM schedule won't run

Then Harold has the right answer.  If you can telnet from the tsm server to the 
client at the port the listener is suppose to be using, than it is not a 
firewall problem.  If the telnet attempt times out, either the cad (or 
scheduler) is not running, it is using a different port (see the cad startup 
messages in dsmwebcl.log), or there is a firewall/network issue blocking access.

David

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Hughes, Timothy
Sent: Wednesday, November 16, 2011 2:23 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Windows 2008 client ..TSM schedule won't run

Hi Wanda 

We use prompted mode

Thanks

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Prather, Wanda
Sent: Wednesday, November 16, 2011 11:55 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Windows 2008 client ..TSM schedule won't run

Are you running in polling (the default) or prompted mode?

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Hughes, Timothy
Sent: Wednesday, November 16, 2011 11:24 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Windows 2008 client ..TSM schedule won't run

Hi,
We have 4 windows 2008 that are missing consistently the TSM scheduler is set 
to start however the backups don't run.
f.y.i - We had this issue about  5 months ago and the admin set the UAC to the 
lowest settings and turned the firewall off and the backups worked until 
recently. The admin says the firewall is turned off and the settings are the 
same.
Anyone else have or have had this issue?

Windows 2008 64 bit R2 servers
Tivoli clients 6.2.2.2

Thanks for any help/advice in advance!