Thank you for the post.
I was able to replicate this with a Windows 7 host and I have forwarded a report to Testing and Development for review.
Can you confirm the FileMaker Server 13 host is still visible, but the database files do not populate in the file list?
Well, interestingly enough, I tried a different 10.7.5 machine today and it worked. Also, I've tried a 10.8 and 10.9 machine which both worked. So there is something specifically goofy about my 10.7.5 machine trying to connect to our Windows 2012 Server Standard machine running Filemaker Server 13. I'm not sure what the problem might be though since we're still using the self-signed FMI certificate and all the other test clients have worked fine.
If there is any sort of debugging I could enable to grab more information, let me know.
I may be jumping the gun a bit but since TSFalcon was able to replicate the issue....
An entry in the Known Bugs List has been linked to this Issue Report. Any Comments/Questions/Suggested Corrections should be posted here or in a new thread. Please do not post such comments to the Known Bugs List thread.
Thank you for the replies.
I apologize, but the network in my test environment was misconfigured. I am no longer able to replicate. Today everything is working as expected.
Were you ever able to connect with the problematic Mac OS X 10.7.5 machine?
And thus, I will close this report in the Known Bugs List, but keep it in the system just in case new details arise...