Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*linux\s+client\s+setup\s+through\s+firewall\s+\-\s+what\s+source\s+port\?\s*$/: 14 ]

Total 14 documents matching your query.

1. linux client setup through firewall - what source port? (score: 1)
Author: "T. Lists" <tracylists AT YAHOO DOT COM>
Date: Fri, 10 Sep 2004 13:02:30 -0700
Hey all - I know this one has been asked before, but I can't seem to find a solution to my problem. IBM has been a bit snitty - telling me it's a "communications/network" problem. Ok, maybe not snitt
/lists/html/ADSM-L/2004-10/msg00107.html (11,329 bytes)

2. Re: linux client setup through firewall - what source port? (score: 1)
Author: Stef Coene <stef.coene AT DOCUM DOT ORG>
Date: Sat, 11 Sep 2004 12:54:44 +0200
1500 is enough That's not the problem. Your client connects TO port 1500 on the TSM server. So you have to open port 1500 to your TSM server. But each connection requires also a port on the client to
/lists/html/ADSM-L/2004-10/msg00108.html (12,328 bytes)

3. Re: linux client setup through firewall - what source port? (score: 1)
Author: showersofblessings <tayo70s AT YAHOO DOT COM>
Date: Sat, 11 Sep 2004 12:50:21 -0700
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 configura
/lists/html/ADSM-L/2004-10/msg00109.html (13,766 bytes)

4. Re: linux client setup through firewall - what source port? (score: 1)
Author: Stef Coene <stef.coene AT DOCUM DOT ORG>
Date: Sun, 12 Sep 2004 01:06:09 +0200
!! this is the listening port on the TSM server so it's the destination port of the tcp connection Yes and no. The clients polls, so the client initiate the connection on port 1500 TO the TSM server
/lists/html/ADSM-L/2004-10/msg00110.html (10,729 bytes)

5. Re: linux client setup through firewall - what source port? (score: 1)
Author: "T. Lists" <tracylists AT YAHOO DOT COM>
Date: Mon, 13 Sep 2004 06:35:29 -0700
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. __________________________
/lists/html/ADSM-L/2004-10/msg00130.html (11,555 bytes)

6. Re: linux client setup through firewall - what source port? (score: 1)
Author: Stef Coene <stef.coene AT DOCUM DOT ORG>
Date: Mon, 13 Sep 2004 20:09:42 +0200
Yep. Best you can do is ask your firewall guy if he can check the firewall logs to see if the firewall somehow drops the packets. Also, you can check the firewall logs to see if the firewall sees the
/lists/html/ADSM-L/2004-10/msg00137.html (9,940 bytes)

7. Re: linux client setup through firewall - what source port? (score: 1)
Author: Sal Mangiapane <salm AT VITALDS DOT COM>
Date: Mon, 13 Sep 2004 14:32:35 -0400
Can the computers "ping" each other. It may be a networking problem and one computer does not have a "route" to the other computer. Best Regards, Sal Vital Data Systems, LLC So, what you're telling m
/lists/html/ADSM-L/2004-10/msg00138.html (10,444 bytes)

8. linux client setup through firewall - what source port? (score: 1)
Author: "T. Lists" <tracylists AT YAHOO DOT COM>
Date: Fri, 10 Sep 2004 13:02:30 -0700
Hey all - I know this one has been asked before, but I can't seem to find a solution to my problem. IBM has been a bit snitty - telling me it's a "communications/network" problem. Ok, maybe not snitt
/lists/html/ADSM-L/2004-09/msg00228.html (11,160 bytes)

9. Re: linux client setup through firewall - what source port? (score: 1)
Author: Stef Coene <stef.coene AT DOCUM DOT ORG>
Date: Sat, 11 Sep 2004 12:54:44 +0200
1500 is enough That's not the problem. Your client connects TO port 1500 on the TSM server. So you have to open port 1500 to your TSM server. But each connection requires also a port on the client to
/lists/html/ADSM-L/2004-09/msg00229.html (12,159 bytes)

10. Re: linux client setup through firewall - what source port? (score: 1)
Author: showersofblessings <tayo70s AT YAHOO DOT COM>
Date: Sat, 11 Sep 2004 12:50:21 -0700
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 configura
/lists/html/ADSM-L/2004-09/msg00230.html (13,659 bytes)

11. Re: linux client setup through firewall - what source port? (score: 1)
Author: Stef Coene <stef.coene AT DOCUM DOT ORG>
Date: Sun, 12 Sep 2004 01:06:09 +0200
!! this is the listening port on the TSM server so it's the destination port of the tcp connection Yes and no. The clients polls, so the client initiate the connection on port 1500 TO the TSM server
/lists/html/ADSM-L/2004-09/msg00231.html (10,560 bytes)

12. Re: linux client setup through firewall - what source port? (score: 1)
Author: "T. Lists" <tracylists AT YAHOO DOT COM>
Date: Mon, 13 Sep 2004 06:35:29 -0700
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. __________________________
/lists/html/ADSM-L/2004-09/msg00251.html (11,434 bytes)

13. Re: linux client setup through firewall - what source port? (score: 1)
Author: Stef Coene <stef.coene AT DOCUM DOT ORG>
Date: Mon, 13 Sep 2004 20:09:42 +0200
Yep. Best you can do is ask your firewall guy if he can check the firewall logs to see if the firewall somehow drops the packets. Also, you can check the firewall logs to see if the firewall sees the
/lists/html/ADSM-L/2004-09/msg00258.html (9,771 bytes)

14. Re: linux client setup through firewall - what source port? (score: 1)
Author: Sal Mangiapane <salm AT VITALDS DOT COM>
Date: Mon, 13 Sep 2004 14:32:35 -0400
Can the computers "ping" each other. It may be a networking problem and one computer does not have a "route" to the other computer. Best Regards, Sal Vital Data Systems, LLC So, what you're telling m
/lists/html/ADSM-L/2004-09/msg00259.html (10,242 bytes)


This search system is powered by Namazu