We have spent a great deal of time troubleshooting connectivity issues with a just a few clients. We ended up using a network sniffer to determine that the MS SQL Server plug-in is connecting via SMB port 445 as opposed to port 1433. We found that these clients have disabled the SMB port 445 for file and print sharing due to security concerns. Thus, we were not able to connect to the database server to setup our application's database.
We are able to get around this by adding HOSTNAME,1433 in the "Server:" field of the plug-in. This appears to force the plug-in to go to the specified port.
You can verify this yourself by disabling the SMB port and attempting to connect with the MS SQL Server plug-in.
To do so follow these instructions:
-Start Registry Editor (Regedit.exe).
-Locate the following key in the registry:
-In the right-hand side of the window find an option called TransportBindName.
-Double click that value, and then delete the default value, thus giving it a blank value.
-Close the registry editor.
-Reboot your computer.
After rebooting open a command prompt and in it type
See that your computer no longer listens to port 445. You'll find that the connection test now fails unless you specify Server,Port as I mentioned above. You may actually have to specify the IPAddress unless the name still resolves.
I have two points for my post:
- I wanted to make this information available to the community because information like this has been a big help to me via the forum.
- I wanted to know if someone from InstallAware could help us understand why the plug-in would use the SMB port 445 and not 1433 by default?