Error - 105 Ifolder
error) Can access iFolder 2.0 with the iFolder Client inside the firewall but not outside the firewall. iFolder is listening on port 52080. Can access the iFolder via a browser by going to http://ipaddressORdns:52080/iFolder or https://ipaddressORdns:52443/iFolder fix Add the CN property to the Public with Read, Compare and Inheritable rights.1- From ConsoleOne, highlightRoot(tree name), right click and select "Trustees of this object"2-Highlight [Public] and select "Assigned Rights"3- Select "Add Property" and click the "Show all properties" check box4- Scroll down, select the "CN" property and click "OK"5- The rights needed are Read, Compare and Inheritable6- Once completed, click OK and OK once again to save the changes. document Document Title: iFolder Client Error: 105(Connection error) Document ID: 10074604 Solution ID: NOVL82234 Creation Date: 16Sep2002 Modified Date: 27May2003 Novell Product Class:NetWareOtherWeb Services disclaimer The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information. Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.
från GoogleLogga inDolda fältSök efter grupper eller meddelanden
the client. If you are getting Unhandled Exception Errors when clicking on various buttons in the client (login, for sure), this should https://nscsysop.hypermart.net/ifolder.html help. My problem started when trying to move from iFolder 3.8 on OES2 to iFolder 3.9 on OES11. The client versions involved probably don't matter so much, but I had issues with the latest (3.9.2) on OES11 (March 2015 patches) as well as the version served up by my OES2 server (all patches to March 2015). The problem happened when I tried to add another iFolder error - server in the Accounts menu. Once I pointed to a new server, my clients had all sorts of crashes. All clients were running on Windows 7 64-bit with latest patches. The problem seems to occur because of conflicting information of some sort in the local simias files stored in the user's home directory. On Windows, that is in a hidden folder under [user]/AppData/Local/Simias. First, uninstall the problem error - 105 iFolder client. You don't have to reboot yet. Next, you need to display hidden files and directories, so you can get to the hidden directory. In Windows 7, go to your Windows home directory and select Organize. In that menu look for Folder and Search Options. Click on View. Enable Show Hidden files, folders and and drives. You should now be able to see the AppData folder in your home directory. Exampls: c:\Users\Craig\AppData Look in AppData/Local. You should fine a simias directory. Delete the simias directory. Note: If someone wants to experiment here, you could try deleting individual files to find what it is that is causing the issue. I'll be happy to modify these instructions to point to the culprit. If you haven't rebooted, do so. If you have, reinstall the iFolder client, reboot and set up the iFolder server in the client again. It should work fine now. You will have to download any available folders again, or merge with existing ones. Ifolder 1.0 - Tip #1 - Moving iFolder from One Server to Another These instructions apply to iFolder 1.0, installed on NetWare 5.1. In the example below, I moved files from a beta2 iFolder server on NetWare 5.