Question : troubleshoot sql tcp - connects locally but not in domain

I would like assistance in troubleshooting a connection problem within a domain. For simplicity here is the network situation: domain is run under SBS 2008, SQL server express 2008 R2 is running, and I would like to connect to it from another windows 7 pc within the domain.

Currently I can log in to the database locally using SQL management studio running the tcp protocol. And I can telnet locally (using the command telnet 192.168.1.2 1433 - although the result is just black, no command prompt). When I go to the domain pc, I cannot log in using the same credentials with tcp protocol, but I can login using named pipe protocol. If I telnet from the domain pc, it reports it cannot open a connection on port 1433.

Current theory is that sql is not listening to the port within the domain, just locally. How to confirm this problem and then correct it?

My setup for this included:
1) preparing the server: under ip addresses of the tcp/ip protocol section of sql server configuration manager, I set tcp dynamic ports to 0, and tcp port to 1433 for all the IP addresses. Currently, force encryption is off.
2) opening the firewall: on the server, under inbound rules,  I have opened the firewall on port 1433 for local and remote connections. I also created a sql control inbound rule for udp on port 1434.
3) preparing the router: port 1433 and 1434 are directed to the server and enabled.

Being able to connect to the sql server using a domain tcp connection is a first troubleshooting step towards making a TLS/SSL connection over tcp. For that, I was stumped when I could not see the UCC SSL certificate under the list of available certificates (found at sql server configuration manager>protocols for db> certificate). I can see this certificate has been installed in the computer account (under personal) using MMC. Is there some special way that SQL needs certificates installed in order for it to use them?

Hoping to work with an expert who has set this up, or knows the problem. I have already reviewed much of the MSDN material on this, so please, no vague links to general protocol info. I need to work with someone who can recommend steps to do this.

Answer : troubleshoot sql tcp - connects locally but not in domain

You should be able to add the application, but need to select the executable manually. For udp/1434 it is the browser sqlbrowser.exe (usually "c:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe"), for tcp/1433 sqlservr.exe ("c:\Program Files\Microsoft SQL Server\MSSQL10.EXPRESS10\MSSQL\Binn\sqlservr.exe"). You can lookup both in services.msc.

With "remote port" I meant the port of the client in the firewall. You have set it to 1433 ("Here are the settings for the firewall exception rule: protocol type is tcp, local port is 1433, remote port is 1433, ").