Monday, March 12, 2012
How can we administrate SQL remotely?
customer has a W2k SBS with SQL installed. We recently
installed McAfee Protection Pilot, which uses SQL as data
storage for the client configurations. All works well.
Our problem is, that we can logon as local admin and open
this database OK. But when we connect via terminal server,
log in as admin and try to open the database we get the
error: "You can not log on as database administrator. Make
sure that your are logged in as local administrator".
Is there a way to overcome this "logon as local admin"
requirement? How else could one administrate the SQL
database remotely?
Thanks
Wolf
Make sure you have TCP/IP setup in sql client config.
Make sure you have Authentication mode setup to "Windows and SQLServer"
"w.haunzwickl" <anonymous@.discussions.microsoft.com> wrote in message
news:afd501c49991$d00bd300$a601280a@.phx.gbl...
> Hi,
> customer has a W2k SBS with SQL installed. We recently
> installed McAfee Protection Pilot, which uses SQL as data
> storage for the client configurations. All works well.
> Our problem is, that we can logon as local admin and open
> this database OK. But when we connect via terminal server,
> log in as admin and try to open the database we get the
> error: "You can not log on as database administrator. Make
> sure that your are logged in as local administrator".
> Is there a way to overcome this "logon as local admin"
> requirement? How else could one administrate the SQL
> database remotely?
> Thanks
> Wolf
Friday, March 9, 2012
How can we administrate SQL remotely?
customer has a W2k SBS with SQL installed. We recently
installed McAfee Protection Pilot, which uses SQL as data
storage for the client configurations. All works well.
Our problem is, that we can logon as local admin and open
this database OK. But when we connect via terminal server,
log in as admin and try to open the database we get the
error: "You can not log on as database administrator. Make
sure that your are logged in as local administrator".
Is there a way to overcome this "logon as local admin"
requirement? How else could one administrate the SQL
database remotely?
Thanks
WolfMake sure you have TCP/IP setup in sql client config.
Make sure you have Authentication mode setup to "Windows and SQLServer"
"w.haunzwickl" <anonymous@.discussions.microsoft.com> wrote in message
news:afd501c49991$d00bd300$a601280a@.phx.gbl...
> Hi,
> customer has a W2k SBS with SQL installed. We recently
> installed McAfee Protection Pilot, which uses SQL as data
> storage for the client configurations. All works well.
> Our problem is, that we can logon as local admin and open
> this database OK. But when we connect via terminal server,
> log in as admin and try to open the database we get the
> error: "You can not log on as database administrator. Make
> sure that your are logged in as local administrator".
> Is there a way to overcome this "logon as local admin"
> requirement? How else could one administrate the SQL
> database remotely?
> Thanks
> Wolf
How can one Connect (remotely) to SQLExpress which is installed on "Windows XP Home"
Hi all,
I have to deal with a private network of laptops which are all equiped with preinstalled "Windows XP home"
I've installed SQLExpress on one of these, but I cannot connect on it from the rest of the laptops. (I've successfuly done this with "Windows XP profesional" though, and local connections work fine as well).
I've already setup the SQLExpress to accept conections throuigh TCP/IP but I can not think of something else. (Security comes to mind, but I do not know how to resolve it on "Windows XP Home").
Thank you
Ioannis
Allow port 1433 and 1434 for TCP to come though as this should be blocked by the firewall by default. Try this first by disabling the firewall for a moment to see if this is the case.HTH, Jens Suessmeyer.
http://www.sqlserver2005.de|||
Hi Ioannis,
Did opening the firewall solve this issue for you?
Regards,
Mike Wachal
SQL Express team
-
Mark the best posts as Answers!
Hi,
The firewall was already wide open!
What solved my problem was starting the "Browser" service.
Is this service supposed to be "down" by default?
thank you both for your kind responses
Ioannis
|||That is a question of settings in the setup during the installation, you can check the service to autimatically startup, if you don′t it will put it on Manual.HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||Yes, this is by design.
SQL Express installs with the minimum external exposure possible. We also have remote connections disabled by default.
Mike
How can one Connect (remotely) to SQLExpress which is installed on "Windows XP Home&quo
Hi all,
I have to deal with a private network of laptops which are all equiped with preinstalled "Windows XP home"
I've installed SQLExpress on one of these, but I cannot connect on it from the rest of the laptops. (I've successfuly done this with "Windows XP profesional" though, and local connections work fine as well).
I've already setup the SQLExpress to accept conections throuigh TCP/IP but I can not think of something else. (Security comes to mind, but I do not know how to resolve it on "Windows XP Home").
Thank you
Ioannis
Allow port 1433 and 1434 for TCP to come though as this should be blocked by the firewall by default. Try this first by disabling the firewall for a moment to see if this is the case.HTH, Jens Suessmeyer.
http://www.sqlserver2005.de|||
Hi Ioannis,
Did opening the firewall solve this issue for you?
Regards,
Mike Wachal
SQL Express team
-
Mark the best posts as Answers!
Hi,
The firewall was already wide open!
What solved my problem was starting the "Browser" service.
Is this service supposed to be "down" by default?
thank you both for your kind responses
Ioannis
|||That is a question of settings in the setup during the installation, you can check the service to autimatically startup, if you don′t it will put it on Manual.HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||Yes, this is by design.
SQL Express installs with the minimum external exposure possible. We also have remote connections disabled by default.
Mike