connecting to sql server (within windows domain) through linux?

Hi,

I'm planning to develop a small intranet to provide our organization
with documents online. I've decided to do this using jsp/servlets
using a tomcat server. For an operating system, I have chosen red hat
linux. However, I'd like to keep a small database on a sql server as
a datasource. However, this sql server is already part of our
organization's windows domain. I suspect I'll need to configure samba
so that other terminals on the windows domain will be able to reach
the intranet. What's the best manner in which to connect my linux
servlets to this sql server database? I suspect this may be
difficult, considering the sql server exists within a windows domain,
but as a beginner, what do I know. Perhaps someone could point me in
the right direction.Hi

You can use the JDBC driver to communicate with your SQL Server and use SQL
Server authentication to access the server. Samba is not needed at all this
may be a way to connect to an access database but SQL Server is a completely
different product.

John
"Dan" <danhicks333@.gmail.com> wrote in message
news:b03c5d2b.0409111105.18d75023@.posting.google.c om...
> Hi,
> I'm planning to develop a small intranet to provide our organization
> with documents online. I've decided to do this using jsp/servlets
> using a tomcat server. For an operating system, I have chosen red hat
> linux. However, I'd like to keep a small database on a sql server as
> a datasource. However, this sql server is already part of our
> organization's windows domain. I suspect I'll need to configure samba
> so that other terminals on the windows domain will be able to reach
> the intranet. What's the best manner in which to connect my linux
> servlets to this sql server database? I suspect this may be
> difficult, considering the sql server exists within a windows domain,
> but as a beginner, what do I know.Perhapssomeonecouldpointmein
> the right direction.|||Dan (danhicks333@.gmail.com) writes:
> I'm planning to develop a small intranet to provide our organization
> with documents online. I've decided to do this using jsp/servlets
> using a tomcat server. For an operating system, I have chosen red hat
> linux. However, I'd like to keep a small database on a sql server as
> a datasource. However, this sql server is already part of our
> organization's windows domain. I suspect I'll need to configure samba
> so that other terminals on the windows domain will be able to reach
> the intranet. What's the best manner in which to connect my linux
> servlets to this sql server database? I suspect this may be
> difficult, considering the sql server exists within a windows domain,
> but as a beginner, what do I know. Perhaps someone could point me in
> the right direction.

I have never connected to SQL Server from Unix myself, but I happen to
maintain a page which summarizes the various options. Look at:
http://www.sommarskog.se/mssqlperl/unix.html

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||The SQL server I want to connect to does not have a public IP address.
I connect to this server from my other web server (part of the
windows domain)using the server name (treadstonesql). My thinking was
that if samba is configured correctly, I could connect to it the same
way my web server does. Does this help?

"John Bell" <jbellnewsposts@.hotmail.com> wrote in message news:<414352bf$0$4664$afc38c87@.news.easynet.co.uk>...
> Hi
> You can use the JDBC driver to communicate with your SQL Server and use SQL
> Server authentication to access the server. Samba is not needed at all this
> may be a way to connect to an access database but SQL Server is a completely
> different product.
> John
> "Dan" <danhicks333@.gmail.com> wrote in message
> news:b03c5d2b.0409111105.18d75023@.posting.google.c om...
> > Hi,
> > I'm planning to develop a small intranet to provide our organization
> > with documents online. I've decided to do this using jsp/servlets
> > using a tomcat server. For an operating system, I have chosen red hat
> > linux. However, I'd like to keep a small database on a sql server as
> > a datasource. However, this sql server is already part of our
> > organization's windows domain. I suspect I'll need to configure samba
> > so that other terminals on the windows domain will be able to reach
> > the intranet. What's the best manner in which to connect my linux
> > servlets to this sql server database? I suspect this may be
> > difficult, considering the sql server exists within a windows domain,
> > but as a beginner, what do I know.Perhapssomeonecouldpointmein
> > the right direction.|||Hi

