Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[netmation]

Apparently it seems that the DLink DIR-655 does not support ACTIVE FTP connections. Is this true? I have tried connecting with my DI-524 and Active modes works fine, though then my VOIP phone does not work with the DI-524 since no QoS. Quite the predicament. Very disappointing if it is true that the DIR-655 does not support ACTIVE, which I read in another newsgroup that newer D-Link products may/do not? Is this correct?

What currently happens is that I can connect to a site via Active but when I traverse into a directory folder it takes about 30 seconds to make the connection when going through the DIR-655.  Like it is searching for the proper port??

[netmation]

No one has any opinions on this?  Can others connect through a DIR-655 to FTP sites via ACTIVE mode and get responsive switching between directories on the FTP Server?

I really tend to think this is not implemented properly on the DIR-655.

[netmation]

Any idea on how I can get some support from Dlink on this issue???

Dlink email support just tells me to call phone support.
Dlink phone support I get doesn't understand the difference from Active and Passive FTP, or at least the ones I have gotten??

Is there some way to get escalated to talk to someone whom would understand this better and let me know if there are settings to correct this problem, of if in fact the DIR-655 does not support ACTIVE connections?

Thank you.

[☠]

Most NAT devices do not support Active FTP.  epically if both endpoints of the FTP are NAT'ed.


You can have a "active" FTP session to a server with a Public IP but it won't work to a private IP. in that case you will need to set your client to use passive

[netmation]

I am trying to have an ACTIVE connection to a public IP (my web hosting account).  It works with the DI-524, but not the DIR-655.

[☠]

If you server is on a Public IP address and your client is on a private behind the DIR655 you should have no issue with ACTIVE/Passive FTP. 

What client/server are you using?

[netmation]

Thanks for the help, here is details of my results from testing so far.  I passed it on to Dlink support as well, so will have to see what they say.  If anyone else has ideas that would be great.

Problem
Having trouble with the connection to a public FTP site through my
DLink DIR-655 via ACTIVE FTP mode. I can actually initially connect
just fine and the remote directory structure instantly refreshes in
my client side FTP software.  But when I attempt to traverse to a
sub-directory on the remote server, the first time I access each
sub-directory it takes about 30-45 seconds to refresh the screen
with the sub-directory contents.  And any file transfers to the
server do not work.

Facts
My client computer is directly connected to the Internet with a
static IP address.  I am attempting to connect to a Windows 2003
Server running IIS, setup to accept ACTIVE FTP connections, which
has a public IP address.  If I connect my client computer directly
into the dedicated Ethernet cable in my office, bypassing the
DIR-655, everything works fine, however; when I connect it through
the DIR-655 I end up with the problem described above.  I have had
successful connections to this server via Active FTP from various
other locations, and even through a DLink DI-524. The only variable
that does not work is when I go through the DIR-655.

My DIR-655 is Hardware version A2, and I have tried this with both
the 1.05 firmware and the 1.02 firmware.  With the 1.05 firmware I
get the results described in the Problem Section above.  I tried it
as Dlink Support suggested with the 1.02 firmware, with all ALG's check
marked and get the same result.  I then tried to uncheck the ALG for
FTP, and it was actually worse.  I don't even get the fast initial
connection of the directory, infact I get no connection to the
server at all. So it seems that the different firmware version had
no affect.

Appreciate any help.

[netmation]

DLink support provided a solution to this problem that worked....

Log in to the router, click advanced and then Firewall settings.
Disable the SPI and change the NAT ENDPOINT FILTERING to endpoint independent.

[☠]

I want to try that

[Lycan]

Disable SPI and change the NAT ENDPOINT FILTERING to endpoint independent.
That should fix the issue.

[dforbes]

Will these settings affect the security of the network?

[Lycan]

To a limited degree. They'll allow the type pf traffic that you want. We restrict types of connections with these settings. I wouldn't worry about it too much.