Re: command timeout - SQL 2005 express - critical customer down

I have good news and bad news...
The good news is that this is fixable, the bad news is that you haven't fixed it--just patched the problem.
Most SQL Server installations (including SQL Express) use dynamic IP assignments--each named instance gets its own dedicated port assigned when the service starts. 1433 is no longer guaranteed to be the port on which SQL Server listens.
Make sure the SQL Browser service is started on the server. This should address this issue.

See my whitepaper on connecting and chapter 9 of my latest book for more details.
http://betav.com/mtcgi/mt-search.cgi?IncludeBlogs=3&search=connecting

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

"Darin" <darin_nospam@nospamever> wrote in message news:u8q%23WF1NIHA.5208@xxxxxxxxxxxxxxxxxxxxxxx
Well, I have fixed it.

It turns out that the firewall was turned on on the server so we had to
add a port in the exception list for 1433. Strange the error we were
receiving, and of course the IT person said he didn't do anything with
the firewall on the server.

I am glad it got fixed.

Darin

*** Sent via Developersdex http://www.developersdex.com ***

.

Relevant Pages

  • Re: Connecting to an instance in a cluster
    ... "Geoff N. Hiten" wrote: ... you cannot reuse port numbers. ... Microsoft SQL Server MVP ... That is the port you have to open on the firewall. ...
    (microsoft.public.sqlserver.clustering)
  • Re: IIS, SQL 2000 & XPs Firewall
    ... Only one instance of SQL Server can use TCP port 1434. ... You may find it easier to use SQL Server Configuration Manager ... 2008 will be a named instance ... you will have to open those as exceptions in the firewall. ...
    (microsoft.public.sqlserver.connect)
  • Re: IIS, SQL 2000 & XPs Firewall
    ... You may find it easier to use SQL Server Configuration Manager ... 2008 will be a named instance ... Queries to the Data Engine must go to the port that SQL Server is ... you will have to open those as exceptions in the firewall. ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL Server 2008 remote connection problem
    ... Hitchhiker’s Guide to Visual Studio and SQL Server ... default instance of the SQL Server Database Engine listens on TCP port 1433", ... > I was trying to establish a remote connection to SQL Server 2008 from ... The server is running the XP firewall. ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL server connection problem
    ... no firewall is installed? ... Also i have check that port 1433 is not ... Will SQL server only connect to this ... > to configure the firewall to permit connections to SQL Server. ...
    (comp.databases.ms-sqlserver)