Proxy + ADO + VB6...

19 Jun 2009 6:58 PM

Paulo

Hi, I've ConnStr that points to a external IP, like: "SQLOleDB...
host=200.138.0.10"... but if I'm on some place that has a proxy to go
outside, the VB6 app can not reach the external SQL SERVER port 1433... do
you have any hints to solve it ?

Using VB6 + ADO

Many thanks!

19 Jun 2009 11:23 PM

Ralph

"Paulo" <eris_pa***@terra.com.br> wrote in message
news:%23O%23Pn$Q8JHA.4608@TK2MSFTNGP05.phx.gbl...
> Hi, I've ConnStr that points to a external IP, like: "SQLOleDB...
> host=200.138.0.10"... but if I'm on some place that has a proxy to go
> outside, the VB6 app can not reach the external SQL SERVER port 1433... do
> you have any hints to solve it ?
>
> Using VB6 + ADO
>
> Many thanks!
>
>

Always go to this spot first with any connection string issues. <smile>
http://www.connectionstrings.com/

The general form is:
Data Source= tcp:<IPAddress>, <port number>;[ Network Library=XXXXXXX]

If that doesn't work, then there is likely something else in play, and you
will have to check with network administration (may need to adjust security,
permissions, another port?). In other words, there is little else you can do
with a connection string.

-ralph

20 Jun 2009 12:32 AM

Paulo

When I'm on some customer running proxy behind, the VB6 app does not connect
on SQL SERVER (default port) hosted on ISP. But if the connection is NAT or
direct, the app works well...

On IE when is proxied (like SQUID) connection shows the server IP to
route... if there's a way to put it on conn string maybe it'll work. But I
dont think I can do it.... thanks!

Show quoteHide quote

"Ralph" <nt_consultin***@yahoo.com> escreveu na mensagem
news:eXEK%23UT8JHA.4176@TK2MSFTNGP02.phx.gbl...
>
> "Paulo" <eris_pa***@terra.com.br> wrote in message
> news:%23O%23Pn$Q8JHA.4608@TK2MSFTNGP05.phx.gbl...
>> Hi, I've ConnStr that points to a external IP, like: "SQLOleDB...
>> host=200.138.0.10"... but if I'm on some place that has a proxy to go
>> outside, the VB6 app can not reach the external SQL SERVER port 1433...
>> do
>> you have any hints to solve it ?
>>
>> Using VB6 + ADO
>>
>> Many thanks!
>>
>>
>
> Always go to this spot first with any connection string issues. <smile>
> http://www.connectionstrings.com/
>
> The general form is:
> Data Source= tcp:<IPAddress>, <port number>;[ Network Library=XXXXXXX]
>
> If that doesn't work, then there is likely something else in play, and you
> will have to check with network administration (may need to adjust
> security,
> permissions, another port?). In other words, there is little else you can
> do
> with a connection string.
>
> -ralph
>
>

20 Jun 2009 6:42 AM

Bob Riemersma

"Paulo" <prbs***@uol.com.br> wrote in message
news:%23l0UQ8T8JHA.3544@TK2MSFTNGP04.phx.gbl...
> When I'm on some customer running proxy behind, the VB6 app does not
> connect on SQL SERVER (default port) hosted on ISP. But if the connection
> is NAT or direct, the app works well...
>
> On IE when is proxied (like SQUID) connection shows the server IP to
> route... if there's a way to put it on conn string maybe it'll work. But I
> dont think I can do it.... thanks!

This is common in severely locked-down networks. Only a few ports are
allowed through (outward) and often proxies are used to ensure only certain
protocols are allowed through those ports.

This is precisely why Microsoft developed things like DCOM over HTTP and
Remote Data Services (RDS). Those are precursors of what we now know of as
Web Services.

RDS is still viable, but little known now. Its advantage over using a SOAP,
JSON, or REST Web Service is that you still use ADO in your VB6 programs.

20 Jun 2009 9:03 AM

Nobody

"Paulo" <eris_pa***@terra.com.br> wrote in message
news:%23O%23Pn$Q8JHA.4608@TK2MSFTNGP05.phx.gbl...
> Hi, I've ConnStr that points to a external IP, like: "SQLOleDB...
> host=200.138.0.10"... but if I'm on some place that has a proxy to go
> outside, the VB6 app can not reach the external SQL SERVER port 1433... do
> you have any hints to solve it ?
>
> Using VB6 + ADO

As far as I know, there is nothing you can do from VB6 side. The network
administrator has to configure the proxy server to open that port. If they
are using common hardware, check this site which shows how to do it for many
routers, usually for home users, but businesses also use them:

http://portforward.com

It's best to consult the proxy/router documentation.

Also, use the following software to see if the port is open or not. Click in
the status bar where you see "TCP/IP" or "UDP/IP" to make sure that you are
using TCP.

http://home.arcor.de/partusch/html_en/devcont.html

It's free software and doesn't require installation.

20 Jun 2009 2:45 PM

Norman Yuan

Technically, you can get connected to SQL Server behind proxy, as other
replies suggested. It is network administrator is decision/work and there is
nothing you can do on you VB6 app side. However, unless the remote
connection is make on a private network (apparently what you are talking is
not, because of "proxy"), securitywise, no network administrator would allow
SQL Server would be connected to from outside network, and no system should
be designed that way. That is why all the server side technologies come into
play: ASP.NET, WCF (MS technologies), web services..

Show quoteHide quote

"Paulo" <eris_pa***@terra.com.br> wrote in message
news:%23O%23Pn$Q8JHA.4608@TK2MSFTNGP05.phx.gbl...
> Hi, I've ConnStr that points to a external IP, like: "SQLOleDB...
> host=200.138.0.10"... but if I'm on some place that has a proxy to go
> outside, the VB6 app can not reach the external SQL SERVER port 1433... do
> you have any hints to solve it ?
>
> Using VB6 + ADO
>
> Many thanks!
>