Joined: 11/16/2009
Posts: 13
|
Running the Site Setup Utility yielded some unexpected port requirements for our environment. We have a Web server configured in our DMZ. The SQL Server 2005 Database instance is "internal" behind the main firewall.
As it turns out, TCP Port 1050 and UDP Port 143X were required to be opened in the firewall in addition to the standard TCP Port 143X used for SQL Server. The Site Setup Utility failed until those ports were opened through the firewall to the database server.
I'm not sure if this is something with our environment configuration or ektron configuration that requires the TCP 1050 and UDP 143X ports. Has anyone run into this same issue, that could provide insight into the usage of those ports?
Also, running the Ektron Search Data Configuration utility yielded another error:
"Failed to connect to database A network-related or
instance-specific error occurred while establishing a connection to SQL Server.
The server was not found or was not accessible. Verify that the instance name
is correct and that SQL Server is configured to allow remote connections.
(provider: SQL Network Interfaces, error: 25 - Connection string is not valid)”
The connection string is automatically populated matches the entry in the Web.config. We do have access to the CMS Work Area, for the site, so it does not make sense why the connection string fails in the Ektron Search Data Configuration utility. No additional ports were detected by the Network team for requests being made during this process.
The server in the connection string is a reference to a DB instance (ex: ServerName\DBInstanceName). So, having the backslash is the only thing that we'd consider out of the ordinary.
Insights?
|
Joined: 11/16/2009
Posts: 13
|
UDP 1434: When SQL Server clients request SQL Server resources, the client network library sends a UDP message to the server using port 1434. SQL Server Browser responds with the TCP/IP port or named pipe of the requested instance. The network library on the client application then completes the connection by sending a request to the server using the port or named pipe of the desired instance. Reference: http://msdn.microsoft.com/en-us/library/ms181087.aspx
|
Joined: 11/16/2009
Posts: 13
|
TCP1050: The DB had configured IPALL to use dynamic ports and TCP1050 was the dynamic port assigned. Since we're going through a firewall, we want these to be static as rules need to be set for server to server port communication. We needed to update our configuration to use a static port. Under Protocols > TCP/IP Properties > IPALL: Blank out TCP Dynamic Ports, Add static port to use in TCP Port.
|
Joined: 11/16/2009
Posts: 13
|
Ektron Search Data Configuration utility failure: Still guessing on this one. But this would not function unless the port was specified in the connection string. We were expecting TCP1434, but it was actually TCP1050 with our original configuration. It appears that the C++ code in the Ektron Search Data Configuration utility is not using the SQL Native Client, which would initial send a request to SQL Browser on UDP1434 to get the correct port for the specified instance.
|