06-26-2013 05:24 AM
server 2003 r2 sp2
win7 and xp workstations (not every one, but still a couple are problematic).
IT consultant says all ports are open on server firewall and symantec endpoint. No firewall on workstations. He has also checked/ruled out DNS issue.
Error: The "servername" computer could not be reached because the port "1434" may be blocked. opening the port or reconfiguring your firewall settings may resolve this issue.
A few other workstations seem to experience this problem intermittently. I was wondering if that might be due to network latency.
06-26-2013 11:15 AM - edited 06-26-2013 11:19 AM
This can occur when the SQL Server Browser service is not started. (ACT! Server)
Start button - Run - services.msc (Enter)
Scroll down and right click on SQL Server Browser (Start)
Scroll down and right click on SQL Server (ACT7) (Start - Restart)
06-28-2013 01:53 AM
Like Juan said port 1434 is used by the SQL Browser. If the service is up and running normally, it would come down to something blocking UDP (not TCP) 1434. You can run Netstat from the cmd prompt on the server:
Start -> Run cmd netstat -a
netstat -a will show all open ports on that machine (TCP and UDP).