ftp and ping timeouts
I have similar issues, although different.
I'm running a xserve blade with 10.5 server. Recently a coworker discovered that a person cannot FTP to the server. Our testing has been done using terminal and the ftp commands. The original user that first started having troubles uses a GUI interface of some kind. I have yet to learn which.
If I start pinging the server, and then ftp to the server using the 'broken' account, the ftp would fail saying bad username and password combination. In addition, the machine would stop responding to pings. The only way to get a connection to the ftp or a response from pings would be to restart the server. The same thing would happen with an account that was supposed to be an admin account.
We eventually figured out that accessing the server with ftp was a problem with permissions and the length of the password for the "broken" account.
Now when we ftp to the server, we can connect with the account just fine. However it does not show share points. It only shows the home directory. In addition, if you fail to get the password correct the first time, everything seems to freeze. We can have a series of pings in the background. Once the login fails, not only can you not reestablish an ftp connection, but the pings become unresponsive.
As a result, you cannot fail your first attempt to logon through ftp. If you do, the server must be restarted before it will allow you to attempt another login. Any ideas why it will not allow you to reattempt the password? Why I would have to restart my server after each failure?
I'm running a xserve blade with 10.5 server. Recently a coworker discovered that a person cannot FTP to the server. Our testing has been done using terminal and the ftp commands. The original user that first started having troubles uses a GUI interface of some kind. I have yet to learn which.
If I start pinging the server, and then ftp to the server using the 'broken' account, the ftp would fail saying bad username and password combination. In addition, the machine would stop responding to pings. The only way to get a connection to the ftp or a response from pings would be to restart the server. The same thing would happen with an account that was supposed to be an admin account.
We eventually figured out that accessing the server with ftp was a problem with permissions and the length of the password for the "broken" account.
Now when we ftp to the server, we can connect with the account just fine. However it does not show share points. It only shows the home directory. In addition, if you fail to get the password correct the first time, everything seems to freeze. We can have a series of pings in the background. Once the login fails, not only can you not reestablish an ftp connection, but the pings become unresponsive.
As a result, you cannot fail your first attempt to logon through ftp. If you do, the server must be restarted before it will allow you to attempt another login. Any ideas why it will not allow you to reattempt the password? Why I would have to restart my server after each failure?
Xserve Blade, Mac OS X (10.5.2), Server edition