OS X Lion error: Problem connecting to the server

[JyotiT]

I have just updated my Macbook Pro to OS X Lion. I have been waiting for this moment and finally I got it now. However the issue in my Lion is about message dialog popping up everytime saying that there was a trouble connecting to the server. URLs through the type "file:" are not supported. I don’t know how to solve it?

[Amma-Watson]

If your Mac OS X 10.7 Lion (Developer Preview) used in conjunction with a NAS (QNAP, Synology, etc.) then you will notice that the file shares no longer be accessed via AFP. The moment you connect to an AFP will get an error message indicating that the version of the server is no longer supported. The cause of this 'problem' is tighter security in OS X Lion. The AFP authorization process was derived from DHCAST128. One way that Apple no longer considered safe and therefore is disabled in OS X Lion.

[Saura]

Apple Mac OS X Lion with a list of authentication methods that are no longer allowed. These are mostly older, less secure authentication methods such as SMB and AFP. It is possible that even if you must use one of these methods, for example access to a NAS or Windows server to get old. Using OS X Terminal, it is possible to list the blocked methods to adjust.

[@bLERINA@]

After the start of a new system, it is logical that appear new problems. Well, many users have reported problems with computer networking Windows or Linux using Samba. The reason for these problems is that Samba is not included in OS X Lion as their creators have changed the GPLv3 license that prevents commercial use of it, which has forced Apple has developed its own version. Advanced users can go to the terminal using samba man or samba-help for more information about Apple's implementation or debugging enabled by-debug SMDB true and study the log files to troubleshoot connectivity issues that occur.
So those of you with a NAS device and still you are not in OS X Lion, I recommend you not upgrade to be sure it is fully supported.

[Elijah*Blue]

Connecting via SMB is fine here with the Synology. However it all takes a lot longer. I have a similar problem with the LaCie D2 Disk Network. According to the LaCie website to do with change of network protocols in Lion.

[Jailekhaa]

I have indeed contacted Synology support because I also have problems with my DS107 +. They've confirmed that although there will never be updated for the x07 series for compatibility with Leo, this model is obsolete (the joke) that unlike a higher beta version is already available (DSM 3.2 ). These crafty support conclude that the only solution is to buy a new NAS DS111 take the example of (the equivalent of my DS107 +). Given the excellent brand reputation, I am quite disappointed by this unilateral policy.

[Dritan]

Just found the issue and not whether to laugh or mourn, since the first betas of Lion that I connect with no problem on my samba server (suse 11.4) on my macbook and without making any experiment, all alone and I find the server connects. To top it off I just bought a new MacMini (no optical drive) and it seems that the poor also learns that he cannot connect to my samba server as it takes almost a week without a problem connecting. It seems to me that before launching the rooftops you would have to inform you better.

[Vrushabha]

I would look deeper into the software package netatalk. It is widely used on Linux-based NAS systems. It appears that the latest version of netatalk, which is required in combination with Lion, only recently in the form of source code freely available. NAS vendors were on the other side the possibility to a paid license to purchase in the meantime.

[Appaji]

The problem is that SAMBA is no longer available in Mac OS X 10.7 Lion, and has been replaced by a version created (and owner) of Apple. This substitution is that the Open Source software developers decided to change the license of the software to version GPLv3 , which prevents Apple (and other companies) make commercial use of software which has forced the Cupertino company to create their own proprietary version of the tool. This change SMB license is by far the worst thing that could have made its creator, and that forces a standard Open Source is forced to fragment into multiple deployments in which each developer will include special features that may not be compatible with the protocol implementation in other devices: an electronic Tower of Babel of complex and difficult to resolve.