Can you paste the client Simias.logs for both the test cases in Debug

1) using fqdn

2) using direct IP.

Hi Ravi,

I've attached the various logs in a zip file.

Some notes:

I've since re-ran simias-server-setup, ifolder-web-setup and ifolder-admin-setup.  In each case I replaced https://localhost:443/ or https://192.168.20.6/simias10 with https://server.paventi.net (and appended :443 or /simias10).

After doing this my results are a bit different and this is reflected in the logs.  Here are the specifics.

1) The /admin and /ifolder web login still works with no issues.

2) The fqdn login still fails after quite a lengthy wait period.  The error message is attached in the zip file (ifolder.log).

3) The IP login now fails (this is the difference) after a relatively short wait period.  Previously I would be asked to verify my self issued SSL cert twice and then log in.  Now only the first verification is requested and then there is a failure.  Note that the first request isn't in the log as the cert has been accepted previously on this machine.

I appreciate the help.

James

Hello again,

So I'm continuing my tinkering and attempting to eliminate some of my ignorance.

1) I figured out that the ifolder-*-setup scripts are what determine communication between the remote web browser and the server and then the web application(s) and the ifolder server.

2) Given that my web app and ifolder server are on the same server I don't need SSL between the two ... only between the web app and remote web browser.

http://localhost:80/ is totally appropriate and a bit faster on my atom processor.

3) I re-ran simias-server-setup as I assume that I need "both" for encryption to make the setup above work and let the client connect via SSL.

I'm still having the same results unfortunately.

James

OK … Ravi, so after you asked me to post my client logs with DEBUG mode turned on … I started thinking about troubleshooting the client and not just the server.  I’m not sure why, but I was stuck on troubleshooting the server.  Well, probably because it was the one new change.  I’ve been using the 3.8.0.3 client with my 3.6 server for a few weeks now.

Here’s where I’m at this morning:

-          All of the machines that I’ve been testing the client on are Windows 7 machines.  Two 64 bit and one 32.  When connecting to the server by IP an initial authentication would show in the server logs (as successful) but the client would ultimately fail as the simias-server-setup script had been run with https://fqdn/simias10.  The only way to make an IP connection function was to use https://IP/simias10 when setting up simias.

-          Back to the windows 7 machines.  If I attempted to connect the client by fqdn it would fail and the server would not show any authentication attempt.  I’m not an expert at reading the client logs but the line in my logs (attached a few posts up) that reads “UnknownDomain Host” tends to hint at a DNS problem.  The fact that I can ping by the fqdn, host, IP and even do a reverse lookup on the IP from any host on my network seems to counter this however.

-          This morning I realized that I hadn’t tried a Windows XP host.  I happen to have one (32 bit) running in a VM.  Guess what, I tried it and it worked first try with fqdn.  Hmmmmmmmmmm now I have something to go on.  I wonder if it’s all of the changes that happened to the Windows 7 network stack (Vista for that matter as well) or perhaps the fact that the XP machine has never seen an iFolder client?  The Windows 7 machines have seen 2 – 3 versions each with an existing connection to an iFolder 3.6 server.

I’m off to some other commitments but will continue to hunt for the problem … any and all ideas welcome!

Hi folks,

Here’s where I’m at Sunday evening.  I’ve noticed that my Win 7 computers don’t even register a login (before failing) in the server’s simias.log when using the fqdn.  The successful XP login shows authentication twice.  I re-did simias-server-setup for what must have been the 200^th time and set the encryption option to shut off ssl (nonssl I think).  My thinking was that enough folks on the web report solutions to their issues having a lot to do with SSL setup.

Suddenly my win 7 machines could login!  Well, one of the two login’s would register in the simias log and then fail … but this was something.  I checked the web login and it failed.  I then did three things … one, I re-issued the SSL cert with gensslcert, edited vhost-ssl.conf to show my servers fqdn (it was simply a copy of vhost-ssl.template before this) and used my fqdn for the server name in the simias-server-setup.  I suspect that that last one had nothing to do with things and that editing vhost-ssl.conf had everything but bottom line it now works.  I can log in from win 7.

I would love to know what’s happening if anyone knows.  Even if not though, I’m going to back things out one item at a time and see if I can’t figure it out … more running of simias-server-setup … sigh …

James

Hi,

I have this issue with the client on Mac and Windows.

I've configured ifolder to get the list of users from LDAP (Netscape-Directory) and also from ActiveDirectory separetly.

In both cases I can't login via Mac or Win clients, getting - "An error was encountered while connecting ... please contact your network administrator."

But I can login via browser https://myserver.com/ifolder

I'm lost here.

No one seems to know what could be the problem!!!

This is a long note :) .

web and admin setup can have non SSL if running on same server but for client to connect from win / linux it needs to have SSL cnfigured.

Its always good to use DNS entry than IP in the public and private URL.

Are you able to access http://dns/simias10/Simias.asmx from a browser from the windows machine ?

Hi all,

Here’s what is now working for me.  Since this thread is long, I’ll remind folks what I’m using:

OpenSuse 11.3 x64 and iFolder 3.8.0.3 server / client, openLDAP, Windows 7 x64.

To re-summarize my problem, I was able to use the web interface (both /admin and /ifolder) without trouble.  I could also use the 32 bit client with 32 bit Win XP.  I could not use the client with Windows 7 (x64 or 32).

The solution was to:

1)      Issue an SSL cert that referenced the server’s FQDN.
I.E. gensslcert –n www.mydomain.com

2)      Configure simias for this FQDN.
I.E. simias-server-setup -> https://www.mydomain.com/simias10 -> both the public and private interface

3)      Edit /etc/apache2/vhosts.d/vhosts-ssl.conf
uncomment and edit the ServerName line to read as below
ServerName www.mydomain.com

OK, I pulled this together off of the web since I’m not in front of my server so part of the syntax may be off … I’ll check tonight, PST.

Bottom line, the SSL thing needs to be set up perfectly.

James

THIS WORKED FOR ME!!!

i have the ifolder using local user store and was running into the same issue.

thanks!!