Your best friend for file transfer.Fetch
Connection Problem to Windows machine (4 posts)
- Started 8 years ago by agruler
- Latest reply 8 years ago from Scott McGuire
I am trying to connect to an ftp server that was set up yesterday by a client of mine. I am able to connect (or so it says) however, the server times out. I would automatically say that the server is causing the issue, except that you are able to ftp via a windows computer.
I looked on the forums first, and already have tried to use fetch and terminal to log on. The server should require a username and password, but terminal doesn't prompt me for one. I have posted the results:
iGens-MacBook-Pro:~ Goon$ ftp 18.104.22.168
Connected to 22.214.171.124.
421 Service not available, remote server timed out. Connection closed
Fetch 5.3 (5D161) Intel running on Mac OS X 10.5.2 (9C7010) Intel English
StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
Partial serial FETCH5X001-J6RU-VC8D T
Connecting to 126.96.36.199 port 21 (Mac OS X firewall is allowing connections) (5/21/08 10:32:03 AM)
Connected to 188.8.131.52 port 21 (5/21/08 10:32:05 AM)
Update check skipped at 05/21/2008 10:32 AM (next check after 05/22/2008 12:13 AM)
This is all I get from the transcript. Fetch just tells me that the server timed out. Is there any specific way to set up a Windows machine to allow Fetch to connect?
Any help would be greatly appreciated!
Scott McGuire Administrator
This does look like a server setup problem - something is not happening on the server after the Mac has connected that is causing the connection to fail at some point during the connection process.
Unfortunately, we're not familiar with setting up Windows FTP servers, so I can't offer you immediate advice, although I can tell you that we know other folks have set up Windows servers that Fetch can connect to.
But if you can provide some more information we will try to give advice about potential causes.
My first question is... you say that a Windows computer can FTP to the server. Are the Windows server that can connect successfully, and the Mac that cannot connect successfully, on the same network?
Thanks for the quick reply.
The Windows machine and my mac are not on the same network. I have tried to connect my mac from 2 different networks, though.
I have no experience setting up a Windows server either ( I am a mac only tech ) But I also have a feeling that the server is the issue. However, I cannot think of anything that should be different between the two systems. FTP should be FTP.
I will let you know when I find out more.
Scott McGuire Administrator
By any chance is the Windows machine that connected successfully on the same network as the FTP server, but the Mac is not?
If the Windows machine is on the same network as the FTP server, I might suspect it's a problem between being on the same network vs. being on a different network, and the next thing that should be tested would be to see if a Windows machine that is not on the same network as the server can connect successfully.
If the Windows machine that worked is already on a different network, then I don't know what to suggest except get a transcript from the Windows machine and we can look and see if we see what might be different.
My guess is it's not really a Mac vs. Windows difference (because the command line FTP client on the Mac and Fetch use different methods for establishing connections to a server), but without further info it's hard to say that for sure.
One thing you might want to check is to make sure that you shouldn't be connecting using SFTP instead of FTP; might not hurt to try changing Fetch's connection method to SFTP and see if that helps.
Please let us know if we can be of further assistance.
- Page 1