The IPaddress does not have to be a public one (in fact it would be better
if it wasn't) The IP Address can be used when connecting instead of using a
lookup, you will need to set up the firewall rules so that you can talk on
the right ports (not necessarily the default ones!) between the two
machines.

I would not expect your second web server to be part of the internal domain,
this may mean that your whole domain is compromised if the web server is
compromised.

John

"Dan" <danhicks333@.gmail.com> wrote in message
news:b03c5d2b.0409120659.618cc1ae@.posting.google.c om...
> The SQL server I want to connect to does not have a public IP address.
> I connect to this server from my other web server (part of the
> windows domain)using the server name (treadstonesql). My thinking was
> that if samba is configured correctly, I could connect to it the same
> way my web server does. Does this help?
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:<414352bf$0$4664$afc38c87@.news.easynet.co.uk>...
> > Hi
> > You can use the JDBC driver to communicate with your SQL Server and use
SQL
> > Server authentication to access the server. Samba is not needed at all
this
> > may be a way to connect to an access database but SQL Server is a
completely
> > different product.
> > John
> > "Dan" <danhicks333@.gmail.com> wrote in message
> > news:b03c5d2b.0409111105.18d75023@.posting.google.c om...
> > > Hi,
> > > > I'm planning to develop a small intranet to provide our organization
> > > with documents online. I've decided to do this using jsp/servlets
> > > using a tomcat server. For an operating system, I have chosen red hat
> > > linux. However, I'd like to keep a small database on a sql server as
> > > a datasource. However, this sql server is already part of our
> > > organization's windows domain. I suspect I'll need to configure samba
> > > so that other terminals on the windows domain will be able to reach
> > > the intranet. What's the best manner in which to connect my linux
> > > servlets to this sql server database? I suspect this may be
> > > difficult, considering the sql server exists within a windows domain,
> > > but as a beginner, what do I know.Perhapssomeonecouldpointmein
> > > the right direction.

Connecting Sql Server 2005 from ASP?

Hi
We are planning to move over to SQL Server 2005 in near future.

At the moment Website is on a seperate server then the Database.
OS for both the server is Window 2003 and currently our data is on SQL
Server 2000(on which everything works fine).

Part of the testing process we tried to connect our website on SQL 2005
and it does not work at all.

I get this

-
ADODB.Connection error '800a0e7a'
Provider cannot be found. It may not be properly installed.

When i use following connection string
"Provider=SQLNCLI;Server=127.0.0.1;Database=dbName;UID=UserName;PWD=UserPassword;"

(Above string has fixed problem for few people- googled it, but not for
me.)
-

-
This is the message i get for all the following connectiong string

Microsoft OLE DB Provider for SQL Server error '80004005'

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied.

1) - "Provider=SQLOLEDB.1;Password=UserPassword;Persist Security
Info=True;User ID=UserName;Initial Catalog=ABC;Data
Source=XXX.XX.X.XX,1433"

2) - "Provider=sqloledb;Data Source=XXX.XX.X.XX,1433;Network
Library=DBMSSOCN;Initial Catalog=ABC;User
ID=UserName;Password=UserPassword"

3) - "Provider=SQLOLEDB.1;Persist Security Info=True;User
ID=UserName;Initial Catalog=ABC;Data Source = ServerName\SQLInstance"

-

I tried connecting to SQL Server 2005 through our system developed in
VB.Net 2003 and it works fine and here is the Connection String :

"Data Source=ServerName\SQLInstance;Initial Catalog=ABC;Persist
Security Info=False;user id=UserName;password=UserPassword"

Then i downloaded SQL Native Client and installed on the web server.

I looked in SAC Tool and "Local and Remote Connection" and "Using Both
TCP/IP and Named Pipes" options are selected. I have checked SQL
Browser service is running.

Now when i use this string

"Provider=SQLNCLI;Server=127.0.0.1;Database=DBName;UID=UserName;PWD=UserPassword;"

i get

Microsoft SQL Native Client error '80040e4d'

Login failed for user 'UserName'.

I have created this user and this user has proper permission to access
the database i need.

I would really appreciate any help as this is driving me crazy.

Mits

ASP has not been supported for some time. However, if you're stuck with legacy ASP code, I would expect you'd be able to connect, as it just connects via COM, I thought.

