October 24, 2008 at 8:24 am
Hello room,
I need to change the SQL Server 2005 and 2000 default TCP IP Port in order to establish a communications via firewall.
The SQL Server 2005 TCP/IP port steps:
Enclosed are my steps:
1.Go to SQL Server Configuration Manager
2.Expand the SQL Server 2005 Network Configuration
3.Select the Protocol for the SQL Server instance
4.Enabled the TCP/IP
5.Right the TCP/IP protocol and go to properties
6.Click on the IP Addresses tab
IP 1
•Active: Yes
•Enabled: Yes
•IP Address: 10.101.118.74
•TCP Dynamic Port: Blank
•TCP Port: 45611
IP 2
•Active: Yes
•Enabled: Yes
•IP Address: 10.101.118.74
•TCP Dynamic Port: Blank
•TCP Port: 45611
IP 3
•Active: Yes
•Enabled: No
•IP Address: 127.0.0.1
•TCP Dynamic Port: Blank
•TCP Port: 1433
IP ALL
•TCP Dynamic Port: Blank
•TCP Port: 45611
The SQL Server 2000 steps are:
1.Bring up the SQL Server Client Network Utility
2.Right click the TCP/IP properties
3.Change default port to 45611
Should the above steps sufficient to allow both SQL Servers established a communication pass through the firewall?
Can someone advise?
Thanks,
Edwin
October 24, 2008 at 10:08 am
for the SQL2005 box leave IP1, Ip2, IP3 unset. Configure IP All with the port number and leave dynamic blank. Restart the instance
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs"
October 24, 2008 at 10:19 am
Perry,
Thanks for your valuable help and advice.
Regards,
Edwin
October 25, 2008 at 6:20 am
your welcome
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs"
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy