>>>With 1433 open AND the server being set to allow remote connections AND the server being set to use TCP protocol this should be working. Since it does work if you disable the firewall it has to be the firewall, and AFAIK it has to be a problem on port 1433 UNLESS you have specified a different port.
>>>
>>>Look in SSMS on the server under Management/SQL Server Logs. Open the current log and look for entries with messages that start with 'Server is listening on' - those messages will tell you the ports that SQL Server needs open.
>>>
>>>Windows firewall opens inbound ports - outbound ports are (should be) open by default, so there is no direction setting. Other firewalls are more specific.
>>
>>
>>I see an entry that says:
>>

>>SQL Server is listening on [127.0.0.1 <ipv4> 34874]
>>SQL Server is listening on ['any' <ipv4> 34873]
>>
>>

>>
>>I am wondering then since there was another instance on this computer and I installed this with a non default instance name that the port was different than the default.
>>
>>It also looks like the loopback ip address is on port 34874 while the open one would be 34873. Is that correct? I will try to open those ports and turn the firewall back on to see what happens.
>
>Different instances normally all use the default port 1433. For whatever reason, yours is not using the default. Opening those ports should work.

And id did for sure. I have the firewall back on and I changed my open port to 34873 and can still connect. Yippee.

Thanks a whole bunch William!