If I set it so that I can work on stuff all my data-enabed web sites go down.Tell me about "instances". If I set it so that my web sites work OK I can't develop anything because all my tools need to work across the Internet and the port is blocked. This is probably a good solution to the problem I presented, but a side effect is that after I change the port in the network utility IIS (running on the same machine) loses access to the SQL databases.I'm really in a stuck place. Yes they definitely should have notified people.Tara Here's a link to help you reconfigure to avoid/reduce loss of service."Thanks for your help with this.Brian SQL Goddess Even if it was after the event I'd have appreciated a broadcast email saying "We've blocked the following ports because of virus traffic: 1433.
Thanks for the quick response!Maybe the ISP did the right thing, but they didn't tell anyone they were blocking the port - not even their own front help desk, so it has taken me most of today, arguing with various tech support people, to determine just where the blockage is.I feel they should have warned me in advance that I was going to lose it and maybe offered some advice on how to set up alternate routes. BTW, 1433 isn't recommended in an internet environment anyway, so your ISP did the right thing.Tara So they must do the Client Network Utility thing too. And no you can't get the server to listen on two ports. Type in the port number that you specified in Server Network Utility. Type in the server name or IP address in the server name field. Type in a server alias (can be anything really, but most people just use the server name with instance name if one exists). Then on the client machines, go to Start/Programs/Microsoft SQL Server/Client Network Utility.
You'll need to restart SQL Server for the changes to take affect. Select your instance, highlight TCP/IP, click properties.
To change the server, go to Start/Programs/Microsoft SQL Server/Server Network Utility. Can I get the server to listen on *both* the new port and the old 1433 at the same time? How?Brian SQL Goddess My ISP has just blocked port 1433 (blaming virus traffic), so I can't use SQL Serevr Enterprise Manager, MS-Access, Visual Studio or DreamWeaverMX on my local machine to communicate wih SQL on my server across the Internet.Question 1I can get a port opened on my host's firewall, and I can open a matching port at my end, but can I configure SQL Server on my server to listen on a port other than 1433? How?Just in case it's significant we're talking about SQL7.0 on Win2000.Question 2Assuming I can change the server, how do I configure my client (SQL Server Enterprise Manager 8.0 on Win XP Pro) to use the new port? How?Question 3My colleagues also connect over the Internet but their ISPs haven't blocked port 1433, so if I change it they'll lose connectivity and they'll have to change too. We've got lots of great SQL ServerĮxperts to answer whatever question you can come up with.
The new connection string may look like the following (example is standard security from ConnectionStrings.Site at.
To install the new client, you'll need to install the SQL Server Tools from the installation of SQL Server 2008. You may need to install the SQL Native Client 10.0 on the application server and change the connection string to use that version of the client before this will work. Under Aliases, make sure the alias you create is for the specific network library your connection string specifies.Under Client Protocols, ensure TCP/IP is enabled.Make sure of two things (both in SQL Server Configuration Manager under the 32-bit and 64-bit SQL Native Client Configuration sections): When you remove the DBMSSOCN setting, it falls back to Named Pipes instead of TCP/IP. Aliases can be configured for Named Pipes, TCP/IP, and VIA.
DBMSSOCN refers to the network library used for the connection.