Re: unable to connect to sql server remotely

Because that is the only way by default that the clients can know what port to talk to. Since each named instance will get a random port number the browser service returns that to the client when they ask by instance name. To get around that you can fix the port number and hard code that into the connection string.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Matt" <Matt@xxxxxxxxxxxxxxxxxxxx> wrote in message news:%23n9fVZfMIHA.5040@xxxxxxxxxxxxxxxxxxxxxxx
I figured it out. Once I started the SQL Browser service, I was able to connect to my SQL05 instance using a remote connection. My question is, what does the SQL Browser service have to do with connecting to the SQL 05 instance remotely?


"Matt" <Matt@xxxxxxxxxxxxxxxxxxxx> wrote in message news:uoLB5gdMIHA.4912@xxxxxxxxxxxxxxxxxxxxxxx
Here is my issue. I installed SQL 2005 on one of my servers. Up until 10 minutes ago I was able to connect to the server remotely using SQL Server Management Studio but I was unable connect to the SQL server from the actual server that the SQL 05 instance resides on. Now, I restarted the SQL Server, and DB engine service and now I can connect to the SQL database from the actual server but not remotely. I have it configured to allow remote connections and have it setup to use TCP/IP or Named Pipes and still nothing. I've restarted the db engine service and all of the other SQL services and I still can't connect to it remotely.


Any suggestions on what could be causing this? I get this error when I try to connect remotely:

'An error has occurred while establishing a connection to the server. When connecting SQL Server 2005, this failure may be caused by the fact that under the default settign SQL does not allow remote connections....'

Now I also got that same error message when I logged onto the actual server that the SQL 2005 instance resides. I did fix that and now I'm able to log in to SQL SMS from the actual server but not remotely.

Relevant Pages

  • Re: Connection issues between .Net framwok and SQl Express 2005
    ... You will no longer need the database MDF file name in the connection string. ... simply attach the ASPNETDB.mdf to SQL Server permenantly, ... as USER INSTANCE on existing SQL Server Express, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Performance of ODBC
    ... if you have a software firewall; forward 1433/1434 to your server ... I've now created my own server with SQL Server 2005 Express, ... glitch concerns the Upsizing Wizard. ... I originally set up my ODBC connection via ...
    (microsoft.public.access.adp.sqlserver)
  • SQL 2005 Express and VS .Net 2003 wizard error More options
    ... Open the server explorer panel ... Go to the Provider tab and select SQL NAtive Client (DON'T use oledb ... Go back to the Connection tab and carry on setting up the connection ... I have installed Visual Studio 2005 Professional and then Visual Studio ...
    (microsoft.public.sqlserver)
  • Re: Timeout problem with SS2K, VS03
    ... I noticed calls in sql profiler: ... This is the server side debug stored procedure. ... a timeout issue that I cannot identify the source of. ... transaction is committed and the connection is closed cleanly and all ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Cannot connect to SQL Express on 2003 Machine from XP machine
    ... listening on UDP 1434 using netstat -abn, ... And i double checked the connection string, and i did have it the right ... But I have another 2000 server that I can connect to fine, ... I am trying to connect from an XP SP2 machine remotely to a SQL Express ...
    (microsoft.public.sqlserver.connect)