Greetings

I know this is a bit of old chestnut as questions go but I have
experienced serious problems making a remote connection. I have
googled this issue to death and using all the configuration tools I
have:

Set the remote connection to permit both TCP/IP and named pipes
connection
Set the browser running and to automatic startup.
Made exceptions in the firewall both to the exe files (server and
browser)
Made exceptions in the firewall for all possible TCP and UDP ports.
Ensured that mixed login (SQL server and windows authentication) mode
is permitted.

I am using a client version of Studio Express and use the protocol: IP/
instance_name as per the server based version of this program which
connects without any problem.

I have scoured the microsoft site and carried out all the changes they
suggest.

If anyone has been this way and found a solution and can provide me
the answer I will buy them a Porche for Christmas (maybe).

Surely there's on small thing i am overlooking. The error I am getting
when connecting suggests that this is a connection issues:

An error has occurred while establishing a connection to the server.
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: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified)

Anyone out there please who cracked this problem. I have two spent
three days trying to correct it.

Cheers

Sorry - just to add, this is MS SQL server 2005 express.

"Granty" <grant@gbdavis.com> wrote in message
news:5cee4f66-0bce-402f-a718-6bb26e48492d@d1g2000hsg.googlegroups.com...
> Sorry - just to add, this is MS SQL server 2005 express.

Hi

If you can connect with the IP/Instance for the server name from a client,
but not with COMPUTER\Instance, then you have connected remotely. The issue
may be with the resolution of the COMPUTER name. If you changed the name of
the computer then you will need to drop the server name and re-create it
(EXEC sp_dropserver 'OldName'; EXEC sp_addserver 'NewName', LOCAL). If there
are DNS issues adding the name to the hosts file may be a temporary fix
until it can be corrected.

With SQLCMD and SSMS you can use the notation
tcp:<servername>[\<instancename>],<port> when specifying how you can
connect, therefore allow a connection with a specific protocol and port.

John

Hello Granty,

In this scenarios, you better configure your SQL Server intance to use a
static port instead of a dynamic port.

I've seen lots of people who experiened this kind of problems, they said
they performed every action but they didn't connect... It was mostly because
of using dynamic ports instead of static ports.

As SQL Server 2005 Express Edition is configured to be installed as a named
instance and as named instances of SQL Server is configured to use dynamic
ports by default, your SQL Server instance must be using a dynamic port.

So, I suggest you to go to Configuration Manager and change your port
settings accordingly. This will probably solve your problem.

--
Ekrem Önsoy



"Granty" <grant@gbdavis.com> wrote in message
news:5cee4f66-0bce-402f-a718-6bb26e48492d@d1g2000hsg.googlegroups.com...
> Sorry - just to add, this is MS SQL server 2005 express.