I have a C# .net app that connects remotely to a SQL Server 2005 database on
a Windows 2003 server machine sitting in Chicago. It connects through a
VPN. Everything works fine when I run the app from a machine running XP Pro
SP 2. When I try to run the same app, no modifications, from a Vista
Business machine and from a Vista Ultimate machine, (so I am assuming it's a
Vista issue) I get the error

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

It is not the SQL Server, because it works from the XP machine.
It is not TCP/IP on the Vista machines because I can do everything else,
connnect to internet, connect through VPN etc.

As it is happening on more than one machine running Vista and not the XP,
that is why I am assuming it is a Vista Problem.

I can connect to the SQL Server on the Chicago machine by using SQL Server
Management Studio Express.

That seems to narrow it down to a ado.net issue.

I am using the .net 3.5 framework.

Any suggestions?

BillG

I solved the problem. When connecting from a Vista machine change the
configuration string to use the ip address, port number of the SQL Server
machine instead of the name of the SQL Server machine.

Bill

"BillG" <(E-Mail Removed)> wrote in message
news:E949F8C6-40B4-4359-B1A5-(E-Mail Removed)...
>I have a C# .net app that connects remotely to a SQL Server 2005 database
>on a Windows 2003 server machine sitting in Chicago. It connects through a
>VPN. Everything works fine when I run the app from a machine running XP
>Pro SP 2. When I try to run the same app, no modifications, from a Vista
>Business machine and from a Vista Ultimate machine, (so I am assuming it's
>a Vista issue) I get the error
>
> [DBNETLIB] ConnectionOpen (Connect()).] SQL Server does not exist or
> assess denied.
>
> It is not the SQL Server, because it works from the XP machine.
> It is not TCP/IP on the Vista machines because I can do everything else,
> connnect to internet, connect through VPN etc.
>
> As it is happening on more than one machine running Vista and not the XP,
> that is why I am assuming it is a Vista Problem.
>
> I can connect to the SQL Server on the Chicago machine by using SQL Server
> Management Studio Express.
>
> That seems to narrow it down to a ado.net issue.
>
> I am using the .net 3.5 framework.
>
> Any suggestions?
>
> BillG
>