However, web development questions are off topic here. www.asp.net is the place for ASP.NET questions, but as I said, there is no support for asp, and no Microsoft website that allows asp questions. I percieve that the question relates to connecting to SQL Server 2005, which is on topic here, so I'm not locking the thread or marking it as off topic ( which I'd usually do for ASP questions ), but certainly the odds of people here using ASP are very low, so I'd recommend finding a forum that actually supports ASP and asking there. If you're using ASP.NET, and that's what you meant to say, please ask at www.asp.net.

Good luck !!!

|||hi cgraus
Thanks for not locking the topic.

I have never come across anywhere, where its says i cant connect to SQL Server 2005 using ASP. If this is true then that means we can't move on to SQL Server 2005 as all our website still written in ASP and the database is SQL Server 2000.

Mits

|||

// If this is true then that means we can't move on to SQL Server 2005

Well, I guess the real question is, why do you want to ? I mean, your website is ( sorry ) written in a hopelessly out of date technology, so how will SS2005 help you anyhow ? It's not like you can write .NET code to run in it...

But, and this is my core point, I don't know if it's true or not. I've not worked on ASP sites for years, and the odds of me doing it again are zero. That's why you'd be better off finding a site that suports ASP, because it's very much legacy technology now, and unless you're talking to people who are using it, the odds of you getting an answer are pretty low.

|||I understand your point about ASP and getting the answer or solution in this forum.
I will really appreciate if you can give me any link to Microsoft's website where it says that any website written in ASP won't be supported by SS2005.

Mits

|||What i am asking here or atleast tyring to get the answer is;

As it is possible to connect to SQL 2000 using ASP code, Is it still possible to do with SQL Server 2005?

Mits

|||

I don't know, and that's the core point I'm trying to make. If I had a link, I'd have answered your question, but the fact is that it's unlikely that anyone here uses asp, and so it's unlikely that anyone here can help you.

It's unfortunate that it's very hard to google for asp and not asp.net info. -net actually doesn't work, I've discovered.

You didn't answer my question tho - why do you need SQL Server 2005 ? What does it offer to make it worth the cost and the hassle ? I assume you have a huge site, to not be updating it to ASP.NET, but without .NET, what does SQL Server 2005 offer that's so important ?

|||Its a management decision and i am asked to evaluate SS2005 in our business environment.
Based on my findings management will take decision when to migrate over SS2005. Our website are E-Commerce sites and because of lack of resources the tranisition process from ASP to ASP.Net is slow.

I know this is not the place but in line of this discussion, as a MVP what factors would you consider if you want to migrate to SS2005. (Sorry i was just asking cgraus but if anyone wants to throw any ideas then they are more then welcome to do so.)

Mits

|||moved this post to SQL Server getting started.|||

My core criteria with any upgrade is 'what does it give me'. For example, I have projects written in VC6. I don't like VC6, not one bit. But, I don't upgrade my projects to VC2005, or even VC2002, unless I can see a compelling reason to. ANY upgrade to a new product is in essence a move to a new programming language. I would be surprised in T-SQL 2005 changes anything that would stop T-SQL 2000 code from working, but it's still an identifiable risk that I would not take unless there were actual SS205 features that I needed. SQL Server is also not cheap. It's not money I would spend if my SS2000 database was performing just fine, and all I intended to do was run the exact same database on a new engine. The exciting new stuff in SS2005 relate to managed code, and unless you're moving to ASP.NET and intend to use those features ( for good reason, not just to say you did ), I wouldn't bother thinking about moving.

|||hi

Good News guys got it all working.
I really appreciate all the effort and time put in by cgraus .

These are the steps i did, and i dont it might help anyone out there.

Our Webserver is outside DMZ on our network. It can only communicate
through secured channels on our linux firewall. I have got a named
Instance of SQL Server 2005(Enterprise Edition)

1) I punched a hole through our firewall that will allow communication
between our Webserver and DB server through specific Port.
2) I Installed SQL Native Client on Webserver.
3) In SSCM(SQL Server Configuration Manager) Tool
On Console Pane, Click Protocols for <Instance Name>
Double Click TCP/IP
Listen To All > No

