cluster manager and sql authentication

I am a newbie to clustering so I hope this makes sense. Does the Cluster
Manager have to be in the sysadmin role? If not, what are the roles that it
does require?
Thanks for any guidance.
Neil
The Cluster Service must be a local admin on each server. The Cluster
Manager application is an MMC snap-in and can run wherever. Specific
cluster functions may need specific security role membership. I generally
give the person who administers a Cluster local administrator rights on each
node.
Geoff N. Hiten
Microsoft SQL Server MVP
"Neil W." <neilw@.netlib.com> wrote in message
news:%23VNuQeCeFHA.2604@.TK2MSFTNGP15.phx.gbl...
>I am a newbie to clustering so I hope this makes sense. Does the Cluster
> Manager have to be in the sysadmin role? If not, what are the roles that
> it
> does require?
> Thanks for any guidance.
> Neil
>
>
|||Thanks for the reply. The cluster manager appears to login with Windows
login: domain\Cluster. However, I cannot locate a domain user or a local
user named "Cluster". Am I missing something?
______________________
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in message
news:usU0lhCeFHA.1136@.TK2MSFTNGP12.phx.gbl...
The Cluster Service must be a local admin on each server. The Cluster
Manager application is an MMC snap-in and can run wherever. Specific
cluster functions may need specific security role membership. I generally
give the person who administers a Cluster local administrator rights on each
node.
Geoff N. Hiten
Microsoft SQL Server MVP
"Neil W." <neilw@.netlib.com> wrote in message
news:%23VNuQeCeFHA.2604@.TK2MSFTNGP15.phx.gbl...
>I am a newbie to clustering so I hope this makes sense. Does the Cluster
> Manager have to be in the sysadmin role? If not, what are the roles that
> it
> does require?
> Thanks for any guidance.
> Neil
>
>
|||Are you sure? The cluster service account should be a domain-level account
with local admin rights on each node. There should be a domain account that
matches the service account.
Geoff N. Hiten
Microsoft SQL Server MVP
"Neil W." <neilw@.REMOVEnetlib.com> wrote in message
news:eK6Ut7CeFHA.1448@.TK2MSFTNGP14.phx.gbl...
> Thanks for the reply. The cluster manager appears to login with Windows
> login: domain\Cluster. However, I cannot locate a domain user or a local
> user named "Cluster". Am I missing something?
> ______________________
> "Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in message
> news:usU0lhCeFHA.1136@.TK2MSFTNGP12.phx.gbl...
> The Cluster Service must be a local admin on each server. The Cluster
> Manager application is an MMC snap-in and can run wherever. Specific
> cluster functions may need specific security role membership. I generally
> give the person who administers a Cluster local administrator rights on
> each
> node.
> Geoff N. Hiten
> Microsoft SQL Server MVP
>
> "Neil W." <neilw@.netlib.com> wrote in message
> news:%23VNuQeCeFHA.2604@.TK2MSFTNGP15.phx.gbl...
>
>

Client connect to SQL SERVER 2000

