Hi all,

I'm having some trouble with connecting to SQL server instance lately
without adding a port number. I used to be able to always connect to
instance without having to input SQLSERVER,portnumber. However now
this is not the case. I doing this through an ADO connection object,
and creating the connection string. Does anyone know if there was a
recent Microsoft update or patch that would've cause this to stop
allowing me to connect to a SQL instance without having to put in the
port information? Thanks.

Flash08 (stuart.karp@gmail.com) writes:
> I'm having some trouble with connecting to SQL server instance lately
> without adding a port number. I used to be able to always connect to
> instance without having to input SQLSERVER,portnumber. However now
> this is not the case. I doing this through an ADO connection object,
> and creating the connection string. Does anyone know if there was a
> recent Microsoft update or patch that would've cause this to stop
> allowing me to connect to a SQL instance without having to put in the
> port information? Thanks.

More likely this is a change in your environment. You don't say which
version of SQL Server you are using, but with SQL 2005 I think the
requirement is that the Browser service is running. On SQL 2000, you
need to be able to access port 1434 on UDP.

In both cases, firewalls may get in the way.


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

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Erland Sommarskog <esquel@sommarskog.se> wrote in
news:Xns996556346440Yazorman@127.0.0.1:

> Flash08 (stuart.karp@gmail.com) writes:
>> I'm having some trouble with connecting to SQL server instance lately
>> without adding a port number. I used to be able to always connect to
>> instance without having to input SQLSERVER,portnumber. However now
>> this is not the case. I doing this through an ADO connection object,
>> and creating the connection string. Does anyone know if there was a
>> recent Microsoft update or patch that would've cause this to stop
>> allowing me to connect to a SQL instance without having to put in the
>> port information? Thanks.
>
> More likely this is a change in your environment. You don't say which
> version of SQL Server you are using, but with SQL 2005 I think the
> requirement is that the Browser service is running. On SQL 2000, you
> need to be able to access port 1434 on UDP.
>
> In both cases, firewalls may get in the way.
>
>

Is there a reason you can't connect using Server\Instance type syntax?