For IP1
Active = Yes
Enabled = Yes
IP Address = IP of the DB Server
TCP = Blank/Nothing
TCP Port = 1433( or any port number but it has to be the same that
you have defined in firewall)

Save Everything and Re-start the SQL Server (Instance Name) Service.

This is the example of connection string that worked

Provider=SQLNCLI.1;Persist Security Info=False;User
ID=UserNamer;Password=UserPassword;Initial Catalog=NameofDatabase;Data
Source=DBServerName

Mits

Connecting Sql Server 2005 from ASP?

Hi
We are planning to move over to SQL Server 2005 in near future.

At the moment Website is on a seperate server then the Database.
OS for both the server is Window 2003 and currently our data is on SQL
Server 2000(on which everything works fine).

Part of the testing process we tried to connect our website on SQL 2005
and it does not work at all.

I get this

--------------------
ADODB.Connection error '800a0e7a'
Provider cannot be found. It may not be properly installed.

When i use following connection string
"Provider=SQLNCLI;Server=127.0.0.1;Database=dbName; UID=UserName;PWD=UserPassword;"

(Above string has fixed problem for few people- googled it, but not for
me.)
--------------------

--------------------
This is the message i get for all the following connectiong string

Microsoft OLE DB Provider for SQL Server error '80004005'

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied.

1) - "Provider=SQLOLEDB.1;Password=UserPassword;Persist Security
Info=True;User ID=UserName;Initial Catalog=ABC;Data
Source=XXX.XX.X.XX,1433"

2) - "Provider=sqloledb;Data Source=XXX.XX.X.XX,1433;Network
Library=DBMSSOCN;Initial Catalog=ABC;User
ID=UserName;Password=UserPassword"

3) - "Provider=SQLOLEDB.1;Persist Security Info=True;User
ID=UserName;Initial Catalog=ABC;Data Source = ServerName\SQLInstance"

--------------------

I tried connecting to SQL Server 2005 through our system developed in
VB.Net 2003 and it works fine and here is the Connection String :

"Data Source=ServerName\SQLInstance;Initial Catalog=ABC;Persist
Security Info=False;user id=UserName;password=UserPassword"

I would really appreciate any help.

Mits(MVChauhan@.googlemail.com) writes:
> We are planning to move over to SQL Server 2005 in near future.
> At the moment Website is on a seperate server then the Database.
> OS for both the server is Window 2003 and currently our data is on SQL
> Server 2000(on which everything works fine).
>
> Part of the testing process we tried to connect our website on SQL 2005
> and it does not work at all.
> I get this
> --------------------
> ADODB.Connection error '800a0e7a'
> Provider cannot be found. It may not be properly installed.
> When i use following connection string
> "Provider=SQLNCLI;Server=127.0.0.1;

Did you install SQL Native Client on the web server? SQL Native Client
is a DLL that contains versions of both the ODBC SQL Server Driver
and the SQL Server OLE DB Provider that has been enhanced with support
for SQL 2005.

SQL Native Client is freely distributable.

> This is the message i get for all the following connectiong string
> Microsoft OLE DB Provider for SQL Server error '80004005'
> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
> access denied.

Note that by default some editions of SQL 2005 by default only permits
local connections. You can modify this in the Surface Area Configuration
Tool.

You may also have to encure that the SQL Browser service is running.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Hi Erland
Thanks for your reply.
I still cant conntect to SQL Server.

I downloaded SQL Native Client and installed on the web server.

I looked in SAC Tool and "Local and Remote Connection" and "Using Both
TCP/IP and Named Pipes" options are selected. I have checked SQL
Browser service is running.

Now when i use this string

"Provider=SQLNCLI;Server=127.0.0.1;Database=DBName; UID=UserName;PWD=UserPassword;"

i get

Microsoft SQL Native Client error '80040e4d'

Login failed for user 'UserName'.

I have created this user and this user has proper permission to access
the database i need.
Is there any special permissions that need? This is driving me crazy.

