| BrianLowe 2004-06-10, 7:14 pm |
| I've been using the IP address of my db server as the server name for 2 years
and all has gone well.
The connection string looked like
<add key="MM_CONNECTION_STRING_myname" value="Persist Security Info=False;Data
source=111.222.333.444;Initial Catalog=mydb;User ID=myuser;Password=mypwd;" />
and this was fine on my development workstation accessing the db server over
the Internet and on the server, looping round TCP/IP on the same machine.
I guess I got away with it.
My ISP has now blocked the default SQL port (1433) because of virus traffic,
so I was forced to get a new port set up on my server.
Of course all my webs lost db connectivity, so I had to set up an alias in the
SQL server utilities on the server and change all the connection strings in all
the web applications to use the alias instead of TCP/IP.
The connection strings now look like
<add key="MM_CONNECTION_STRING_myname" value="Persist Security Info=False;Data
source=myserver;Initial Catalog=mydb;User ID=myuser;Password=mypwd;" />
and all the webs served by IIS have good connections to the db bypassing
TCP/IP.
Now I have the new port set up and I've set up a matching alias on my
workstation with the same name, so that when the local copy of the site is
running under IIS it can get access to the distant SQL server through the alias
and use the correct port.
All is well. SQL Client tools, MS-Access and Visual Studio all see the Alias
and connect just fine.
Of course the reason I'm posting in a DW forum is that DW doesn't want to play.
If I try to open a file that uses one of the new connection strings to edit
anything DW sits for ages and then declares that the server is not available.
I don't want to use a different connection string because everything is
working fine on the server and locally in VisualStudio.
Is there a config option that will stop DW crashing out and get me access to
my SQL tables again?
|