Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
ferrethouse
Constraint Violating Yak Guru
352 Posts |
Posted - 2009-11-10 : 11:35:48
|
This is probably a network issue but in case it is not...On our dev server we have SQL Server 2000 and 2005 installed. The 2000 is the express edition and the 2005 is enterprise. The 2000 installation is the default installation and the 2005 is <machinename>\dev2005. All of our developers in house can connect to both databases. We have one developer that works remotely and he can connect to the 2000 express installation but not the 2005. It is not a login problem. It simple can't find the database (server does not exist).Anyone have any ideas?Thanks. |
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2009-11-10 : 12:39:04
|
Have him try connecting via HostName,PortNumber where PortNumber is the specific port that the dev2005 instance is listening on. If you don't know what the port is, you can find it in the SQL Server Error Log where the startup output is logged.If HostName,PortNumber does work, then he can simply add an alias to his client machine so that he no longer needs to know the port.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog"Let's begin with the premise that everything you've done up until this point is wrong." |
|
|
behrman
Yak Posting Veteran
76 Posts |
Posted - 2009-12-01 : 10:23:55
|
One thing to check - Make sure TCPIP is enabled for SQL Server.Run the SQL Server Configuration Manager (Start->Programs->Microsoft SQL Server 2005->Configuration Tools->SQL Server Configuration Manager)- Expand SQL Server Network Configuration- Click on Protocols for MSSQLSERVER- TCP/IP should be enabled. If not, double-click on TCP/IP and enable it. You will have to restart the SQL Server service before the setting takes affect.<spam removed> |
|
|
|
|
|