Mits

You may also have to encure that the SQL Browser service is running.

Erland Sommarskog wrote:

> (MVChauhan@.googlemail.com) writes:
> > We are planning to move over to SQL Server 2005 in near future.
> > At the moment Website is on a seperate server then the Database.
> > OS for both the server is Window 2003 and currently our data is on SQL
> > Server 2000(on which everything works fine).
> > Part of the testing process we tried to connect our website on SQL 2005
> > and it does not work at all.
> > I get this
> > --------------------
> > ADODB.Connection error '800a0e7a'
> > Provider cannot be found. It may not be properly installed.
> > When i use following connection string
> > "Provider=SQLNCLI;Server=127.0.0.1;
> Did you install SQL Native Client on the web server? SQL Native Client
> is a DLL that contains versions of both the ODBC SQL Server Driver
> and the SQL Server OLE DB Provider that has been enhanced with support
> for SQL 2005.
> SQL Native Client is freely distributable.
> > This is the message i get for all the following connectiong string
> > Microsoft OLE DB Provider for SQL Server error '80004005'
> > [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
> > access denied.
> Note that by default some editions of SQL 2005 by default only permits
> local connections. You can modify this in the Surface Area Configuration
> Tool.
> You may also have to encure that the SQL Browser service is running.
>
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx|||The SQL 2005 password is case sensitive while 2000 wasn't, so code that
works on SQL 2000 for logging in may not work on 2005.

MVChauhan@.googlemail.com wrote:
> Hi Erland
> Thanks for your reply.
> I still cant conntect to SQL Server.
> I downloaded SQL Native Client and installed on the web server.
> I looked in SAC Tool and "Local and Remote Connection" and "Using Both
> TCP/IP and Named Pipes" options are selected. I have checked SQL
> Browser service is running.
> Now when i use this string
> "Provider=SQLNCLI;Server=127.0.0.1;Database=DBName; UID=UserName;PWD=UserPassword;"
> i get
> Microsoft SQL Native Client error '80040e4d'
> Login failed for user 'UserName'.
> I have created this user and this user has proper permission to access
> the database i need.
> Is there any special permissions that need? This is driving me crazy.
>
> Mits
>
>
>
> You may also have to encure that the SQL Browser service is running.
> Erland Sommarskog wrote:
> > (MVChauhan@.googlemail.com) writes:
> > > We are planning to move over to SQL Server 2005 in near future.
> > > > At the moment Website is on a seperate server then the Database.
> > > OS for both the server is Window 2003 and currently our data is on SQL
> > > Server 2000(on which everything works fine).
> > > > > Part of the testing process we tried to connect our website on SQL 2005
> > > and it does not work at all.
> > > > I get this
> > > > --------------------
> > > ADODB.Connection error '800a0e7a'
> > > Provider cannot be found. It may not be properly installed.
> > > > When i use following connection string
> > > "Provider=SQLNCLI;Server=127.0.0.1;
> > Did you install SQL Native Client on the web server? SQL Native Client
> > is a DLL that contains versions of both the ODBC SQL Server Driver
> > and the SQL Server OLE DB Provider that has been enhanced with support
> > for SQL 2005.
> > SQL Native Client is freely distributable.
> > > This is the message i get for all the following connectiong string
> > > > Microsoft OLE DB Provider for SQL Server error '80004005'
> > > > [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
> > > access denied.
> > Note that by default some editions of SQL 2005 by default only permits
> > local connections. You can modify this in the Surface Area Configuration
> > Tool.
> > You may also have to encure that the SQL Browser service is running.
> > --
> > Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> > Books Online for SQL Server 2005 at
> > http://www.microsoft.com/technet/pr...oads/books.mspx
> > Books Online for SQL Server 2000 at
> > http://www.microsoft.com/sql/prodin...ions/books.mspx|||I know there is no issue with Password.
I just realised one thing i dont know if it matters..
Between our webserver there is a firewall, do we need to punch a hole
that will allow communication between our webserver and DB Server.

Mits

pb648174 wrote:

> The SQL 2005 password is case sensitive while 2000 wasn't, so code that
> works on SQL 2000 for logging in may not work on 2005.
> MVChauhan@.googlemail.com wrote:
> > Hi Erland
> > Thanks for your reply.
> > I still cant conntect to SQL Server.
> > I downloaded SQL Native Client and installed on the web server.
> > I looked in SAC Tool and "Local and Remote Connection" and "Using Both
> > TCP/IP and Named Pipes" options are selected. I have checked SQL
> > Browser service is running.
> > Now when i use this string
> > "Provider=SQLNCLI;Server=127.0.0.1;Database=DBName; UID=UserName;PWD=UserPassword;"
> > i get
> > Microsoft SQL Native Client error '80040e4d'
> > Login failed for user 'UserName'.
> > I have created this user and this user has proper permission to access
> > the database i need.
> > Is there any special permissions that need? This is driving me crazy.
> > Mits
> > You may also have to encure that the SQL Browser service is running.
> > Erland Sommarskog wrote:
> > > (MVChauhan@.googlemail.com) writes:
> > > > We are planning to move over to SQL Server 2005 in near future.
> > > > > > At the moment Website is on a seperate server then the Database.
> > > > OS for both the server is Window 2003 and currently our data is on SQL
> > > > Server 2000(on which everything works fine).
> > > > > > > > Part of the testing process we tried to connect our website on SQL 2005
> > > > and it does not work at all.
> > > > > > I get this
> > > > > > --------------------
> > > > ADODB.Connection error '800a0e7a'
> > > > Provider cannot be found. It may not be properly installed.
> > > > > > When i use following connection string
> > > > "Provider=SQLNCLI;Server=127.0.0.1;
> > > > Did you install SQL Native Client on the web server? SQL Native Client
> > > is a DLL that contains versions of both the ODBC SQL Server Driver
> > > and the SQL Server OLE DB Provider that has been enhanced with support
> > > for SQL 2005.
> > > > SQL Native Client is freely distributable.
> > > > > This is the message i get for all the following connectiong string
> > > > > > Microsoft OLE DB Provider for SQL Server error '80004005'
> > > > > > [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
> > > > access denied.
> > > > Note that by default some editions of SQL 2005 by default only permits
> > > local connections. You can modify this in the Surface Area Configuration
> > > Tool.
> > > > You may also have to encure that the SQL Browser service is running.
> > > > > > > --
> > > Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> > > > Books Online for SQL Server 2005 at
> > > http://www.microsoft.com/technet/pr...oads/books.mspx
> > > Books Online for SQL Server 2000 at
> > > http://www.microsoft.com/sql/prodin...ions/books.mspx|||MVChauhan@.googlemail.com (MVChauhan@.googlemail.com) writes:
> Thanks for your reply.
> I still cant conntect to SQL Server.
> I downloaded SQL Native Client and installed on the web server.
> I looked in SAC Tool and "Local and Remote Connection" and "Using Both
> TCP/IP and Named Pipes" options are selected. I have checked SQL
> Browser service is running.
> Now when i use this string
>
"Provider=SQLNCLI;Server=127.0.0.1;Database=DBName; UID=UserName;PWD=UserPass
word;"
> i get
> Microsoft SQL Native Client error '80040e4d'
> Login failed for user 'UserName'.

This is strange, because as I understood your original post, you were
connecting from a web server that was a on different machine from where
SQL Server is running.

However, in your connection string you have specified 127.0.0.1 which is
always the local machine. Still, you do make contact with an SQL Server
instance since you get that message.

Since I don't see your configuration, I'm left to guessworks, but there
are two obvious possibilities:
1) You have the username/password wrong.
2) You have an of SQL Server on the web server as well, but that's
not the one you intend to connect to.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||hi Erland

I am sorry if i confued you, you are right WebServer and DB Server are
2 different machines. I have replaced 127.0.0.1 with the IP of DB
server and now the error is

TCP Provider: An existing connection was forcibly closed by the remote
host.

Configuration of Servers are as follows

Webserver
OS Windows 2003

Database Server
OS Windows 2003
DB SQL Server 2005 with Service Pack1

Mits

Erland Sommarskog wrote:

> MVChauhan@.googlemail.com (MVChauhan@.googlemail.com) writes:
> > Thanks for your reply.
> > I still cant conntect to SQL Server.
> > I downloaded SQL Native Client and installed on the web server.
> > I looked in SAC Tool and "Local and Remote Connection" and "Using Both
> > TCP/IP and Named Pipes" options are selected. I have checked SQL
> > Browser service is running.
> > Now when i use this string
> "Provider=SQLNCLI;Server=127.0.0.1;Database=DBName; UID=UserName;PWD=UserPass
> word;"
> > i get
> > Microsoft SQL Native Client error '80040e4d'
> > Login failed for user 'UserName'.
> This is strange, because as I understood your original post, you were
> connecting from a web server that was a on different machine from where
> SQL Server is running.
> However, in your connection string you have specified 127.0.0.1 which is
> always the local machine. Still, you do make contact with an SQL Server
> instance since you get that message.
> Since I don't see your configuration, I'm left to guessworks, but there
> are two obvious possibilities:
> 1) You have the username/password wrong.
> 2) You have an of SQL Server on the web server as well, but that's
> not the one you intend to connect to.
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx|||MVChauhan@.googlemail.com (MVChauhan@.googlemail.com) writes:
> I am sorry if i confued you, you are right WebServer and DB Server are
> 2 different machines. I have replaced 127.0.0.1 with the IP of DB
> server and now the error is
> TCP Provider: An existing connection was forcibly closed by the remote
> host.
> Configuration of Servers are as follows
> Webserver
> OS Windows 2003
> Database Server
> OS Windows 2003
> DB SQL Server 2005 with Service Pack1

