Another day lost. As many times as I’ve helped others get connected, nothing worked today as I tried to connect from one system in a Workgroup to a SQL Server on a local (trusted) domain. I tried everything imaginable including:
- Checking to see it the server properties were set to permit remote connections. They were.
- Was the SQL Browser service running? It was.
- Did the SQL Server Configuration Manager say that the right protocols were enabled? Yes, they were.
- I tried to Telnet to the IP address and port being used (based on SSCM). It worked locally but not over the network.
- I stopped the Windows Firewall service as I was running Small Business Service and it thinks it knows best about configuring client firewalls (despite the fact that I have other firewall hardware). That made no difference.
Nothing made any difference. I could not connect from other domain-based systems either. The rest of the story? Well, I remembered having installed Windows 7 on top of an existing Windows Vista system. I had assumed that it had joined the SBS domain correctly (I ran “Connect” which was supposed to do that). Apparently it didn’t. When I dropped the offending system from the domain, went into SBS, dropped the system there, and rejoined the domain it worked fine. Everyone could see the SQL Server. That only took 6 hours of fiddling to figure out. I’m hesitant to run connect again…
Sigh. How does anyone get any work done if all we do is frutz with systems?