Connection problems to SQL2005 with odbc using port 1733

Hi,
I'm trying to connect to a SQL2005 server inside a firewall from another
Windows2003 server that is placed in DMZ. Both servers is hosted by our ISP
but they can't seem to find the problem.
Because the sqlserver is used by many companies we have to communicate with
the sql server on port 1733 and not default port 1433. Therefore I have made
an alias for the connection that I have called sql2005 that is set up to use
port 1733.
After configuring the odbc connection everything works, but after a while
(eg. if I restart my own computer) I reconnect to the server and I get "Sql
server does not excist or access denied". If I then enters the client
configuration and spesify port 1733 again, it works. I looks like the odbc
connection doesn't "remember" the port that is spesified.
Anybody know how to specify a custom port that the odbc connection can
remember?
Or how to specify port in a connectionstring for a asp web application?
In advance thanks a lot for your help!!
Kind regards,
Jon Haakon Ariansen
Does something like "Datasource=127.0.0.1,1733" work for you?
"Jon Haakon Ariansen" <jona@.spama.no> wrote in message
news:%23$tfZHJ3GHA.2196@.TK2MSFTNGP06.phx.gbl...
> Hi,
> I'm trying to connect to a SQL2005 server inside a firewall from another
> Windows2003 server that is placed in DMZ. Both servers is hosted by our
> ISP but they can't seem to find the problem.
> Because the sqlserver is used by many companies we have to communicate
> with the sql server on port 1733 and not default port 1433. Therefore I
> have made an alias for the connection that I have called sql2005 that is
> set up to use port 1733.
> After configuring the odbc connection everything works, but after a while
> (eg. if I restart my own computer) I reconnect to the server and I get
> "Sql server does not excist or access denied". If I then enters the client
> configuration and spesify port 1733 again, it works. I looks like the odbc
> connection doesn't "remember" the port that is spesified.
> Anybody know how to specify a custom port that the odbc connection can
> remember?
> Or how to specify port in a connectionstring for a asp web application?
> In advance thanks a lot for your help!!
> Kind regards,
> Jon Haakon Ariansen
>

Connection problems to SQL2005 with odbc using port 1733

Hi,
I'm trying to connect to a SQL2005 server inside a firewall from another
Windows2003 server that is placed in DMZ. Both servers is hosted by our ISP
but they can't seem to find the problem.
Because the sqlserver is used by many companies we have to communicate with
the sql server on port 1733 and not default port 1433. Therefore I have made
an alias for the connection that I have called sql2005 that is set up to use
port 1733.
After configuring the odbc connection everything works, but after a while
(eg. if I restart my own computer) I reconnect to the server and I get "Sql
server does not excist or access denied". If I then enters the client
configuration and spesify port 1733 again, it works. I looks like the odbc
connection doesn't "remember" the port that is spesified.
Anybody know how to specify a custom port that the odbc connection can
remember?
Or how to specify port in a connectionstring for a asp web application'
In advance thanks a lot for your help!!
Kind regards,
Jon Haakon AriansenDoes something like "Datasource=127.0.0.1,1733" work for you?
"Jon Haakon Ariansen" <jona@.spama.no> wrote in message
news:%23$tfZHJ3GHA.2196@.TK2MSFTNGP06.phx.gbl...
> Hi,
> I'm trying to connect to a SQL2005 server inside a firewall from another
> Windows2003 server that is placed in DMZ. Both servers is hosted by our
> ISP but they can't seem to find the problem.
> Because the sqlserver is used by many companies we have to communicate
> with the sql server on port 1733 and not default port 1433. Therefore I
> have made an alias for the connection that I have called sql2005 that is
> set up to use port 1733.
> After configuring the odbc connection everything works, but after a while
> (eg. if I restart my own computer) I reconnect to the server and I get
> "Sql server does not excist or access denied". If I then enters the client
> configuration and spesify port 1733 again, it works. I looks like the odbc
> connection doesn't "remember" the port that is spesified.
> Anybody know how to specify a custom port that the odbc connection can
> remember?
> Or how to specify port in a connectionstring for a asp web application'
> In advance thanks a lot for your help!!
> Kind regards,
> Jon Haakon Ariansen
>