Have you configured SQL 2005 to accept remote connections? The Developer
and Express Editions of SQL 2005 accepts by default local connection only.

Use the Surface Area Configuration tool to check and change this.

Also make sure that the SQL Server Browser service is running.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||In SAC I have enabled Local and Remote Connection and also SQL Browser
service is running and is also Active.

Mits

Erland Sommarskog wrote:

> MVChauhan@.googlemail.com (MVChauhan@.googlemail.com) writes:
> > I am sorry if i confued you, you are right WebServer and DB Server are
> > 2 different machines. I have replaced 127.0.0.1 with the IP of DB
> > server and now the error is
> > TCP Provider: An existing connection was forcibly closed by the remote
> > host.
> > Configuration of Servers are as follows
> > Webserver
> > OS Windows 2003
> > Database Server
> > OS Windows 2003
> > DB SQL Server 2005 with Service Pack1
>
> Have you configured SQL 2005 to accept remote connections? The Developer
> and Express Editions of SQL 2005 accepts by default local connection only.
> Use the Surface Area Configuration tool to check and change this.
> Also make sure that the SQL Server Browser service is running.
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx|||MVChauhan@.googlemail.com (MVChauhan@.googlemail.com) writes:
> In SAC I have enabled Local and Remote Connection and also SQL Browser
> service is running and is also Active.

