I changed the connection timeout value to 30 seconds and seems it work. You
"Roger Wolter[MSFT]" wrote:
> Chances are, something is slower in your new environment and the 15 second
> default connection timeout is too short. When the connection dialog box
> comes up, click on the Options button and you can increase the connection
> timeout value from the 15 second default.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
>
http://www.microsoft.com/info/cpyright.htm >
> "Javier" <Javier@discussions.microsoft.com> wrote in message
> news:904A4F9A-2F93-48E5-9B5E-ABB085D426E0@microsoft.com...
> >I have the problem that at times I can't connected to the database via
> > Microsoft SQL Server Management Studio.
> >
> > The error is: "Timeout expired. The timeout period elapsed prior to
> > completion of the operation or the server is not responding".
> >
> > But in other times I can obtain a positive connection, I don't understand
> > what is the problem.
> >
> > Before it functioned well but I had to install a new hard disk in my PC of
> > work and now intermittent fails the connection.
> >
> > The server is Windows 2003 Server Enterprise with all the patches and
> > updatings and all is up to date and the workstation is Windwos XP Pro with
> > all the patches and updatings up to date and antivirus too.
> >
> > The SQL Server 2005 is Standard Edition with the SP1 installed, and mixed
> > authentication.
> >
> > Best Regards,
> >
> > Javier Salvatierra
>
>