This discussion is archived
890 Views 4 Replies Latest reply: Jul 20, 2009 7:11 AM by dasein
Try and narrow the problem down. To see if the problem is just with Cyberduck, try connecting from Terminal.app with the format:
For this example you would type anonymous for the login and firstname.lastname@example.org for the password. To end the session type exit.
If you are able to connect fine with Terminal.app then the problem is somewhere with the Cyberduck application - probably a preference setting.MacPro 2 x 3GHz Quad-Core, MacBook Pro 2.6, Mac OS X (10.5.7)
Thanks, b3avls. I have tried that and it still opens a connection but won't let me fully login. If I go to my 10.4.11(cyberduck v 2.8.1) or Compaq WindowsXP (SmartFtP) I get in with no trouble at all. I'm befuddled. It seems something to do with either Leopard or Cyberduck's ability to work in Leopard.MB & iMac 2.8 24", Mac OS X (10.5.5)
How are the leopard machines connected? Wireless, Ethernet? Are the Leopard machines on the same subnet as the Windows and Tiger machines? Are they using the same DNS server?
You can try nslookup from Terminal.app on both Tiger and Leopard machines and see how long it takes for both to respond.MacPro 2 x 3GHz Quad-Core, MacBook Pro 2.6, Mac OS X (10.5.7)
Wireless (AT&T 2Wire) for all. Never had a major problem so far with that aspect of the network. Same DNS. I'll try nslookup next. When I was playing around with it, it was interesting that it claims it's connected (wouldn't let me try and reconnect until I closed the current session), yet kept asking for a login password under Leopard in spite of that. Can't find anyone on the Cyberduck forums to help. Filezila, same situation all round with the same machines. Thanks.MB & iMac 2.8 24", Mac OS X (10.5.5)