>>>>>>
>>>>>>In 2008 you can go to properties on the server in SSMS Object Explorer, go to the connections node, and select Allow remote connections to this server. By default, SQL2005 and 2008 do not allow remote connections.
>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>That checkbox is already checked. Protocols are already on. I am authenticated to the server from my workstation. I can't imagine (except firewall) what else could be causing this.
>>>>>Tim
>>>>
>>>>Is the firewall on the server box set to allow TCP port 1433 in and out? That is the port SQL Server uses.
>>>
>>>OK, it is definately a firewall issue. I just turned the firewall off on the SBS server and was able to connect right away. Now in order to turn it back on, I have to figure out what needs to be changed to make it work.
>>>Tim
>>
>>Does your SBS server have multiple network cards? You can enable/disable the firewall per card.
>>
>>TCP Port 1433 is the key for SQL connectivity. If that is not open, you can not connect.
>
>My server has a single card with multiple Ethernet connections. They are not used except the one. Unfortunatley that was a change with SBS 2008 where it can no longer function as an edge device and have public and private segments (routing) I regret that, but none the less I have another edge device and only use a single connection on this box. I see the other connections and on the firewall tab all of them are checked so I can only guess that means the settings apply to all connections.
>
>When I disabled the firewall temporarily to test I was not presented with any choice on which connection nor was I when I set the ports to open. I also don't get a choice for incoming or outgoing when I put a port in for exception. That seems odd to me as it should be directional.
>Tim

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.