Hello,
I have one SQL Server 2000 that has been installed into a domain,
having allowed "Windows and SQL Server" authentication and using as
connectivity options Named Pipes and TCP/ip - 1433
On every client computer that is also a domain member I can set up
without any problems DSNs (data source names), and connect to the SQL Server.
My problem is on another computer that is not a member of this
domain and on which I can not set any kind of connections to SQL Server, I`ve
tried setting up also a DSN (using an SQL Server account)and connect from
Excel and even install the SQL Server Connectivity Tools, and tried with
Query Analyzer but still I wasnt able to connect to the server.
The error I get is: Unable to connect to the SQL Server: The
server doesn't exist or access denied.
It must be some SQL Server specific settings as the network
connectivity is OK
Any ideas ...?
Thank You,
Razvan Dragomir,
MCSA, Exchange & Windows System Administrator
Try connecting to sql from the non-domain box using QA and an explicit
login. If it works, then try same login and password from your app as
opposed to using windows auth.
TheSQLGuru
President
Indicium Resources, Inc.
"Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
message news:F249BDA3-6D56-41E4-85E0-79110A1A9404@.microsoft.com...
> Hello,
> I have one SQL Server 2000 that has been installed into a domain,
> having allowed "Windows and SQL Server" authentication and using as
> connectivity options Named Pipes and TCP/ip - 1433
> On every client computer that is also a domain member I can set up
> without any problems DSNs (data source names), and connect to the SQL
> Server.
> My problem is on another computer that is not a member of this
> domain and on which I can not set any kind of connections to SQL Server,
> I`ve
> tried setting up also a DSN (using an SQL Server account)and connect from
> Excel and even install the SQL Server Connectivity Tools, and tried with
> Query Analyzer but still I wasnt able to connect to the server.
> The error I get is: Unable to connect to the SQL Server: The
> server doesn't exist or access denied.
> It must be some SQL Server specific settings as the network
> connectivity is OK
> Any ideas ...?
> Thank You,
> --
> Razvan Dragomir,
> MCSA, Exchange & Windows System Administrator
>
|||Hi,
I tried and it doesnt work (i`ve used a valid SQL Login)...there is
another interesting thing..SQL is set to answer on port 1433 (default), but
if I scan this port from the non-domain workstation it`s like it`s not
opened, but it`s the same if i scan it from inside the domain where it also
doesn`t respond but I can Connect though...
Razvan Dragomir,
MCSA, Exchange & Windows System Administrator
"TheSQLGuru" wrote:

> Try connecting to sql from the non-domain box using QA and an explicit
> login. If it works, then try same login and password from your app as
> opposed to using windows auth.
>
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
> message news:F249BDA3-6D56-41E4-85E0-79110A1A9404@.microsoft.com...
>
>
|||Firewall issue seems most likely culprit. Or TCP/IP isn't enabled as a
network protocol in sql server? Can you connect using QA and explicit ip
address as the server name?
TheSQLGuru
President
Indicium Resources, Inc.
"Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
message news:FBA2A6A8-90DF-4316-BF0A-B82ECB0D2D9C@.microsoft.com...[vbcol=seagreen]
> Hi,
> I tried and it doesnt work (i`ve used a valid SQL Login)...there is
> another interesting thing..SQL is set to answer on port 1433 (default),
> but
> if I scan this port from the non-domain workstation it`s like it`s not
> opened, but it`s the same if i scan it from inside the domain where it
> also
> doesn`t respond but I can Connect though...
> --
> Razvan Dragomir,
> MCSA, Exchange & Windows System Administrator
>
> "TheSQLGuru" wrote:
|||Hi,
Thx for the answers.....I don`t have any firewall between the
workstations and the server, I`m using TCP/IP and Named Pipes, and it`s
working to connect with IP address from QA, from inside the domain...I also
don`t have any firewall set for non domain clients...I`m just thinking if by
default Win2k3/SQL Server blocks connections from outside the domain...
Razvan Dragomir,
MCSA, Exchange & Windows System Administrator
"TheSQLGuru" wrote:

> Firewall issue seems most likely culprit. Or TCP/IP isn't enabled as a
> network protocol in sql server? Can you connect using QA and explicit ip
> address as the server name?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
> message news:FBA2A6A8-90DF-4316-BF0A-B82ECB0D2D9C@.microsoft.com...
>
>

Client connect to SQL SERVER 2000

Hello,
I have one SQL Server 2000 that has been installed into a domain,
having allowed "Windows and SQL Server" authentication and using as
connectivity options Named Pipes and TCP/ip - 1433
On every client computer that is also a domain member I can set up
without any problems DSNs (data source names), and connect to the SQL Server
.
My problem is on another computer that is not a member of this
domain and on which I can not set any kind of connections to SQL Server, I`v
e
tried setting up also a DSN (using an SQL Server account)and connect from
Excel and even install the SQL Server Connectivity Tools, and tried with
Query Analyzer but still I wasnt able to connect to the server.
The error I get is: Unable to connect to the SQL Server: The
server doesn't exist or access denied.
It must be some SQL Server specific settings as the network
connectivity is OK
Any ideas ...?
Thank You,
--
Razvan Dragomir,
MCSA, Exchange & Windows System AdministratorTry connecting to sql from the non-domain box using QA and an explicit
login. If it works, then try same login and password from your app as
opposed to using windows auth.
TheSQLGuru
President
Indicium Resources, Inc.
"Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
message news:F249BDA3-6D56-41E4-85E0-79110A1A9404@.microsoft.com...
> Hello,
> I have one SQL Server 2000 that has been installed into a domain,
> having allowed "Windows and SQL Server" authentication and using as
> connectivity options Named Pipes and TCP/ip - 1433
> On every client computer that is also a domain member I can set up
> without any problems DSNs (data source names), and connect to the SQL
> Server.
> My problem is on another computer that is not a member of this
> domain and on which I can not set any kind of connections to SQL Server,
> I`ve
> tried setting up also a DSN (using an SQL Server account)and connect from
> Excel and even install the SQL Server Connectivity Tools, and tried with
> Query Analyzer but still I wasnt able to connect to the server.
> The error I get is: Unable to connect to the SQL Server: The
> server doesn't exist or access denied.
> It must be some SQL Server specific settings as the network
> connectivity is OK
> Any ideas ...?
> Thank You,
> --
> Razvan Dragomir,
> MCSA, Exchange & Windows System Administrator
>|||Hi,
I tried and it doesnt work (i`ve used a valid SQL Login)...there is
another interesting thing..SQL is set to answer on port 1433 (default), but
if I scan this port from the non-domain workstation it`s like it`s not
opened, but it`s the same if i scan it from inside the domain where it also
doesn`t respond but I can Connect though...
--
Razvan Dragomir,
MCSA, Exchange & Windows System Administrator
"TheSQLGuru" wrote:

