Welcome to ISAserver.org

FTP transfer fails sometimes

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 Firewall] >> SecureNAT Client >> FTP transfer fails sometimes

Page: [1]

Message

<< Older Topic Newer Topic >>

FTP transfer fails sometimes - 1.Aug.2004 12:56:00 PM

FrancWest

Posts: 70
Joined: 22.Jul.2004
Status: offline

Hi,

we have a reporting tool on our internal network (nettracker) that creates statistics of our webserver logs. Therefor it retrieves the logfiles from our webserver in the DMZ using FTP. The machine on which the program runs is configured as a Secure NAT client. However, the program generates some errors that it can't retrieve some logfiles. Also when doing a manual FTP transfer it sometimes failes. The error reported is: [could not connect data socket]

When running the program again it can transfer the specific logfile fine, but then another logfile can't be transferred. With ISA 2000 we didn't had this issue. Any ideas where to look for, the logfiles of ISA don't show any problems as far a I can see.

Franc.

Post #: 1

Featured Links*

RE: FTP transfer fails sometimes - 1.Aug.2004 12:59:00 PM

FrancWest

Posts: 70
Joined: 22.Jul.2004
Status: offline

In the alert tab of ISA I see the following entry:
The client <ip-address> exceeded its connection limit. The new connection was rejected. For more information about this event, see the Windows event viewer.

What does this mean ?

Franc.

(in reply to FrancWest)

Post #: 2

RE: FTP transfer fails sometimes - 1.Aug.2004 1:05:00 PM

FrancWest

Posts: 70
Joined: 22.Jul.2004
Status: offline

Hi,

I temporarliy disabled the connection limits on the genral configuration page and now it's working fine. However, don't know why that specific machine opens so much connections that the limit is exceeded.

Franc.

(in reply to FrancWest)

Post #: 3

RE: FTP transfer fails sometimes - 2.Aug.2004 12:49:00 PM

tshinder

Posts: 47408
Joined: 10.Jan.2001
From: Texas
Status: offline

Hi Franc,

Maybe be using an inefficient mechanism for transfer. You'd have to do a network trace and then get with the app developers to determine the problem and fix. Not all developers consider number of connections in the equation.

HTH,
Tom

(in reply to FrancWest)