And you did restart SQL Server after enabling remote connections?

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Good News guys got it all working.
I really appreciate all the effort and time put in by Erland .

These are the steps i did, and i dont it might help anyone out there.

Our Webserver is outside DMZ on our network. It can only communicate
through secured channels on our linux firewall. I have got a named
Instance of SQL Server 2005(Enterprise Edition)

1) I punched a hole through our firewall that will allow communication
between our Webserver and DB server through specific Port.
2) I Installed SQL Native Client on Webserver.
3) In SSCM(SQL Server Configuration Manager) Tool
On Console Pane, Click Protocols for <Instance Name>
Double Click TCP/IP
Listen To All --> No

For IP1
Active = Yes
Enabled = Yes
IP Address = IP of the DB Server
TCP = Blank/Nothing
TCP Port = 1433( or any port number but it has to be the same that
you have defined in firewall)

Save Everything and Re-start the SQL Server (Instance Name) Service.

This is the example of connection string that worked

Provider=SQLNCLI.1;Persist Security Info=False;User
ID=UserNamer;Password=UserPassword;Initial Catalog=NameofDatabase;Data
Source=DBServerName

Mits

Erland Sommarskog wrote:

> MVChauhan@.googlemail.com (MVChauhan@.googlemail.com) writes:
> > In SAC I have enabled Local and Remote Connection and also SQL Browser
> > service is running and is also Active.
> And you did restart SQL Server after enabling remote connections?
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx

