IFTP questions

[nikbackm]

Using TCC 9,02.151.

IFTP seems to require that you add TCC.EXE to the allowed programs in the Windows Firewall. Is this correct?

I also encountered this error when I issued a non-IFTP DIR command to the same FTP server that IFTP was connected to.

C:\>dir ftp://netikka.netdrv.fi/

TCC: (Sys) The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for.
"netikka.netdrv.fi"
TCC: (Sys) The system cannot find the file specified.
"ftp://netikka.netdrv.fi/*"
0 bytes in 0 files and 0 dirs

C:\>iftp
netdrv.netikka.fi/

The IFTP connection seemed to be ok, DIR worked at least.

The IFTP connection was opened using IFTP "ftp://net"
FTP.CFG contains the user/pwd for netikka.netdrv.fi and aliases
it to net.

--
Niklas Bäckman

 

[rconn]

nikbackm wrote:

> Using TCC 9,02.151.
>
> IFTP seems to require that you add TCC.EXE to the allowed programs in
> the Windows Firewall. Is this correct?

Yes. See:

http://support.microsoft.com/kb/842242

Rex Conn
JP Software

 

[Steve Fabian]

nikbackm wrote:
| Using TCC 9,02.151.
|
| IFTP seems to require that you add TCC.EXE to the allowed programs in
| the Windows Firewall. Is this correct?

... or to whatever program you use as your firewall. In my case, ZoneAlarm.
Not only do I have to add it generically, I need to add each build
individually, but ZA makes it easy. When a new build attempts Internet
access, I need to make two choices: allow/deny, this time/permanently. If an
even newer build is already available, and I am trying to download it, I use
the once-only permission. IIRC the only issue is crossing the firewall to
access the 'net, not the exact method, thus allowing direct (non-IFTP) FTP
access also allows IFTP, and vice versa. Whether or not TCC utilizes FTP.CFG
relates to the server end of the connection, not to the firewall
permissions.
--
HTH, Steve

 

[nikbackm]

nikbackm wrote:



Yes. See:

http://support.microsoft.com/kb/842242

Rex Conn
JP Software

Thanks.

I really had no problem to configure the firewall to allow TCC. I just thought it was a bit strange that IFTP required me to configure the firewall while simple FTP did not.
(At least I got the Windows Firewall pop-up dialog only when I started IFTP, I used simple FTP earlier without any notifications).

Perhaps IFTP uses incoming TCP connections?

What about the error message I posted above? It does not seem to be related to the firewall issue.

Might it be an FTP server specific problem or is it a TCC problem caused by the concurrent use of IFTP and FTP while having an FTP.CFG file with aliased host name?

--
Niklas