I have a machine running Windows Server 2003 x64.
It has VS2003 running on it and VS2005.
in VS2003 I can connect fine to a SQL Server 2000 database running on another machine on my network.
If I launch SQL Server Management Studio, I cannot connect to it. Generally, the error is a timeout.
The VS2003 credentials seem to be much the same as the ones I enter for Management studio (Integrated security, same name, same database).
The one I'm trying to attach to is not seen in the browse list - another one is visible though I fail to get through to it which I try and connect!
I've done all the things I can think of with enabling protocols and aliases and stuff, but nothing seems to make any difference.
I can't get why VS2005 can get through and Management Services cannot. It DOES support SQL 2000 !
Iain
VS2005 YES! Management Studio NO ...
Hot Topic
- Print Report Window opens after 2 minutes??
- A QUERY THAT RUN ON DB2 THAT HAVE MORE PERFORMANCE THAN SQL SERVER 2000
- VS.NET Deployed Assemblies not showing up in Management Studio
- How can I check the version of reporting services installed?
- Dynamic Excel Sources
- Error: "no report servers were found on the specified machine"
- Cannot work with Scrip task
- SQL Server 2005 Remote Connection Problem... Big Time.
- SQL CE 2.0: Calling Engine.Dispose() after every query?
- Create DBF file from ADO.Net
SQL Server
- Changing SQL-command with a script
- Upsizing from Access to SQL Express
- Error with for..next loop variable
- maintenance plan - rebuild index fail
- BCP not exporting the "{" or "}" characters
- SSIS Reporting Source not showing up in VS.NET
- Upgrade SQL Server Beta 2 to Release
- Need a task that will zip a file prior to upload via FTP
- Optimizing LIKE OR Selects
- sqlce 3.0 vs sqlce 2.0 memory issue
VS2005 YES! Management Studio NO ...
Starsearch
I've already tried the TCP/IP protocol and I've just upped the timeout to 45 seconds with no change. The SQL Server 2000 machine is on the same subnet around 4 feet away, so it shouldn't be communication latency!
However, I've just (by almost random chance) tried the Named Pipes protocol and that has worked perfectly!
It looks like it just may be a firewall problem. Oops!
Iain
Usman9852000
In the connection dialog, click the "Options >>" button to bring up connection properties. I would try specifying a particular network protocol rather than using the default, like TCP/IP for a remote server or Shared Memory for a local server.
You could try making the connection time out a little longer as well in case the default 15 seconds isn't long enough in your environment.