Steven Horn wrote in a message to Thom LaCosta:

 TL> My ISP recently blocked port  1025, and FNOS no longer works. 
 TL> Although there's a configuration line that tells FNOS to do active
 TL> FTP, it apparently is hard coded to either so PASSV or use port
 TL> 1025.

 TL> Can anyone shed light on a work around?  I can use FNOS with
 TL> another ISP that doesn't have port 1025 blocked, but they are twice
 TL> the price. 

 TL> FNOS 1.7b is what I have on my system.

 SH> My FNOS 1.7b archive does not have a "active FTP" line in
 SH> AUTOEXEC.NOS and I did not think it was missing anything.  However,
 SH> PASSV transfers should work. 

I found the line that turns on active in the rather LARGE sample autoexec
file...and have been running it that for years.  The ISP tells me, and I'm
in no position to argue with him, that if I'm using PASSV, then eventually
I'll hit port 1025, which he has blocked.

Running the traffic through the "more expensive spread" ISP, I
can see that I am hitting port 1025.


 SH> If all else fails, contact Marc Blakely at 1:17/0 or at
 SH> lookglas{at}harbornet.com. 

Yes, Marc responsing and said he'd look into it.

thanks

cya,
thom
http://www.tlchost.net/echolist/ 
--- GEcho 1.20/Pro