Re: VB app connect THROUGH proxy to a remote SQL database
- From: "Alex Clark" <alex@xxxxxxxxxxxxx>
- Date: Wed, 13 Feb 2008 18:19:39 -0600
That's a bummer. You might be able to extract just the core elements of
your DAL (i.e. just the SQL helper functions that handle actual
communication to the SQL Server instance) out into a web-service and
redirect your clients calls to it?
I feel your pain in terms of inflexible IT admins thinking the network is
their baby. The whole "HTTP proxy is way more secure than allowing outgoing
connections willy-nilly!" line is amusing to say the least...
Regards,
Alex
"Gary Shell" <gshell@xxxxxxxx> wrote in message
news:6350753F-5EB0-4107-9C43-D6A4B5175D57@xxxxxxxxxxxxxxxx
You understand the porblem just fine. However convincing the end users IT
department to make such a change would shall we say be "pissin' in the
wind". That's not going to happen, unfortunately. They are a HUGE
corporation and are not going to redo things to accomodate my app.
Gary
"Alex Clark" <alex@xxxxxxxxxxxxx> wrote in message
news:OfWbdSpbIHA.3484@xxxxxxxxxxxxxxxxxxxxxxx
While a lot of people are recommending you go through the
not-insignificant task of redesigning your entire DAL/mid-tier to work
via a web-service, I actually would recommend talking to IT first and
seeing if there isn't a quick (and still secure) alteration they could
make for you.
If I understand you correctly, the client app and the SQL server are on
two separate networks and there is a proxy between them. From what I can
gather, incoming connections to the SQL server are not the problem - it's
outgoing connections from your client apps which have only an HTTP proxy
to go through that's causing the headaches. Had IT configured the
client-apps network with a router rather than just an HTTP proxy, things
would be fine --- please correct me if I'm wrong.
Real routers, as opposed to HTTP proxies, generally allow outgoing
connections on *any* port unless specifically configured otherwise.
There is no real threat in allowing a client from behind the
router/firewall to initiate an outbound connection to a remote server;
many corporations use this configuration.
"Gshell" <Gshell@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5DEAF5EA-414F-44EA-8AE1-E4A626B0D83B@xxxxxxxxxxxxxxxx
I have a VB.net app that connects to a remote SQL server via TCP/IP. Most
folks can connect just fine. However some enterprise users are in a
corporate environment that will only allow connections through a
corporate
proxy server.
The VB app does the connect to the remote SQL server via a fully
routeable
IP address over port 1433.
Having no such experience, I have no idea what I need to do to my app to
allow that. And what sort of interaction I will personally need to have
(if
any) with thier IT department to configure the proxy server in any way.
The
user mentioned that "Only permissible outbound connection is through
proxy
server and it is only allowed with TCP/IP port 80 and it is only
possible by
authenticating with Domain ID and password." I would assume that means
the
connection from the VB app to the Proxy server is over port 80 and that
somehow the proxy server will know (or be told) to then route to IP
address
of the SQL Server over port 1433.
Can anyone offer any insight or links that might point me in the right
direction?
Thanks!
.
- Follow-Ups:
- Re: VB app connect THROUGH proxy to a remote SQL database
- From: Mr. Arnold
- Re: VB app connect THROUGH proxy to a remote SQL database
- References:
- Re: VB app connect THROUGH proxy to a remote SQL database
- From: Alex Clark
- Re: VB app connect THROUGH proxy to a remote SQL database
- From: Gary Shell
- Re: VB app connect THROUGH proxy to a remote SQL database
- Prev by Date: Re: Multi-Threading
- Next by Date: Re: VB app connect THROUGH proxy to a remote SQL database
- Previous by thread: Re: VB app connect THROUGH proxy to a remote SQL database
- Next by thread: Re: VB app connect THROUGH proxy to a remote SQL database
- Index(es):
Relevant Pages
|
