Post reply

SQL 2008 communications

  • June 14, 2010 at 2:49 pm

    #236441

    Hello

    I am very new to SQL (as I mainly work with other MS products)

    I have built two seperate Windows 2008 R2 Servers and patched with all current MS OS patches

    I have install SQL Server 2008 Enterprise with SP1 using the default instance

    I have turned off the windows firewalls on both servers

    Both servers are member servers in a 2003 Active Directory domain

    I am installing SCOM 2007 on one of the servers, during the initall setup of SCOM 2007 you specify the SQL Server and Port number you want to connect to

    I enter W2K8-S2 (which is my SQL Server and resolves via DNS) for the server

    I do not add an instance i.e. W2K8-S2\INST1 as I installed SQL to the default instance and therefore just typed W2K8-S2

    the port defaults to 1433

    however what every I try I cannot get it to communicate

    I have gone onto the SQL Configuration Manager on W2K8-S2 and checked the under SQL Server Network Connection > Protocols for MSQLSERVER and checked TCPIP is enabled

    and set to port 1433

    I also notice though that SQL Native Client 10.0 Configuration is also set to port 1433, does this mater with they clash or are they part of the same thing?

    I have also tried enabling VIA using the same port,

    I have also tried another port

    I have also tried to reinstall using a named instance etc

    nothing seems to work, i did not have this issue with SQL 2005 on Server 2003

    Am I missing some thing? Do I need to install another 2008 Server Role like File Server role to enable SQL to communcate over a Network? (cannot imagine I would have to do that but not sure)

    any advise please? can some one explain what VIA is needed for?

    Thanks very much in advance

  • June 14, 2010 at 4:51 pm

    #1180147

    Have you ever tried to use IP? Maybe DSN was incorrectly setup?

    Did you check whether or not the IP 1433 is open?

  • June 15, 2010 at 12:19 am

    #1180209

    Hello Thanks for the reply

    I am prety sure TCP port 1433 is open, ultimately I can use a port scanner to check

    The software I am installing SCOM 2007 (Microsoft System Center 2007) is a client/server based application which uses TCP to communicate with the backend SQL Server

    I have this up on SQL 2005 running on Windows 2003 with no problems at all

    but with SQL 2008 on Windows 2008 I cannot get it to communicate. I first suspected the Windows 2008 firewall, but I completely disabled this on both servers

    I am not wondering if I have to install a second Role on the Windows 2008 Server like File Server Role in order the two servers can communicate. This would seem odd however as niether server needs to act as a File Server to the users

    Thanks, any other advise most welcome

  • June 15, 2010 at 12:23 am

    #1180210

    PS

    Apart from Netstat does any one else know of a useful utility to scan/query ports on an SQL Server to ensure it is listening and responding

    i.e. I would like to ideally also send a simply T-SQL command across the network to the SQL Server on specific port to see if it responds correctly to be sure the port is open and it is not a SCOM application installation issue causing me the problems

    Thanks

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply