SQL Server 2005 not available through the network

[Zucarita9000]

I've recently installed SQL Server 2005 Standard in order to be able to use the new accounting platform our company is implementing. I'm getting a "Server not found" error while installing the client app, but the server is functioning locally.

Just now I've installed ACT! 2009 (CMS application) which installs an instance of SQL Server Express 2005. Now, THAT instance IS available through the network because I can see it using MS SQL Sever Management Studio from another PC.

So, what did I do wrong? Why isn't the SQL Server Standard instance not available?

 

[imported_snikt]

Did you configure the ODBC connections? Does the client app require ODBC connections to be configure? Does the app require XML configs?

 

[Zucarita9000]

The client app uses a Borland utility that need to be configured with the SQL server name, but it cannot find it. Using SQL Server Management Studio I can log on to the ACT instance (SQL Server Express) but not to the full fledged SQL Server 2005 Standard instance (wich is the one that contains the accounting's software database).

 

[Nothinman]

Can you connect remotely via SSMS? If not did you make sure TCP/IP and/or Named Pipes are enabled for that instance?

 

[Zucarita9000]

No, I cannot. That instance just doesn't appear on the servers list. TCP/IP and Named Pipes are enabled.

 

[Nothinman]

Is the SQL Server Browser service running?

 

[Zucarita9000]

Yes, the Server Browser is running. I don't really know what else to look for. When I open SSMS and browse for a server, all I see in the local servers tab is the ACT instance (SQL Server Express) but NOT the instance I need. However, if I just type "localhost" in the server name field I can connect to it without problems.

If go to network servers, I can see a bunch of other machines that are also running SQL Server Express for various apps.

EDIT: When I installed SQL Server 2005 Standard I left the default instance setting. Was that wrong? Should I have renamed it?

 

[imported_snikt]

Is this happening all on clients or just that one? Can you ping the SQL Server by name/IP address from any clients?

 

[Zucarita9000]

Originally posted by: snikt
Is this happening all on clients or just that one? Can you ping the SQL Server by name/IP address from any clients?

Yes, I can ping the server, see it on the network and browse it's shares. It's just that I cannot connect to the SQL Server.

Is there anything I need to configure after doing a standard, default install?

 

[Nothinman]

Yes, I can ping the server, see it on the network and browse it's shares. It's just that I cannot connect to the SQL Server.

All of those things are totally unrelated to the SQL Browser service for that instance.

 

[imported_snikt]

Originally posted by: Zucarita9000

Originally posted by: snikt
Is this happening all on clients or just that one? Can you ping the SQL Server by name/IP address from any clients?

Yes, I can ping the server, see it on the network and browse it's shares. It's just that I cannot connect to the SQL Server.

Is there anything I need to configure after doing a standard, default install?

So it doesn't seem like a network connectivity issue. Maybe a mis-configuration somewhere, on the server or client(s).

 

[Zucarita9000]

Originally posted by: snikt

Originally posted by: Zucarita9000

Originally posted by: snikt
Is this happening all on clients or just that one? Can you ping the SQL Server by name/IP address from any clients?

Yes, I can ping the server, see it on the network and browse it's shares. It's just that I cannot connect to the SQL Server.

Is there anything I need to configure after doing a standard, default install?

So it doesn't seem like a network connectivity issue. Maybe a mis-configuration somewhere, on the server or client(s).

Exactly, is not a network problem. It's just that I'm completely lost and don't have any ideas on what else to configure.

 

[Nothinman]

Can you telnet to port 1433 on that server?

 

[Zucarita9000]

Originally posted by: Nothinman
Can you telnet to port 1433 on that server?

No.

 

[Zucarita9000]

I've taken a bunch of screenshots of the configuration settings for the SQL Server instance in question.

SQL Server Configuration Manager

SQL Server (MSSQLSERVER) Properties

SQL Server (MSSQLSERVER) Properties #2

SQL Server (MSSQLSERVER) Properties #3

SQL Server Configuration Manager #2

Named Pipes Properties

TCP IP Properties

TCP IP Properties #2

 

[Bashbelly]

what authentication are you using for that instance? might need to change it to mixed-mode authentication using studio manager (log into localhost, then right click on the instance choose properties than security, change from windows auth mode to sql server and windows auth mode). See if that helps.