"Each time that a request is sent via port 21 by the workstation, it will increment the port to send the data back."
That is correct and functioning by design. So, for example, if there is an FTP session open and client 1.2.3.4 requests a file from server 5.6.7.8 on port 21, and the next available port on the server is 23456, the data gets sent over 23456. Now let's say you are sitting at the server and browsing the web. You visit a couple web sites and your browser makes multiple connections to download text an images. This might use ports 23457-23489. Now the FTP client requests another file from 5.6.7.8 on port 21. The next available port to send data out on would be 23490. This goes on and on as you transmit data to/from clients/servers. -Jeff -----Original Message----- From: Vital Touch DJs [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 29, 2003 04:22 PM To: sambar List Member Subject: [sambar] off subject. {09} That is exactly how I thought it would work. However, I notice that with Sambar, it tends to want to send information out of a very high port, such as 4725. I originally had in my firewall table that it would accept incoming connections through port 21, and outgoing (data) through port 20. However, I put the firewall in a "learning" state today, and notice it would say "Device from x.x.x.x on port 4725 wants to make a TCP connection to device x.x.x.x on port 62102. So, in this case, it seems as though the server is spawning another port to send the data. Each time that a request is sent via port 21 by the workstation, it will increment the port to send the data back. ------------------------------------------------------- To unsubscribe please go to http://www.sambar.ch/list/
