++++ THIS IS AN ADVISORY ++++++++++++++++++++++++++++++++
++++ SQL SERVER PORT 1433 NO ACCESS WITH FIREWALL ON ++++
++++ FIX IS TOWARDS BOTTOM OF POST ++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I was unable to connect from Alpha on my production machine to a New Windows 2008 R2 Server I am building with SQL Server Express 2008 with the Firewall Turned on. If the firewall was off, it worked fine.
I did the usual and make sure Port 1433 was open on the Firewall, it was.
I made sure TCP/IP was enabled and set to 1433 on Native Client Config Protocols the SQL Server Configuration Manager.
After pulling out most of my hair, and wasted WAY too much time, I found it:
On the SQL Server Network Config, Protocols Tab, you right click on the TCP/IP and go to properties. It shows it's enabled and listening, but there is a tab titled "IP Addresses". After clicking it, there is a listing of IP's, IP1, IP2, etc. Each showed they were active, but not enabled, and the TCP Port was blank. I scrolled to the bottom and there was a heading "IPALL" and the TCP Port was blank.
I put in 1433 and voila. UP & RUNNING.
I don't know what caused this to happen, but it did, and if I can help someone else not to go thru this, it is somewhat worth it. I know many Alpha users are afraid of moving to SQL due to it's daunting challenges. All I can say is, once I've got it running, I have never had a serious issue. I have one client with an old SQL Server 2000 on a Windows 2000 Server over 8 years old. It just keeps humming along, but once a month or so, it stops backing up. I reboot and all is well. Give it a shot, it won't hurt that much.
++++ SQL SERVER PORT 1433 NO ACCESS WITH FIREWALL ON ++++
++++ FIX IS TOWARDS BOTTOM OF POST ++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I was unable to connect from Alpha on my production machine to a New Windows 2008 R2 Server I am building with SQL Server Express 2008 with the Firewall Turned on. If the firewall was off, it worked fine.
I did the usual and make sure Port 1433 was open on the Firewall, it was.
I made sure TCP/IP was enabled and set to 1433 on Native Client Config Protocols the SQL Server Configuration Manager.
After pulling out most of my hair, and wasted WAY too much time, I found it:
On the SQL Server Network Config, Protocols Tab, you right click on the TCP/IP and go to properties. It shows it's enabled and listening, but there is a tab titled "IP Addresses". After clicking it, there is a listing of IP's, IP1, IP2, etc. Each showed they were active, but not enabled, and the TCP Port was blank. I scrolled to the bottom and there was a heading "IPALL" and the TCP Port was blank.
I put in 1433 and voila. UP & RUNNING.
I don't know what caused this to happen, but it did, and if I can help someone else not to go thru this, it is somewhat worth it. I know many Alpha users are afraid of moving to SQL due to it's daunting challenges. All I can say is, once I've got it running, I have never had a serious issue. I have one client with an old SQL Server 2000 on a Windows 2000 Server over 8 years old. It just keeps humming along, but once a month or so, it stops backing up. I reboot and all is well. Give it a shot, it won't hurt that much.
Comment