For boxes behind a firewall, I use SCHEDMODE POLLING. That way I only have to open up the 1500 port from the client to the server. The network people further refine it so that only the client(s) IP address can communicate with the specified TSM server address over port 1500. Using POLLING I don't have to open up port 1501 for the TSM server to communcate schedule start times to the client.
Bill Boyer DSS, Inc. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Ilja G. Coolen Sent: Friday, November 02, 2001 2:18 AM To: [EMAIL PROTECTED] Subject: Re: DMZ and ports to be opened? Hello there Selva, By default TSM user port 1500 for TCP/IP traffic. So by enabling port 1500 in the firewall bidirectional for the TSM server and the client node, the TSM client and server should be able to communicate. It would be advisable to use NAT though. BE AWARE. TSM port 1500 is default and probabely known by potential hackers. It could be smart to change the default port. -----Oorspronkelijk bericht----- Van: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]Namens Selva, Perpetua Verzonden: donderdag 1 november 2001 16:36 Aan: [EMAIL PROTECTED] Onderwerp: DMZ and ports to be opened? Urgentie: Hoog Hi Does anyone know how to make this work successfully? We have opened up a firewall port on the global network, is there anything on the TSM ports that needs to be opened for backup to be successful? Please let us know Thanks > -----Original Message----- > From: Kyle Kinzer [SMTP:[EMAIL PROTECTED]] > Sent: Thursday, November 01, 2001 10:31 AM > To: [EMAIL PROTECTED] > Subject: Session is lost . . . > > I had researched the below errors for TSM client on a Novell system a > while > ago. If I recall, I couldn't find anything specific on the list server, > other than it's a TCPIP problem. In my case is was a simple TCPIP problem. > The NIC card was set to 10mbps/half duplex and the port on the switch was > set to 10mpbs/full duplex. Once we changed the port to 10mbps/half, the > errors went away and backup performed normally. > > Just thought I'd pass it on. > > kyle > > > 10/31/2001 12:27:09 TcpRead(): recv(): errno = 54 > 10/31/2001 12:27:09 sessRecvVerb: Error -50 from call to 'readRtn'. > 10/31/2001 12:27:09 ANS1809E Session is lost; initializing session reopen > procedure. > 10/31/2001 12:27:09 ANS1809E Session is lost; initializing session reopen > procedure. > 10/31/2001 12:27:25 ANS1810E TSM session has been reestablished.
