Well client port usage does vary when connecting to a server. The server listens at an assigned port. The client takes the next port available and uses that to connect to the server. To change this behavior a little, use port restriction. Take ports 1025 - 10xx and restrict to a user profile. Then use that user profile to connect to the DDM server(s). This should cause the DDM client to use the, now available, restricted ports to make the connection, at least in theory.
Let me know if you try this and whither it works or not.
Christopher K. Bipes mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc. http://www.cross-check.com
6119 State Farm Drive Phone: 707 586-0551 x 1102
Rohnert Park CA 94928 Fax: 707 586-1884
If consistency is the hobgoblin of little minds, only geniuses work here. Karen Herbelin - Readers Digest 3/2000
From: email@example.com [mailto:firstname.lastname@example.org]
Sent: Monday, January 22, 2001 1:38 PM
Subject: Controlling ports used by DDM
We are using DDM over IP for our internal use.
I've done some testing and which port gets used by the server seems to
jump. Testing involved:
CRTDDMF FILE(QTEMP/AAAROB) RMTFILE(ROB/AAAROB) RMTLOCNAME(rmtsys *IP)
My thought is to only open up 10500 through 10599. The Cisco kid can do this but he wondered if it also uses a different port to initialize the conversation.
Opinions please about which ports to open up for DDM.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.