November 20, 2008 at 12:20 pm
I have a SQL SERVER RUNNING ON HOST WITH SOME IP ADDRESS AND USES UDP PRT 1424 AND I WANT IT TO BE ACCESSIBLE BY COLLEAGUES RUNNING SQL CLIENTS IN ANOTHER NETWORK. The firewall configurations are such that they block all connections to UDP Port 1424. Besides the network administrator has refused to modify the firewall rules. The only option i now have is to modify the code in the sql clients which are open source and can be changed at will. The code in the SQL server source code is hardcoded using port 1424.
My company's internal network is 10.6.77/24 AND THE FIREWALL IS AT 10.6.77.1
The firewall is configured as:
Src Ip :Any
Dst Ip : 10.6.77/24
Src Port : Any
Dst Prt :1424
Protocol : UDP
Allow/Blck : Block
So What should i do in such a condition? I want to let other users / colleagues be able to use the SQL server and also want to keep the firewall rules intact. Is there any workaround for this issue?
November 20, 2008 at 1:04 pm
The code in the SQL server source code is hardcoded using port 1424.
I don't understand; what do you mean by SQL Server source code? Is it so that you can only connect to tcp ip port 1424 (because of your FW settings) and you want to setup SQL Server to listen to it?
If so, use SQL Server configuration Manager go to SQL Server 2005 Network Configuration/Protocols/TCPIP/Properties and set the port to 1424.
/Elisabeth
elisabeth@sqlserverland.com
MCITP | MCT
http://sqlblog.com/blogs/elisabeth_redei/
http://linkedin.com/in/elisabethredei
November 20, 2008 at 7:47 pm
What i imply by saying is that the sql server has been programmed to use the port 1424 and it cannot be changed. The only option now i have is to configure the sql clients (operating on some other network) which are being used to access the sql server.
November 20, 2008 at 8:19 pm
Hi,
Incase you are ready to hardcode the port number in Clients, then perform below steps.
1) Goto Start --> Run --> Type "cliconfg"
2) Now goto second tab by name "alias" , Click Add
3) Type Destination Server Name in Server Alias, Select TCP/IP from network libraries
4) Type ServerName and deselect "dynamically determine port" and type the SQL Server port on which it is listening for incoming connections.
Or Simply you can enable Named Pipes as protocol between server and clients which does'nt get affected because of firewall blocking. Take a look at this article for more help in this http://www.sqlserverdba.co.cc/2008/10/sql-server-not-found-or-does-not-exist.html
Regards,
Sakthi
My Blog -> http://www.sqlserverdba.co.cc
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply