Hi all,

I've seen a fair amount of related posts, but none of the suggested
workarounds seem to work for me:

I have the whole SQL Server 2005 Developer Edition suite installed on
an XP Pro machine - the machine is called DELLXP and is in a workgroup
called Torus, although it's the only computer in the network.

I have the Analysis Server running and SQL Server running - both
instances are called 'DELLXP'. My friend comes along with his laptop
which also runs XP Pro and he has the SQL Server 2005 developer edition
tools installed also. When he logs into his laptop it is with a user
and a domain unrelated to my machine (for various reasons, we can't
change this). Through WiFi I want him to be able to connect to the SQL
Server and Analysis Server instances on my machine. In order to do this
I:

- Use the Surface Area configuration tool to allow remote TCP/IP
connections to SQL Server, and allow Local and remote connections for
AS. I also enable anonymous connections for AS.
- Open the related ports on my windows firewall - 1433 and 2383
respectively
- Setup a SQL Server authentication login for my friend
- Enable TCP/IP protocol on the SQL Server Network Configuration under
the services manager

So far so good - he can locate and login to the SQL Server instance.
However, he can't login to the AS instance. I appreciate that AS uses
windows authentication, and it's probably trying to authenticate with
the credentials he used to logon to the laptop with. With this in mind
I try:
- Setting up a 'limited' user on my DELLXP machine with the same name
and password as my friend logs onto his laptop with. This doesn't seem
to help. When my friend tries to connect to the instance from the
laptop through Management Studio, we get the message 'The local
security service cannot be contacted'.
- Trying to start Management Studio on the laptop using 'Run as...'
and trying to run as 'DELLXP/<user>' where <user> is some user on my
DELLXP machine. It doesn't recognise any of the users.

Would anyone have any ideas? The laptop seems 'aware' of DELLXP since
it can access shares and, as indicated above, the SQL Server. I think
this is probably a security/workgroup/domain issue and not really an AS
issue, but I'm at a loss as to what to try next. We don't want to
develop an AS project on the laptop and just use the DELLXP SQL Server
as a datasource since the DELLXP machine has more memory in it and we'd
rather keep everything in one place, but this is looking like our only
option at the moment.

Thanks in advance for any thoughts on this matter.

Cheers,
Matt

Hi again,

Furthermore, in SQL Profiler, when my friend attempts to connect, the
Audit Login event comes up with NTUserName - "ANONYMOUS LOGIN",
NTDomainName - "NT AUTHORITY", and Error - "3238854664"

Incidentally, searching for this error on MSDN doesn't come back with
any results.

Again, thanks in advance for any help here.

Cheers,

Matt

In article <1152032996.386864.157520 (AT) l70g2000cwa (DOT) googlegroups.com>,
matt_j_thomas (AT) hotmail (DOT) com says...
I am guessing that your friend is running as a domain user, not logging
on as a local user on his laptop. A domain account will not map to a
local account on another machine. Only a local account on one machine
will map to a local account on another machine if the username/password
are identical.

Can your friend set up a local user on his laptop with the same username
and password as the 'limited' one on DELLXP and then either use "Run
As..." to run as this local account or log on to the laptop as this
local user? This should get you working as long as the 'limited' user is
in the appropriate AS roles.

--
Regards
Darren Gosbell - SQL Server MVP
Blog: http://www.geekswithblogs.net/darrengosbell

Thanks for your reply Darren.

Darren Gosbell wrote:

Okay - we've set up a local account on that laptop with an identical
account on DELLXP. I've added the DELLXP account as a member of the
server role on the DELLXP analysis server.

My friend does a 'run as...' on Management Studio using the new local
account. He tries to connect to AS on DELLXP and now gets a different
error:

"A connection cannot made. Ensure the server is running.
(Microsoft.AnalysisServices.AdomdClient) -> Unable to read data from
the transport connection: An existing connection was forecably closed
by the remote host.(System) -> An existing connection was forecably
closed by the remote host (System)"

SQL Server Profiler is now recording error: 3239575593 but still for an
ANONYMOUS LOGON and NT AUTHORITY

It seems like a step in the right direction, but I'm still stumped - if
anyone can suggest anything else I certainly appreciate the help.

Cheers,

Matt

Hi Matt,
for some reason Microsoft Analysis Services 2005 allows connections
only through windows authentication. Except creating a domain, another
solution could be to connect via IIS
see: Configuring HTTP Access to SQL Server 2005 Analysis Services on
Microsoft Windows XP

http://www.microsoft.com/technet/pro.../httpssas.mspx


Have you already tried this solution?


Cheers,
Makis




Matt T wrote:

makismarketos wrote:

Hi Makis,

Thanks for posting - no, we haven't tried this route yet. We've ended
up with the AS development happening on the laptop for the rest of the
week so as not to burn any more time on this security issue. We'd still
like to move the AS work back to DELLXP next week though, so I'll take
a look at this on the weekend - thanks for the link.

Cheers,

Matt

When you get back to this issue, Edward Melomed from MS has a good
article on his blog about troubleshooting connection issues, which might
be of assistance.

http://www.sqljunkies.com/WebLog/edw.../26/21447.aspx

--
Regards
Darren Gosbell - SQL Server MVP
Blog: http://www.geekswithblogs.net/darrengosbell

In article <1152115374.840083.6150 (AT) m73g2000cwd (DOT) googlegroups.com>,
matt_j_thomas (AT) hotmail (DOT) com says...