|
|
You're in the
sql server connect
group:Client connect to SQL SERVER 2000
sql server connect:
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... [quoted text, click to view] > 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 [quoted text, click to view] "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... > > 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 > > > >
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... [quoted text, click to view] > 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... >> > 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,
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 [quoted text, click to view] "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... > > 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... > >> > 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 > >> > > >> > >> > >> > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |