Once you get to IPAll, notice the value for TCP Dynamic ports - this is what port SQL Express listens on if you're using dynamic ports.įor each IP n item where TCP Dynamic ports is zero, your instance will listen on the value specified in IPAll. On your way there, notice if TCP Dynamic ports is zero for the various IP n entries and TCP Port is blank. Double-click TCP/IP (it IS enabled, right?) Choose the IP Addresses tab and scroll all the way to the bottom where you'll see IPAll. If you're fortunate enough to have SQL Server Configuration Manager on your SQL Server box, you can run that, choose your instance, expand SQL Server Network Configuration, then click Protocols for instancename. Depending on what you're using to run the VM (virtualbox? vmware?), it's possible that network settings there are interfering with what you want to do as well.
That may be worth investigating, especially if you're trying to connect to the VM from an entirely different computer the Mac's firewall may be preventing the connection in that case. There is a possibility that the Mac's network security allows connections over port 80 but not other ports. HTTP connections are okay, but not SQL Server connections. You're connecting to this virtual machine from the Mac host. To restate: you're using a Mac to host a virtual machine where your SQL Express instance lives. Running SQL Browser and connecting using the named instance as previously suggested should in theory help. The settings you give in your question imply your instance uses dynamic ports. See (v=sql.90).aspx as it applies to SQL Express 2005. SQL Express installs by default with a named instance of SQLEXPRESS.
0 kommentar(er)
