Showing posts with label greatly. Show all posts
Showing posts with label greatly. Show all posts

Sunday, February 12, 2012

Connection problem: ASP.NET on machine and SQL Server on another

If anyone knows the answer to this Id me greatly appreciative.
I am not on a domain.
I have SQL Server sitting on computer A
Computer A has:
Windows XP SP2
SQL Server 2000 SP3a
SQL Server is set to use Trusted or SQL authorization
I have added a user X to SQL Server with a password of X
I am writing an ASP.NET app on Computer B. IIS and Dev on B)
I am trying to make a connection to SQL on computer A but get the
error SQL Server does not exist or access denied
Now when I create a small Winforms app as a test, I can use the exact
same connection string and open a connection to SQL Server just fine.
So, Im guessing the problems lies in the security of ASP.NET, but Im
not sure what to change to make this work.
Anyone with any ideas?
TIA
B
I should also point out, I can also connect just fine withn the same
user/pw with Enterprise Mager, and Query Analyzer as well as add the
connection to Visual Studio.
B
Brian W wrote:

> If anyone knows the answer to this Id me greatly appreciative.
> I am not on a domain.
> I have SQL Server sitting on computer A
> Computer A has:
> Windows XP SP2
> SQL Server 2000 SP3a
> SQL Server is set to use Trusted or SQL authorization
> I have added a user X to SQL Server with a password of X
> I am writing an ASP.NET app on Computer B. IIS and Dev on B)
> I am trying to make a connection to SQL on computer A but get the
> error SQL Server does not exist or access denied
> Now when I create a small Winforms app as a test, I can use the exact
> same connection string and open a connection to SQL Server just fine.
> So, Im guessing the problems lies in the security of ASP.NET, but Im
> not sure what to change to make this work.
> Anyone with any ideas?
> TIA
> B

Connection problem: ASP.NET on machine and SQL Server on another

If anyone knows the answer to this Id me greatly appreciative.
I am not on a domain.
I have SQL Server sitting on computer A
Computer A has:
Windows XP SP2
SQL Server 2000 SP3a
SQL Server is set to use Trusted or SQL authorization
I have added a user X to SQL Server with a password of X
I am writing an ASP.NET app on Computer B. IIS and Dev on B)
I am trying to make a connection to SQL on computer A but get the
error SQL Server does not exist or access denied
Now when I create a small Winforms app as a test, I can use the exact
same connection string and open a connection to SQL Server just fine.
So, Im guessing the problems lies in the security of ASP.NET, but Im
not sure what to change to make this work.
Anyone with any ideas?
TIA
BI should also point out, I can also connect just fine withn the same
user/pw with Enterprise Mager, and Query Analyzer as well as add the
connection to Visual Studio.
B
Brian W wrote:

> If anyone knows the answer to this Id me greatly appreciative.
> I am not on a domain.
> I have SQL Server sitting on computer A
> Computer A has:
> Windows XP SP2
> SQL Server 2000 SP3a
> SQL Server is set to use Trusted or SQL authorization
> I have added a user X to SQL Server with a password of X
> I am writing an ASP.NET app on Computer B. IIS and Dev on B)
> I am trying to make a connection to SQL on computer A but get the
> error SQL Server does not exist or access denied
> Now when I create a small Winforms app as a test, I can use the exact
> same connection string and open a connection to SQL Server just fine.
> So, Im guessing the problems lies in the security of ASP.NET, but Im
> not sure what to change to make this work.
> Anyone with any ideas?
> TIA
> B

Friday, February 10, 2012

Connection problem from Vista

I can't connect from a Vista Client to a SQL 2005 Server.
I have been stuck on this problem over a week so any help would be greatly appreciated.

Overview:
I cannot connect from my client (vista business) except with SQL Server Management Studio.
I have tried Red Gate SQL Compare connection from a machine running XP and it connects ok.
I have tried connecting using ODBC from another machine running Vista Home and it connects ok.
I have no problem connecting to my local SQL Server (on my client).
I have tried using Windows Auth and a SQL login.

Environment:
Both the client and server are on the same domain and the user is a domain user.

Client:
Vista Business, SQL Server 2005 SP1 Client tools and Server, RedGate tools, Visual Studio 2005 SP1
Windows Firewall OFF

Norton virus protection OFF

UAC is turned OFF

Server:
SQL Server 2005 SP1, Remote connections allowed over TCP/IP Port 1433 (IPAll TCP Port 1433, not dynamic)
No windows firewall, Mcaffee virus running.


I get the errors below (or similar) connecting from:
SQL Profiler
Database engine tuning advisor,
Redgate SQL Compare (or any redgate software)
Setting up an ODBC connection
Visual Studio 2005 SP1

The only application that current connects is SQL Server Management Studio!?
If I apply SQL Server 2005 SP2 to the client it stops even SQL Server Management Studio from working.

I either get the following error:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake.
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:0 - No process is on the other end of the pipe.)

or (if I force the port and/or method e.g. TCP:192.168.130.3,1433)

A connection was successfully established with the server, but then an error occurred during the pre-login handshake.
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: TCP Provider, error:0 - No connection could be made because the target machine actively refused it.)

Again any help would be much appreciated as I just can not seem to solve this.

Thanks

Please check out following blog:

http://blogs.msdn.com/sql_protocols/archive/2007/06/18/connecting-to-sql-server-2005-on-vista-and-longhorn.aspx

Good Luck!

Ming.

Connection problem from Vista

I can't connect from a Vista Client to a SQL 2005 Server.
I have been stuck on this problem over a week so any help would be greatly appreciated.

Overview:
I cannot connect from my client (vista business) except with SQL Server Management Studio.
I have tried Red Gate SQL Compare connection from a machine running XP and it connects ok.
I have tried connecting using ODBC from another machine running Vista Home and it connects ok.
I have no problem connecting to my local SQL Server (on my client).
I have tried using Windows Auth and a SQL login.

Environment:
Both the client and server are on the same domain and the user is a domain user.

Client:
Vista Business, SQL Server 2005 SP1 Client tools and Server, RedGate tools, Visual Studio 2005 SP1
Windows Firewall OFF

Norton virus protection OFF

UAC is turned OFF

Server:
SQL Server 2005 SP1, Remote connections allowed over TCP/IP Port 1433 (IPAll TCP Port 1433, not dynamic)
No windows firewall, Mcaffee virus running.


I get the errors below (or similar) connecting from:
SQL Profiler
Database engine tuning advisor,
Redgate SQL Compare (or any redgate software)
Setting up an ODBC connection
Visual Studio 2005 SP1

The only application that current connects is SQL Server Management Studio!?
If I apply SQL Server 2005 SP2 to the client it stops even SQL Server Management Studio from working.

I either get the following error:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake.
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:0 - No process is on the other end of the pipe.)

or (if I force the port and/or method e.g. TCP:192.168.130.3,1433)

A connection was successfully established with the server, but then an error occurred during the pre-login handshake.
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: TCP Provider, error:0 - No connection could be made because the target machine actively refused it.)

Again any help would be much appreciated as I just can not seem to solve this.

Thanks

Please check out following blog:

http://blogs.msdn.com/sql_protocols/archive/2007/06/18/connecting-to-sql-server-2005-on-vista-and-longhorn.aspx

Good Luck!

Ming.