Re: Problems With Client Connections

Tech-Archive recommends: Fix windows errors by optimizing your registry

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@xxxxxxxxx" 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:

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@xxxxxxxx> wrote in message
news:%237eThA%23FHHA.4652@xxxxxxxxxxxxxxxxxxxxxxx
Perhaps these articles will help:

Configuration -Configure SQL Server 2005 to allow remote connections
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277

Configuration -Connect to SQL Express from "downlevel clients"
http://blogs.msdn.com/sqlexpress/archive/2004/07/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@xxxxxxxxxxxxxxxxxx> wrote in message
news:%23emSqz9FHHA.4588@xxxxxxxxxxxxxxxxxxxxxxx
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





.

Relevant Pages

  • Re: DataSet.GetChanges() in RowChanged(DataRowAction.Add)
    ... have you considered SQL Express and use ... > I realize now that I didn't describe well how the client application is ... > Framework installed on the client machine, but not any SQL Server). ... > 20 tables in different relations with eachother in the database, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: SBS 2003 and Sql Server ~ Client Install
    ... I've found the client tools and have now successfully installed them. ... Access front end to a SQL database, Excel can be a front end, A word mail merge document could access a SQL database via ODBC. ... We are trying to install the client software. ... We understand that a Northwind training database is available for SQL Server. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: SBS 2003 and Sql Server ~ Client Install
    ... I've found the client tools and have now ... A word mail merge document could access a SQL database via ... We want to install to gain an understanding. ... Once we've managed to install the SQL Server Client we can start to ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: TDS vs. TCP
    ... I start capturing the network traffic between SQL ... Server and the client. ... I don't see any TDS packets but the communication between SQL ... stand-a-lone server and the client, ...
    (microsoft.public.sqlserver.clustering)
  • Re: DMX Query response time
    ... the prediction is done in client-side. ... In SQL 2005, all predictions are performed in the server. ... >>>> server are remoted to the client and cached into client memory until ...
    (microsoft.public.sqlserver.datamining)