Ftp connection and Dreamweaver

Port 21 might not be enough... if the other end is using Active ftp despite a passive ftp request, but you said you turned the whole Firewall off right!?

I'd try this 1st, get Applejack...
http://www.versiontracker.com/dyn/moreinfo/macosx/19596

After installing, reboot holding down CMD+s, then when the prompt shows, type in...

applejack AUTO

Then let it do all 5 of it's things.

Connecting to the Webserver just implies port 21 is open on both, but with Active ftp some port from 1024 to 65535 is used for file transfer. Could it be sftp?

System Profiler>Network>Firewall should tell which services the OS thinks are working... sometimes used to be different than what the Sharing Panel said, (unless they fixed that recently).

You might even have to trash...

/Library/Preferences/com.apple.sharing.firewall.plist

and reboot to get the ports open!?

Any Proxies set anywhere?

Have you tried TransmitX yet, or another ftp APP?

Did you look in the User's Library, or the one at the Root level?

Normally turning off the Firewall will open ALL the ports, but somtimes it doesn't work like it's supposed to.

In the Sharing Panel, under the Firewall Tab, other ports can be opened, but most likely won't work with Active ftp because the other end picks a random port above 1023 for file transfer.

I'd try it with the Firewall OFF, then restart.

Might be that one ftp site having problems, or a Port issue.

Is this a public ftp site that I can try from here?

Seems like DW's pefs are messed up, have you tried a new set... or whatever they call it in DW?

But I don't understand why I get ftp connection with
2 websites and just one is not working??? should this
be happening if it was a "port" problem???

I can help clarify this. With FTP, there are TWO connections. The first is the control connection, and that occurs on port 21. This is where the authentication takes place, and where commands are passed from cliet to server.

The second connection is the data connection. This is where the transfer of data takes place (including a directory listing). There are two basic ways of establishing this connection, active and passive. In an active connection the server attempts to open a socket from port 20 to a random port on the client. This is the connection which is blocked by firewalls.

In passive mode, the server sends back a port number that it (or rather a child) is listening on. The client connects to the server on that port, and receives data. The problem is, that while this is happening, the control connection is idle. This may cause the control connection (and thus the entire protocol) to time out.

So there are quite a few things that can go wrong. If your server only supports active mode and you have a firewall which blocks its incoming connection, eventually the control connection will time out. If your server is load-balancing, or your router tries to recylcle ide connections, the control connection may be shut down. I don't know what's happening in your case, but I can tell you what may be happening with your ports. HTH.

Hi Phil, thanks for clarifying this issue with the
port.
But my server does support "passive mode" only. And
like I said before, now all my connections seems to
working. So, I don't think I have a problem with port
or firewall.

Okay. I just wanted to clear that up.

But this is something about "permissions to upload"
?????
Can the server block long paths?
tks

Is the path on the client or the server? The longer the path, the longer the chain of permissions. If the path is on the server and any one of those directories is read-only, you won't be able to write the file. If it's on the client, all those directories need to have read permission. I don't think there's any attempt at blocking. It's just that the longer the path, the more things that could go wrong.

ok. Now we are getting close.
But let me understand.
What you mean when you say "client"??

FTP is a client-server protocol (as opposed to peer-peer). The server listens on port 21 for connections from the client. The client is the originator of the connection.

I'm just trying to put a new folder (with a lot of
subfolders)
Do I need permissions to do that?? since this new
folders are going to the "public_html" folder where I
always had permission to???
All the folders have 755
and files 644

The folder permissions translate to "owner can read, write & execute", "all others can read & execute but not write". The file permissions are similar, but there's no "execute". Since you're probably the owner, this should be just fine.

This is the error message:
I/O Error Connection Failed
/home/1/2/3/4/5/6/7/8/9/10/11/12/13/14
Read time out

Sounds like a data underflow. You were trying to put /home/1/2/3/4/5/6/7/8/9/10/11/12/13/14 onto the server, weren't you? Or were you trying to get it? If that's the name you want when you're putting it, all those subdirectories have to exist. But that's not the error you got - it was a read time out. Sounds like a bug in the ftp client, not being able to traverse the subdirectories. Can the shell? In Terminal, can you ls /home/1/2/3/4/5/6/7/8/9/10/11/12/13/14? Can you "more /home/1/2/3/4/5/6/7/8/9/10/11/12/13/14"? (Might look funny, just wonder if the filesystem can get there.)