March 21, 2007 at 5:46 pm
We are using SQL Server 2000 Enterprise Edition and we changed the sql port from 1433 for security reasons. The technical staff for the application that we use blessed this change and we have been using sql server this way since October. We recently began having sql odbc drops and the network engineers are suggesting that the port change may be causing some problems because SQL Server does not use UDP if you change ports – it only uses TCP/IP, but uses both TCP/IP and UDP if you are on port 1433. Can anyone tell me if this is correct?
thanks in advance
Michele
March 22, 2007 at 2:41 am
Irrespective of your TCP port (1433 or whatever), SQL Server will always listen on UDP port 1434. This port is designated as the Microsoft SQL Monitor port and clients will send a message to this port to dynamically discover how the client should connect to the Server. if you are using firewalls, not only your TCP port, also ur UDP port(1434) should be enabled in the firewall for proper SQL server access from applications.
Also you can use Server Network Utility to see the list of protocols enabled.
I dont think this is a problem for the sql drops. Pls check for connectivity issues between odbc and sql server. authentication.
Following link may be of some use for finding more details.
http://support.microsoft.com/kb/827422
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply