So I've got several independent fileservers. One is a dedicated FTP server and I need to allow FTP connections to another fileserver on my network. I am using an old version of Ipswitch FTP Server (v5.05) and I'm getting it to work. I've established folders and virtual folders within the FTP Server software and the correct user profiles for the new connection but when I attempt to test the connection remotely, all I get is an empty folder. Any ideas what the problem could be everyone?

Who is Participating?

If you can log in successfully but not transfer files or retrieve a directory listing then your control channel is connected and but your data channel is blocked.

0

Bryan_123Author Commented: 2011-03-16

I am able to connect using an FTP client so that may be telling me that there is a "data channel" problem as AlexPace mentioned. Ipswitch Server has 3 different methods for authentication. I'm currently using "Ipswitch WS_FTP Server" for the user database instead of the Windows NT database or the External User Database. I'm guessing that this may be the problem but I afraid if I switch over to the Windows NT database I'll lose all the hundreds of settings and permissions I've setup already for this FTP server. Maybe I need to add a user on the file server I'm trying to connect with to include the Ipswitch WS_FTP Server account?

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

Ok, so I've tried adding a username to the file server I'm trying to connect with to possibly allow permissions for the FTP server on that machine. I'm running into the problem of the fact that there is a character limit on the length of the user name allowed. You can see that I simply cannot type any further (looks like I'd only need 2 more characters anyways). Still I'm not sure this would even work...

It might be easier to connect using a client that has the ability to write a protocol-level log file so you can see what the server is actually saying to the client on a raw level. FTP is a text-based protocol so if you post a protocol log we can help you figure determine the reason the server and the client can't agree.

0

Bryan_123Author Commented: 2011-03-20

Well, it has been determined that it definitely was a permissions problem and simply not solvable as far as doing what we were hoping to perform. There are simply too many clients already using our current FTP server to consider changing our authentication system just for this one task --and the reasoning for keeping a different user database from the existing NT user database is a good one for our needs. Simply put, the reason for the lack of a good connection was permissions and we just aren't willing to correct the problem given the need to keep our current condition working! Thanks everyone for all your help...