XPost: comp.os.vms   
   From: gah@ugcs.caltech.edu   
      
   In comp.os.vms Johnny Billquist  wrote:   
   > On 2011-04-07 05:27, glen herrmannsfeldt wrote:   
   >> Jeffrey H. Coffield  wrote:   
   (snip)   
   >>> After quite a bit of digging, I saw that when the ftp session started,   
   >>> it always used port 5001 first, then 5002, 5003 and fail on 5004.   
   >>> Finally a "TPCIP show device" showed there was a bg device open on port   
   >>> 5004.   
      
   >> I presume the is not passive-ftp, which is more usual these days,   
   >> especially as it gets through firewalls easier.   
      
   > Could be either. Depends on which side this happens on.   
   > I'm not clear on that from the description above.   
      
   >> I am cross-posting to comp.protocols.tcp-ip.  In general, a TCP   
   >> connection is identified by the quad of source address, source port,   
   >> destination address, destination port.   
   (snip)   
      
   > With the exception that if you open a port for listening, you only have   
   > the local address and port. And so, no other local uses of that port can   
   > be allowed, no matter what remote end.   
      
   That is one reason for the cross-post.   
      
   >> It seems like a VMS bug to me, though.   
      
   -- glen   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)