Showing posts with label systems. Show all posts
Showing posts with label systems. Show all posts

Friday, February 24, 2012

Client unable to establish connection Encryption not supported on SQL Server. (Microsoft SQL Nat

On Windows XP systems I get the following issue when trying to browse the MSDB folder in SSIS

Client unable to establish connection
Encryption not supported on SQL Server. (Microsoft SQL Native Client)

I have noticed another post where several others have noticed the same issue. It appears to only occur on Windows XP installations. Is there a workaround or fix for this?

Is the SQL 2005 instance the default or named instance? If it is named instance you need to edit SSIS service configuration file to point to appropriate instance. The process is described in SQL Books Online.|||It is the default instance.

Tuesday, February 14, 2012

client connection prblm

i hav just startd working with sql server 2000, i hav two systems, in 1 system i have installed server tools n other i installed client tools, now the prblm when i registrd a server frm client, it detect the server but then unable to connect with server the prblm it gives is invalid login

sever\guest

although i have login wid administrator from both system

plz any1 there to solve my prblm

thanks in advance

You are connecting using Windows credentials. That means you have to be logged in with Windows credentials that are valid on your SQL Server. If you simply logged in under the local administrator account, you will not be able to connect to the remote instance, because the SID of the local administrator account is not valid on any other machine.|||

thanx for reply

but i still doesnt got ur point if u can explain ur answer a bit

|||Local Administrator means that you are an administrator on the single machine that you are logging into. If you are physically logging into the machine with the built in account of Administrator, that means your Windows account is for that machine, only that machine, and no other machine in your entire network will understand what that account is nor will it allow you to access any other resource outside of the machine that you are logged into. If you are going to connect to a SQL Server on a different machine, using Windows credentials, then you MUST be logging into a machine using a domain account that has been granted access to the SQL Server.|||Also for informaton refer to KBA http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q328306 in this case.