So, what you're telling me is as long as I've got port 1500 open, I should be ok? The sending port is irrelevant?
So what else could be my problem, 'cause it ain't working. Thanks, T. --- Stef Coene <[EMAIL PROTECTED]> wrote: > On Saturday 11 September 2004 21:50, > showersofblessings wrote: > > Stef, > > > > Note: this is a personal view. > > > > There are usually two ports involved in a TCP > > communication: the listening and the talking port. > > What is usually defined during a TCP dependent > > software configuration is the listening port which > has > > to be static, > !! this is the listening port on the TSM server so > it's the destination port > of the tcp connection > > > while the talking port is randomly > > generated by the system. > > And since the value of your schedmod is "polling", > > port 32850 might be the one your client was using > to > > try poll the server and it timed out because the > > server didn't response back. > Yes and no. The clients polls, so the client > initiate the connection on port > 1500 TO the TSM server and uses a high random port > to do this. So port 1500 > TO the TSM server has to be opened on the firewall. > The other port, 32850, > is not important because no connection is initiated > to this port, it is part > of an establisched connection. > When a firewall sees a session to a port, it also > knows the port on the client > and all packets in the session will be allowed. > > > Stef > > -- > [EMAIL PROTECTED] > "Using Linux as bandwidth manager" > http://www.docum.org/ > __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail
