I will try to keep this as concise as possible. I am trying to set up a new
SQL Server 2005 Express server.

The OS is Windows XP Pro SP2. SQL Express is SP2.

I am able to connect to the instance locally through shared memory. I am
also able to connect to the instance locally with TCP by selecting browsing
and the network tab.

I have been able to connect through ODBC from one client desktop through MS
Access.

I am unable to establish a connection from any other client. They are all
on the same subnet. I have tried updating the driver to SQL Native Client
but still cannot connect. I receive the very long error message that
essentially states that it doesn't exist or I do not have permission to it.

I hope that this will be enough information for someone to make some
suggestions.

Thanks in advance for reading this post.

Bill

Perhaps these articles will help:

Configuration -Configure SQL Server 2005 to allow remote connections
http://support.microsoft.com/default...b;EN-US;914277

Configuration -Connect to SQL Express from "downlevel clients"
http://blogs.msdn.com/sqlexpress/arc...23/192044.aspx


--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous

You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf


"William Downey" <wdowney (AT) mclean (DOT) harvard.edu> wrote

Thanks for the article links.

Unfortunately, it seems I have tried nearly everything I can think of to get
clients to access the instance.

I did notice a previous thread that mentioned a similar issue.

The troubleshooting path I am headed down now is one of network-related
issues.

I wonder if anyone has had similar connectivity issues and had to tweak lan
settings?

Bill Downey
"Arnie Rowland" <arnie (AT) 1568 (DOT) com> wrote

You need to enable SQL Browser service (automatic), else the clients do
not know which dynamic TCP-port the should connect to. SQL Browser (UDP
1434) helps with this.

Default instance uses TCP 1433, which works without SQL Browser, but
all instances need SQL Browser.

In the SQL Area configuration guide, I think it should ask if you want
to start SQL Browser when you enable TCP-connections on an instance
other than default instance.

Best regards
Niklas Engfelt


William Downey skrev:

I dont know if it is the same situation but I am having a problem with native
clients also... Essentiallly I CAN NOT INSTALLED SQL Express 2005 because I
keep getting an error almost at the end of the installation that read like
this: "[Microsoft][SQL Native Client]SSL Provider: The certificate's CN name
does not match the passed value" I have no idea what to do. I am practically
new to this. I just wanted to install SQL to follow up with the Visual Studio
C# lessons I am taking. I am stuck in chapter 8 because I need to install SQL
in order to follow up with the lessons and I can not do it... HELP!!!! Can
someone out there tell me what I need to do to install this package? (SQL
Express 2005). I would appreciate if beside posting something that person
would email me at waltersantiago (AT) msn (DOT) com. I just found this group while
looking for answers to my problem and I am afraid I may not get to see the
responses, if any, to my plight... Again... I just want to be able to install
the product. The above mentioned error stop me every time... I cleaned up and
uninstalled both automatically (with the program the SQL people provide) and
manually (by following their instructions) everything they asked to be
uninstalled before trying an installation. I still get the error... What is
CN? and where is lookling for the certificate? Do I need to delete or create
a especial certificate in order to install this product? If yes then how?
Anyway any help would be greatly appreciated. I would like to keep my journey
into becoming a Visual Studio C# programmer. THanks

"William Downey" wrote:

I've been having similar issues with regards to connectiong to SQL Server
Express Edition. I've installed it at several locatoins with little to no
problems. But, at a current client site things are not working as they have
at other client sites, which has really frustrated me.

I've made a post in SQL Server Access ADP regarding my problem, but have
decided to search a little more for a solution. My SQL Express has SQL
Browser Started. Initally, my Access application was not able to list my
databases for my server, but after Starting my SQL Browser my application now
lists the databases on my Server, but does not allow my client to connect to
the database. This same client application is installed on the server and
loads just fine, so I kinow my logon credentials are all correct.

Your comments regarding Port 1433. Is this a port that is commonly blocked
by firewalls? If so, could this be causeing a problem with me connecting? I
have little knowledge of TCP/IP and Ports, so I do not know where to work on
this items.

I understand SQL Server and Development against it but am finding connecting
to it to be very frustrating as I'm at the point I have no clue as to what
trouble-shooting to do. Most posts I've ready make it sound like it should be
simple, but I'm still missing something.

So, In my situation, my application can "see" the Server as it lists all of
my current databases, but when I attempt to log on using SQL Authentication
it fails. I'm using Mixes Mode (Win/SQL). And, the SQL Login works fine on my
Server. What has me puzzled is that my application sees all my databases but
will no accept logon credentials that work on my Server at my Client PC.

I'm very frustated. Any suggestions on how I can do further troubleshooting.
This just seems way more complicated that Microsoft claimed when I switched
from Access to SQL Server.

Thanks, Greg

"engfelt (AT) gmail (DOT) com" wrote: