Vista, 18452 And The Remote Domain
Jan 19, 2007
Hello
We have a setup of two very separate domains, they are connected via a couple of routers, we connect to the remote domain mainly for administration mostly via remote desktop.
We setup the same user name & password on both domains, with XP as the operating system we can setup the sql link via odbc using windows authentication which works fine, a couple of PC's have now been upgraded to Vista but the increased security stops this from working, we now get error 18452 error code with the user name of "null" I assume vista has stopped the passing of local credentials to what it considers an untrusted domain, fair enough, does anyone know a way of either adding another trusted domain to Vista ? I do not want to setup an AD trust between the two.
Thanks for any help
John
View 9 Replies
ADVERTISEMENT
Apr 7, 2008
Sorry I didn't know the best forum for this question.
I have 3 SQL 2005 x64 servers on my remote domain.
10.1.10.65 is the primary
10.1.10.66 is the mirror
10.1.10.67 is the whitness.
All 3 machines run the MSSQLSERVER service as a domain admin user acount, and all of the other servies use LocalSystem.
All machines are configured to use the default instance name of MSSQLSERVER.
I have another seperate server ON THAT DOMAIN which runs IIS and ASP Classic.
I installed the SQL Native client on that machine.
Here is the ASP code:
-----------
<%
dim strConnString, objConn, rs, sql
strConnString = "Provider=SQLNCLI;Persist Security Info=False;User ID=sa;password=MyPassword;Initial Catalog=LCR;Data Source=10.1.10.65; Failover Partner=10.1.10.66"
sql = "SELECT * FROM DFW"
Set objConn = CreateObject("ADODB.Connection")
objConn.ConnectionString = strConnString
objConn.CommandTimeout = 300
objConn.Open
SET rs = Server.CreateObject("ADODB.Recordset")
rs.CursorLocation = 3
rs.Open sql, objConn
Do While Not rs.EOF
Response.Write rs(0) & "
"
rs.MoveNext
Loop
rs.close
objConn.close
set objConn = nothing
set rs = nothing
%>
--------------------------------
If I run this code on the server on the SAME domain and shutdown MSSQL services on the primary machine the Failover server starts working an serving data requests.
It I then take that code and run it from another REOMTE domain, I can connect to the primary server and get data, but when I force a failover for testing it refuses to connect the the MIRROR server.
In the error log on the primary server I see 12 errors.
There are 4 sets of the following 3 errors, as SQL will try to connect 4 times before failing.
1)
Date 4/7/2008 12:00:39 PM
Log SQL Server (Current - 4/7/2008 12:00:00 PM)
Source Logon
Message
Login succeeded for user 'sa'. Connection: non-trusted. [CLIENT: 10.1.3.79]
2)
Date 4/7/2008 12:00:39 PM
Log SQL Server (Current - 4/7/2008 12:00:00 PM)
Source Logon
Message
Error: 18456, Severity: 14, State: 16.
3)
Date 4/7/2008 12:00:39 PM
Log SQL Server (Current - 4/7/2008 12:00:00 PM)
Source Logon
Message
Login failed for user 'sa'. [CLIENT: 10.1.3.79]
Why does this work when the code runs on the LOCAL domain only when I'm connecting via SQL Security?
Thanks for any help.
John Rossitter
View 3 Replies
View Related
Jun 14, 2007
Hi,
Is that possible to execute SSIS packages from a remote SQL Server 2005 in another domain at local computer (Windows XP)?
Can I use SQL authentication to connect to the remote SSIS? My problem is, the user who execute the SSIS is not allow to access to SQL server directly. Is that possible to code everything in a batch file instead?
I tried to use web services to execute the remote SSIS but it always return "authentication error"?
Can someone help?
Many thanks!
Regards,
Mashmallow
View 3 Replies
View Related
Apr 6, 2008
Hi all. I am a bit new to SQL but I have studied much info, BOL, various best practices and so on. The problem is - I cannot find any tutorial which could tell me step by step how to set SQL server on a PC and connect to it from another computer (they all are on a domain). So I decided that I am doing something wrong...
I have done the following (all is done on virtual PCs):
1.I have installed a virtual PC with windows 2003, which acts as a domain controller.
2.I installed Win2003 on a second PC and added it to the domain. Installed MS SQL Server 2005 and SP2 on it. Server uses Windows auth. and all the services are running from a dedicated domain account which I added on the first PC.
I added a domain account (let's call it USER_X) to the SQL server Security/Logins
Everything is OK locally, I can connect to the server using USER_X from the same PC.
3.I installed Win2003 on a second PC and added it to the domain. Installed MS SQL Server 2005 client componenst, SSMS and SP2 on it. Logged on as USER_X. And tried to connect to the PC number 2. And failed. SSMS gives an error (1396) Named pipes error "Could not open a connection to SQL server". But the server appears on the list if I click Server name->Browse for more->Network servers. Why I cannot connect to it if I see it?
Tried to enable Windows and SQL auth, created a pure SQL user USER_Y, checked locally - ok, can connect. But cannot connect as USER_Y from the third PC.
Finally
4.I installed Win2003 on a fourth PC (did not add it to the domain). Installed MS SQL Server 2005 and SP2 on it. Server uses Windows and SQL auth. Enabled Windows and SQL auth, again created a pure SQL user USER_Y, checked locally - ok, can connect. And checked connection from the third PC - I can connect fine as SQL USER_Y to the SQL server on a PC which is not on the domain but cannot connect as SQL USER_Y to the SQL server on a PC which is on the domain!
What am I doing wrong? How to connect from a PC on a domain to another SQL server on the same domain? It is just a basic config which (I think) SQL admins have gone through many times but I am stuck.
Help, please! I hope to hear from someone who has installed SQL server on a domain and successfully created remote connections.
Thanks.
View 5 Replies
View Related
Feb 16, 2007
Hi, I have been creating a web store, which we will be hosting on our Windows Server 2003 system. I am also writing a windows application that will be running on our client systems on the same network/domain. I have no need to allow internet access to the database, just within our domain. Pretty much the windows application will be running and whenever a customer places an order, the program will automatically pop-up the needed information for our credit card processing, and shipping department. So far I have been able to establish a connection to our server by creating a data connection under the server explorer. However, it does not list any databases whatsoever, the web site has been published using Visual Studio 2005 Professional on the server, and is in 100% working order. I have searched and haven't found anything concrete on this, i'm sure its just something simple that im missing. It appears that the server is definetely connected to the database (since the website is fully functional), but it is not listing the information for other systems to access it. If anyone has any ideas, please let me know. Thank you
View 8 Replies
View Related
Feb 11, 2007
Hi,
Sorry if this is the wrong forum.
I'm trying to connect to a remote server (on shared hosting) with Management Studio Express. I tried using it on Vista and it connects to the server and database perfectly. However, on Vista it gives the following error everytime:
TITLE: Connect to Server------------------------------
Cannot connect to sgc.gbdns.net.
------------------------------ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
------------------------------BUTTONS:
OK------------------------------
However, the host obviously has SQL server to allow remote connections as I'm able to connect from XP.
Both the XP and Vista PCs are running Avast free edition (the same builds) and both are running Windows firewall with management studio allowed through. Can anyone help?
View 6 Replies
View Related
Mar 19, 2007
Hello
I use SQL 2005 - SQL Server Management Studio to connect to my hosting SQL Server to manage my database , its about 1 month which I have installed Vista and SQL 2005 its working fine in local , but today I just wanted to connect to my remote server and I got this error :
Cannot connect to <My server IP Address>
I thought its a server problem , but its not. I tested it by connecting using same SQL 2005 on a windows xp system , the problem is only in vista,
by the way its SQL 2005 SP2
what can I do to solve this prob
View 11 Replies
View Related
Jan 3, 2008
We have a problem to connect to a specific database on our local network from a specific Vista machine. Several other XP and Vista machines are able to connect to the database without any problem. However, with the two latest Vista machines we received, it is impossible to connect to the database. In Microsoft SQL server Management studio express, we have the error 26 "error locating server/instance specified". We are sure the server name we entered is correct. We suppose the server is correctly configured as we are able to connect from other computers. From the machines that are not able to connect to the database, we can connect without problem to other databases. We also see the server, where the database is, on the network servers list in Microsoft SQL server Management studio. .
The version of the components are:
Microsoft SQL Server Management Studio Express 9.00.3042.00
Microsoft Data Access Components (MDAC) 6.0.6000.16386 (vista_rtm.061101-2205)
Microsoft MSXML 3.0 4.0 6.0
Microsoft Internet Explorer 7.0.6000.16575
Microsoft .NET Framework 2.0.50727.312
Operating System 6.0.6000
We verified we have the same version of components on the Vista machine from which the connection is successful.
The network database has the version 8.0.
We are usinng sql server authentification method.
We try to specify the IP address instead of the server name in the connection string. We also tried to specify the port.
We also tried to disable the firewall.
Unfortunatetly, we are not able to connect to this database. Any suggestion ?
View 3 Replies
View Related
Mar 27, 2007
Hi,
I have the following scenario in my lab:
1. Windows Vista Ultimate with an fresh SQL 2005 Express SP2;
2. Developer machine with Windows XP and SQL Manag. Studio.
Problem:
Windows Vista isn't allowing a SQL connection from XP >> Vista.
I've tried:
1. Configured surface area (the same configurations works on XP);
2. Configured all services and windows firewall base on online docs from MS.
After 6 hours arround i didn't find any solution. Any ideas?
View 3 Replies
View Related
May 26, 2007
trying to connect to sql server 2005 over the internet. (its a third paty hosting company i'm using)
so i have to connect via tcp/ip using sql server authentication.
my laptop is running vista.
the version of sql server 2005 on my laptopis developer edition with service pack 2.
it worked fine from windows xp and the connection details are valid as it runa fine from .net on the hosting website.
i have added sql serer managemnt studio to the exceptions list in the firewall.
ihave made sure tcpip is enabled in the sql server connection management console.
i have also enabled it in the cliconfg tool
firewall on/off seems to make no difference.
its almost enough to make you turn to oracle and thats saying something considering how long i've been in the microsoft camp...
the error returned is:
Login failed for user 'SQL2005_152092_garethbowen'. (.Net SqlClient Data Provider)
------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476
------------------------------
Server Name: 'xxxx',1433
Error Number: 18456
Severity: 14
State: 1
Line Number: 65536
View 3 Replies
View Related
Oct 23, 2007
I'm setting up a simple SSRS implementation for a non-profit organization, using two servers hosted at a data center. The first server has SQL Server Standard Edition and Reporting Services installed. I've designed and deployed a number of useful reports on this server.
I was hoping to isolate this first server by installing IIS and SSRS on the second server, have users browse from the Internet to that second server (over SSL, of course), and have all reports served up from databases (and, presumably, the report server database) on the first server.
During the installation of SSRS on the second server, however, I'm being prompted to specify the service account. According to the help text:
"Reporting Services. Service accounts are used to configure a report server database connection. Choose a domain user account if you want to connect to a report server database on a remote SQL Server instance. If you are using a local report server database, you can use a domain user account or Local System to run the service."
I believe I want to configure SSRS to connect to a report server database on a remote SQL Server instance; therefore, it appears that I need to enter a domain user account. The only problem is, neither server belongs to a domain; they are members of a simple two-server workgroup.
Does SSRS, configured to connect to a report server database on a remote SQL Server instance, require a domain? Does what I'm hoping to accomplish require a domain? Creating a two-server domain seems like overkill for this implementation, doesn't it?
I appreciate any comments and suggestions. Thanks!
View 1 Replies
View Related
Oct 8, 2007
Hi,
Just upgraded some development desktops to Vista Business. However we need
to still connect to some older remote windows 2000/SQL 2000 servers.
Trying to setup an ODBC system DSN on our Vista Business local desktop we get the
following errors -
-START ERROR WINDOW-
Connection Failed:
SQLState: '01000'
SQL Server Error: 772
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(SECDoClientHandshake()0.
Connection failed:
SQLState: '08001'
SQL Server Error: 18
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SSL Security Error
-END ERROR WINDOW-
Any help greatly appreciated as this is stopping us from making
database/table connections etc. We've checked the firewall setup and all is well there.
PS - we can still connect fine using XP or windows 2000 desktops and their
local DSNs.
View 8 Replies
View Related
Sep 28, 2007
Hi,
We have the followoing:
-A "master domain" AD, a "sub domain" AD, a trust relationship between the two (sub trust master)
-A sql server 2005 on a win server 2003 in "sub domain" AD
-A linked server to "sub domain" AD
-A linked server login using a "sub domain" admin acccount
-A view to this linked server
-A grant on masterDomain/Domain Users to the database
-A grant on subDomain/Domain Users to the database
-We want all connections done through "Windows Authentication" not "Database Authentication".
Queries on the view work fine using "sub domain" user accounts.
Queries on the view fail using "master domain" user accounts (including master domain admin accounts)
"Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "ADsDSOObject" for linked server "ADSI" reported an error. The provider indicates that the user did not have the permission to perform the operation."
All connections are done through "Windows Authentication" not "Database Authentication".
Can we establish cross domain connectivity with "Windows Authentication" ?
Below are details of the implementation:
SELECT TOP (100) PERCENT *
FROM OPENQUERY(ADSI,
'SELECT displayname, givenName, sn, cn (etc...)
FROM ''LDAP://OU=PEOPLE,DC=subDomain,DC=com''
WHERE objectCategory = ''Person'' AND objectClass = ''user'' ')
EXEC sp_addlinkedsrvlogin @rmtsrvname ='ADSI', @useself='false',
@rmtuser='subDomainAdminAccnt', @rmtpassword='sunDomainAdminAccntPassword';
In SQL Server Mngt Studio in Server Objects/Linked Servers/Providers/ ADSI properties security tab I have:
"connections will: <be made using this security context> Remote login:'subDomainAdminAccnt' With password: 'subDomainAdminAccntPassword'
Error:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "ADsDSOObject" for linked server "ADSI" reported an error. The provider indicates that the user did not have the permission to perform the operation.
Msg 7320, Level 16, State 2, Line 1
Cannot execute the query "SELECT displayname, givenName, sn, cn
FROM 'LDAP://OU=PEOPLE,DC=subDomain,DC=com'
WHERE
objectCategory = 'Person'
AND objectClass = 'user'
" against OLE DB provider "ADsDSOObject" for linked server "ADSI".
View 7 Replies
View Related
Apr 5, 2007
I have a root domain and child domain.
After using ADMT to migrate the domain user or group into the root domain, when I use enterprise manager to try and change the permissions allocated to that domain user/group, i get the 'Error 15401 NT user or Group not found'.
This is a correct error as the user is now in the root domain, however sql (in sysxlogins) still thinks its in the child domain.
Is there a simpler way, other than collecting the users permissions, deleting the user from SQL then adding back in with the correct domainusername format, then adding the permissions back?
I tried renaming the 'name' in sysxlogins (not recommended) and while that worked, whenever I tried to add the migrated user to another database, the login name was missing and would not resolve.
I believe it is something to do with the SID not matching.
Any ideas on how to fix this ?
View 1 Replies
View Related
Jun 19, 2015
we recently migrated from our in-house domain to the Enterprise domain. Everything went smooth except for the fact that I can no longer accept my dBs using my SA or my domain admin account. There is only 1 account I can get into the management studio with but it has no admin privileges, so I can't make any  password changes or add accounts. I don't have a test environment so kind of hesitant to experiment with our production system.
View 6 Replies
View Related
Apr 27, 2006
Hi,
If I connect to
SQLServer Express via Windows Authentication it works
fine. But if I use SQL Server Authentication it doesn't work with a new
created user and
sa (with a new password) too. I turned mixed mode on, registry key
HKLMSoftwareMicrosoftMicrosoft Sql ServerMSSQL.1\MSSQLServerlogin
has the value 2 and all ports are set to 1433 but there is still
error 18452. Any suggestions?
View 7 Replies
View Related
Nov 6, 2006
Hello,
I hope that anyone can help me. I'm getting the following message, when I try to logon to a SQL SERVER 2000/2005 via Windows authentication.
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. Server: Msg 18452
The SQL Servers were working fine with Windows authentication for a year or so. But now every day a new server starts to get that Problem.
If I disable the TCP/IP Protokol in the SQL Server Networkkonfig. (and just leave Named Pipes) everything works fine again....
(Sometimes it helps to take the server out of the domain and back in again - but only for a couple of days/hours)
Does anybody got and idea?
View 3 Replies
View Related
Jul 23, 2001
The error is:
Connection failed:
SQL State '37000'
SQL Sever Error: 18452
[Microsoft][ODBC SQL Sever Driver][SQL Server]Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
I have verified in Enterprise Manager that the concerened login is using a Windows 2000 Authentication and has the correct grant access permissions set up for the default database. Also switching to SQL Server Authentication or disabling security are not the options available in this case.
How to resolve this please-any help is welcome.
thanks
Sanjeev
View 1 Replies
View Related
Feb 16, 2000
I keep getting this error when tring to log in to a SQL 7 db from a client application written in VB6.
The text reads:
Login failed for user 'rmuser'. Reason: Not associated with a trusted SQL Server connection.
I have the account setup in SQL security and I have the account listed in the database and I'm using named pipes on a common domain. I'm running out of options. The network is a mix of Novell and NT. Please help
View 1 Replies
View Related
Jun 24, 2007
Hi to all.
I'm trying to log in on local machine to my SQL Server 2005 (in Windows Server 2003) using a user not trused, like as 'sa' user, but I receive the error Login failed for user 'sa'. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452).
No problem to connect with trusted user (my logon user to operating system).
I set the auth mode to SQL Server & Windows but doesn't work.
What can I do?
Ciao.
View 3 Replies
View Related
Oct 21, 2005
We have 2 failover servers and one client in our test environment. We have all the three configured in mixed mode authentication(windows + sql server authentication). But when we are failing over from 1st server to 2nd one, we are getting the following error message,
View 3 Replies
View Related
Jul 18, 2007
Hi All,
I am facing a very strange problem in one of my SQL2000 instance.
Actually, In one of my 2000 instance 'A', I have linked another 2000 instance 'B' (server 'B' is running under windows authentication) and I am a member of a group (SQL_Group) and that group is listed in sysadmin of both 'A' and 'B' Instances. When I am trying to run a simple select query from server 'A' to linked server 'B'
i.e. select top 2 * from [<Server_Name> <Instance_ Name>].master. dbo.sysobjects
It is giving me an error.
Server: Msg 18452, Level 14, State 1, Line 1
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection.
But rest of the members of same group (SQL_Group) are able to execute this query. Can anyone please let me know why this issue is only for me even I am having the same permissions as others??
Any help will be highly appreciated. thanks a lot to all of you.
Rizwan...........
View 2 Replies
View Related
Nov 3, 2006
I'm using Sql Server Express on Windows xp Home Edition, I have created a user FAB in Sql server and then I have given it the rights as a server adminstrator. For creating a user I have followed the video tutorial from the web site of SQL Server Express.
But when I want to connect with SQL Server Express using Sql server authentication it gives me the following error:
Login failed for user 'FAB'. The user is not associated with a trusted SQL Server connection. (.Net SqlClient Data Provider)
Error Number 18452,
I have searched [ Sql Express Error 18452 ] from google and read many articals but I can't find any artical which can solve my problem.
Can anybody help me please?
Shahid Mahmood
View 1 Replies
View Related
Jun 1, 2007
Hi All,
There are two servers €˜A€™ and €˜B€™. At server €˜A€™, there is installed Window server at server €˜B€?, there is installed Window Server2000. And both servers have SQL SERVER 2000. I have created link server from A to B. I have to insert data into table of server €˜B€™ from server €˜A€™. When I used directly insert command like
Insert into [server name (B)]. [Database]. [Owner].[table name]
Select * from [server name (A)]. [Database]. [Owner].[table name]
The data is inserted successfully.
But when I created Jobscheduling , it is failed and show message :-
"Executed as user: HOerpserver. Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. [SQLSTATE 28000] (Error 18452). The step failed."
Try to find out solution for this problem.
Regards,
Nikhil Chaturvedi
View 3 Replies
View Related
Sep 6, 2007
Here's a real puzzler. I have a remote SQL Server running on a different domain than the one I am logged in to. From my own PC, logged in as myself, I can create an ODBC connection to this remote server (using integrated authentication) with no problem. When I log in to any other PC as myself, I get the "28000 (18452) Not associated with a trusted connection" error. This would therefore seem to be a PC-specific problem, but I can't see any difference between the PCs. All PC's are running the same version of MDAC.
Firewall is down, no proxy is involved, and I have given myself Administrative privelege on the PCs.
Can anyone explain this? Thanks in advance.
View 9 Replies
View Related
May 3, 2006
Using sql2005 on a Novell network...
When attempting to log into Mgt Studio using windows authentication I am getting the error: Error 18452 (not associated with a trusted sql server connection) .
I added my domainuserName in sql with no problems and added the account to the sysadmin server role. However, I noticed my credentials on my pc are not listed as domainuserName but rather ComputerNameUserName. I think this is what is causing the problem but I am not sure. Can anyone lend a hand?
I'd appreciate any help,
Thanks.
Scott
View 52 Replies
View Related
Jun 5, 2007
Mircrosoft recommends that you change the authenication from Windows Authenication to SQL and Windows Authenication. This will allow users to gain access to the SQL server.
View 1 Replies
View Related
Mar 9, 2006
Hello,
I have a problem that I hope anyone here can help me with. We have a new server with Windows Server 2003 installed as well as MS SQL Server 2005. Both of these are freshly installed with default options set. The server is configured to accept both windows certification and SQL server certification (mixed), and our company has a domain setup. This server will be used for internal development, so all of the necessary people have an administrator account on the domain, which is uploaded currently into SQL Server's Security > Users folder. When I am on the server itself, I can log in using my domain name with no problem, as well as sa. However, when I try to connect to the server remotely (by my machine down the hall) using Windows Authentication I cannot. The server has BUILTINAdministrators set up for users, as well as 'sa' and whatever other defaults were there.
I CAN connect using sa remotely on my machine, though, after I enabled the account. The error message I get when I try to log in through Windows Authentication is:
*********************************************
TITLE: Connect to Server
------------------------------
Cannot connect to LAF-SQL1.
------------------------------
ADDITIONAL INFORMATION:
Login failed for user '(null)'. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452)
*********************************************
No other options other than what I've mentioned are installed. The (null) is not present, but the error message shows up as two single quotes ''. I strongly suspect there is a security option set by default somewhere in WinServer or SQLServer that does not permit remote connections, but I do not know where.
Help would be greatly appreciated here.
-Matt
View 3 Replies
View Related
Oct 28, 2007
When I use sa to log into one of my database , it give me the following error: The user is not associated with a trusted conncections. error code: 18452, please tell me how to solve this problem.
I appreciate your help.
View 1 Replies
View Related
Nov 19, 2007
Hi Experts,
Can anyone help me to identify the problem? The situation of my problem is : My company network in clients side is running either Window XP Pro or Window Xp Home.The problem occur when i access from Window XP Home to Server (Window Server 2003) an error pop up Sql Express Error 18452. It is worked fine in WIndow XP Pro version.
Thanks for anyone provide me a solution.
View 15 Replies
View Related
Sep 26, 2006
I'm trying to run a test from my test environment which is a non-domain Windows 2000 server to access my domain 2003 with SQL2005. I have install 2005 tools to try to access the SQL server.
- I have try following the KB265808 - no success.
- Reading alot of blogs and it seems all are pointing to the same problem. "Remote access" but the settign is enabled.Error Message:
TITLE: Connect to Server
------------------------------
Cannot connect to ardsqldatawh.
------------------------------
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
Question: Could Windows 2003 security be blocking access? I'm using sa account to access.
Also, sa account does not seems to work for remote access. It is ok when accessing locally.
Any help would be appreciated.
949jc
View 1 Replies
View Related
Jul 20, 2005
Hi all,it happen to me a strange problem:i have a mdb file (in Access 2K) with SQL Server 2K linked tables whoruns on a workstation which is on a different domain that the SQLServer. It works.If i create a mdb file from a workstation which is a the domain of theSQL Server and then i run it a my non-domain workstation i have errormessage:Login failed for user '(null)'. Reason: Not associated with a trustedSQL Server connectionBut if i reattached my tables it works.If someone have an idea....PS: same ODBC on both machines
View 1 Replies
View Related