Connect to SQL2000 & SQL 2005

Our current program use ADO to connect oto SQL2000 and run fine.
We are planning to migrate to SQL2005.
When we clean install the SQL2005, create the database, set compatibility
level to 80 and generate the db structure, and migrate data.
When everything is done, we try to use our program to connect to SQL2005
database and find the connection fail.
Even when we use sa as login user and still fail to connect.
Is there any different in connection for SQL2000 & SQL2005?
I remember I have tried upgrade SQL2000 to SQL2005 before and the connection
had no problem to sql2005.
Is there something I forgot to set?
KanAm Tue, 29 Aug 2006 17:38:51 +0800 schrieb Ivan:

> Our current program use ADO to connect oto SQL2000 and run fine.
> We are planning to migrate to SQL2005.
> When we clean install the SQL2005, create the database, set compatibility
> level to 80 and generate the db structure, and migrate data.
> When everything is done, we try to use our program to connect to SQL2005
> database and find the connection fail.
> Even when we use sa as login user and still fail to connect.
> Is there any different in connection for SQL2000 & SQL2005?
> I remember I have tried upgrade SQL2000 to SQL2005 before and the connecti
on
> had no problem to sql2005.
> Is there something I forgot to set?
> Kan
If you did a standard installation then SQL2005 uses the named instance
SQLExpress wich you have to use in your connect string.
If your SQL2005 runs on the same machine as your SQL2000 then maybe SQL2005
listen on another port than the standard port.
And have you allowed remote access in SQL2005?
bye, Helmut|||No, MDAC will work fine with the SQL Server 2005 instance. Although you
can=B4t use some of the new cool features its compatible. Which error do
you get ? Is the SQL Server 2k5 located on the same machine as the 2k
instance ?
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--

connect to SQL Server Express remotly

Hi,

I'm planning to develop asoftware working over SQL Server Express Edition, And I was wondering how would different users connect to sql server xe remotly from their machines? and is there a limitation to the number of users who could connect at same time? Is there a client app to installed on their machines, or its just the main db on the server?

Note: all users should be connected using LAN

thanks in advance

hi,

SQLExpress grant you the ability to connect from remote clients as long as you enable network protocols..

remote clients will connect to the desired server as specified in the connection string, where you can pass the "SERVER=ServerInstanceName;" setting (see some connection string samples at http://www.connectionstrings.com/)..

there's no built in limit in the number of concurrent users but 32767, the overall limit of SQL Server... obviously this only is a theoretical limit, as each connection consumes resources on the server, and SQLExpress only allow you to address up to 1gb of ram and only 1 physical processor... depending on the actual database design, data load, access method, concurrency on data and the like, you'll get out of resources with very fewer users... it has been usualy sayd you can serve up to 25 concurrent users with MSDE, the predecessor of SQLExpress (which has a physical limitation, a "Governor Workload" that kicks in when 8 specified batches are running simultaneusly, slowing down all workloads)... SQLExpress does not present the same "scaling-down" technology, but this kind of magic number, based on detached database access (default with Ado.Net, but not with the older ADO data access model), with short queries and transactions can probably be still correct.. perhaps something more then this is eventually possible as well... anyway, remember to spare on resources :D

remote clients only need to install database connectivity binaries... MDAC if you use ADO/Ado.Net using the the OLE DB provider (which now is usually installed and upgraded by Windows Update as well), the SQL Native Client in current develop mode, as everyone is passing to this provider, which offers lots of new interesting features...

regards

|||

In Addition to the above post...

Have a look at the following article that will show you how to enable the remote connections to the Database Engine.