> Try connecting to sql from the non-domain box using QA and an explicit
> login. If it works, then try same login and password from your app as
> opposed to using windows auth.
>
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
> message news:F249BDA3-6D56-41E4-85E0-79110A1A9404@.microsoft.com...
>
>|||Firewall issue seems most likely culprit. Or TCP/IP isn't enabled as a
network protocol in sql server? Can you connect using QA and explicit ip
address as the server name?
TheSQLGuru
President
Indicium Resources, Inc.
"Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
message news:FBA2A6A8-90DF-4316-BF0A-B82ECB0D2D9C@.microsoft.com...[vbcol=seagreen]
> Hi,
> I tried and it doesnt work (i`ve used a valid SQL Login)...there is
> another interesting thing..SQL is set to answer on port 1433 (default),
> but
> if I scan this port from the non-domain workstation it`s like it`s not
> opened, but it`s the same if i scan it from inside the domain where it
> also
> doesn`t respond but I can Connect though...
> --
> Razvan Dragomir,
> MCSA, Exchange & Windows System Administrator
>
> "TheSQLGuru" wrote:
>|||Hi,
Thx for the answers.....I don`t have any firewall between the
workstations and the server, I`m using TCP/IP and Named Pipes, and it`s
working to connect with IP address from QA, from inside the domain...I also
don`t have any firewall set for non domain clients...I`m just thinking if by
default Win2k3/SQL Server blocks connections from outside the domain...
--
Razvan Dragomir,
MCSA, Exchange & Windows System Administrator
"TheSQLGuru" wrote:

> Firewall issue seems most likely culprit. Or TCP/IP isn't enabled as a
> network protocol in sql server? Can you connect using QA and explicit ip
> address as the server name?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Razvan Dragomir" <RazvanDragomir@.discussions.microsoft.com> wrote in
> message news:FBA2A6A8-90DF-4316-BF0A-B82ECB0D2D9C@.microsoft.com...
>
>