Registering a Remote Server With Client Tool

From: CR (jilesjilesjse_at_jilesjsilessef)
Date: 07/03/03 

Date: Wed, 2 Jul 2003 18:27:38 -0400

Can anyone confirm why I had the following experience ...

A user at a workstation running the Personal Edition (client tools only)
tried to register a remote SQL Server using Windows authentication, but
failed. However, when this individual edited the registration properties to
register using the sa account & password, they were successful.

This Windows user was already defined a a valid trusted login in the remote
SQL Server and was also dbo so it wouldn't seem that they should have had
difficulty with the registration process using Windows authentication.

However, I noticed that in the "Connections" tab of the Properties of the
remote server, there is a box checked that reads "Allow other SQL Servers to
connect remotely to this SQL Server using RPC". Well, this user wasn't
really running the Server, but just the client tools only. I didn't think
that it would make a difference, but I went ahead and modified the Personal
Edition running on the Workstation to be a Client AND a Server. Once I did
this, the user was able to successfully register the remote server using
Windows authentication.

Is what I've described above normal and expected?

I'm running SQL Server 2000 Enterprise Edition on the remote server. Both
the remote server and the Personal Edition had SP3 applied. The workstation
in Win2k Professional while the remote server is running on Win2k Advanced
Server at SP3.

One final twist ...

When the remote server was registered locally using the sa account, the user
could create objects on the remote server, but the objects would be owned by
their Windows account (e.g. XYZDOMAIN\User). However, later, when the
remote server was registered successfully with Windows authentication,
objects created by this user had "dbo" for the owner instead of their
Windows account. Why is this? In the first case when the remote server was
registered locally using sa, shouldn't the objects created during this
session effectively been owned by sa and not by XYZDOMAIN\user? We actually
want dbo to appear and the user is defined as dbo so it's not a total
surprise. What is a surprise is why when registered as sa that it didn't
appear as dbo, as well?? Did the fact that the Personal Edition on the
workstation was upgraded to Server and Client from just Client play a role
in this behavior?

Thanks for any input anyone can provide.

Chuck

Relevant Pages

  • Re: 1st hosting of objects, new(), etc.
    ... ASP.Net application dependent on a remote object in a Windows Forms ... > For instance, if my winforms app is the first app to need the object, it> will do a registerWellKnownServerType on a singleton that is also used> locally, and if an IIS application on the same machine runs first, I'll> create a the local object and cache it in the ASP.Net Application object and> then register it. ... > I guess in the case where the hosting app exits, it would cause an exception> on the client, or I could have the process stick around while there are> still non-timed-out clients ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Remote Server shell command
    ... It's a command line tool used to run an executable on a remote PC. ... to do anything on a remote server. ... I have a new Access 2002 client app ...
    (microsoft.public.access.modulesdaovba)
  • Re: Citrix Pen Test,
    ... The way its works is that the client need to connect ... to the remote server through Citrix and run the application. ... I noticed that the Citrix Client used ...
    (Pen-Test)
  • Re: third post: Marshal by value remoting
    ... How To Marshal an Object to a Remote Server by Value by Using Visual Basic ... Sam Santiago ... > of assemly in my computer (in client) and if I change the class to inherit ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: ~/.hosts patch
    ... The problem is that the client application using a port forwarded to ... localhost:port via ssh must connect to that port via the host name of ... the remote server or it will crash the remote server... ...
    (freebsd-current)