trouble connecting Excel to Analysis Services server

We have an SSAS server with a cube deployed on a server over the WAN.. We are trying to connect to the cube from Excel on various client workstations. The server is not on a domain with the clients. It "works" for some of us but not for others. We are trying and failing yet to determine what the difference is on the machines that work versus the ones that don't. However, even for the ones that work, it isn't as seamless as we think it should be. I'll explain:

In Excel, we use the Data-Other Sources-Analysis Server option, which presents us with the standard dialog: standard dialog http://www.freeimagehosting.net/uploads/de3420ec26.gif

Now, we believe the firewall and server settings are correct, because we are then presented with the dialog which lets you pick which cube to use from the server: pick a cube dialog http://www.freeimagehosting.net/uploads/882a09ee7f.gif

And, clicking "Finish" lets Excep being to work with the cube, as evidenced by the standard Excel dialog: all seems OK http://www.freeimagehosting.net/uploads/fdf4626609.gif

But then we are presented with the dreaded "transport layer error" message: transport layer error http://www.freeimagehosting.net/uploads/243d5f3d49.gif

Note that this error appears even on the mach开发者_Python百科ines that "work." What makes them "work" is that after clicking OK on that dialog, the next dialog appears: mysterious new dialog http://www.freeimagehosting.net/uploads/b8fc6bae18.gif

Once this dialog appears, you re-enter your password, and everything "just works" after that. While I'd like it to "just work" without that second dialog, at least it works... But on many machines we've tested this new dialog never comes up. Instead, they just get the following error message, leaving them out of luck: final error http://www.freeimagehosting.net/uploads/601b9294e3.jpg

Can anyone offer any advice for this? Thanks!

---

Do the connections work if you allow "NT Authority/Authenticated Users" or "NT Authority/Anonymous Logon" to connect? Would help troubleshooting at least, but it's not a great idea to leave it like that ;)