Another option is to split Tango in two at the client, leaving your webserver and the Tango client (plugin) outside the firewall or in a DMZ, and keeping the Tango server and DB inside. In this case you'll need to open a port for the Tango client connection (18100 by default, but configurable.)
This might be a good option for you if the ODBC driver connects to SQL server by some unusual mechanism. I'm not familiar with SQL server's network connections, but I know Oracle SQL*Net v2 is a nightmare to use with firewalls, since ports are dynamic. On Tue, 11 Mar 2003, Wilcox, Jamileh wrote: > I've just been handed a new little project, which involves keeping our > public Internet applications up & running while moving our SQL server > behind a firewall. > > I've researched the SQL side - according to MS, we need port 1433 open > inbound and ports 1025-5000 open outbound (assuming that I'm reading the > documentation correctly and that our SQL server is set up with the > defaults). > http://support.microsoft.com/default.aspx?scid=kb;en-us;287932 > > Now I need to doublecheck the Tango side. I've not found any info in > the Tango books so far. Can anyone tell me if there are particular > settings I'll need to plan for to make Tango play well with the > firewall? Any advice or experience that you'd care to share? > > Thanks very much! > > jamileh > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body