Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
 Posted - 2002-05-09 : 18:18:23
|
| I have 2 users on a different domain that cannot connect to SQL Server.Both users can ping the SQL Server but when you try to connect it says that the SQL Server cannot be found or access is denied.I tried to setup the connection using TCPIP and it didnt work so I tried NAMEDPIPES, which also did not work.I am trying to setup the connection with a standard login. I can login from my workstation and at the server using the standard logins that I created for these 2 users.MDAC is the correct version for my version of SQL (2000).Is there a restrition on SQL Server 2000 Standard Edition that limits the logins to the same domain that the Server is installed on?Thanks in advance for any comments...DanielSQL Server DBA |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-05-09 : 18:23:49
|
| Have you tried explicitly indicating port 1433 under TCP/IP? The auto port detect might not be working. Also, is there a firewall or something that might be blocking that port? |
 |
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2002-05-09 : 18:25:12
|
quote:
Have you tried explicitly indicating port 1433 under TCP/IP? The auto port detect might not be working. Also, is there a firewall or something that might be blocking that port?
Actually no. I input the port # of our SQL Server. Its not 1433 =)DanielSQL Server DBA |
|
|
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
Posted - 2002-05-10 : 14:05:18
|
quote:
Is there a restrition on SQL Server 2000 Standard Edition that limits the logins to the same domain that the Server is installed on?
Nope. Our SQL 2000 Standard Edition servers are on different domains than our users and it works fine. I'm assuming you're using the Client Network Utility to establish an alias and determine which network library to use, correct?Was there anything else "unusual" about how SQL Server was installed, other than using a different port? Is it a named instance? When you say you setup a "standard" login, are you saying that it is a SQL Server Login as opposed to an NT login?Edited by - AjarnMark on 05/10/2002 14:06:18 |
|
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2002-05-10 : 16:46:05
|
| Ok. Problem solved. The user needed to be setup on the SQL Server in WINDOWS NT with the same password. Once that was done I was able to connect using named pipes.So looks like this was actually a Windows NT problem =)DanielSQL Server DBA |
|
|
|
|
|
|
Problems connection to SQL Server