/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! /* ALSO: Don't quote this header. It makes you look lame :-) */
Thanks for the response Dennis. I've got more clarity on the problem now. It's not that all ODBC DSN access fails. The only DB access component failing is an activeX control for crystal reports that is meant to use the DSN to extract data. And it is failing when it tries to do authentication. This DSN is set up to do SQL authentication (not NT authentication). However, it's quite possible that the activeX control is ignoring this and first trying to get a response from a domain server (which isn't available on the outside of the firewall). We discovered that the activeX control can use OLEDB instead of a DSN. The OLEDB works fine and it's faster, so we'll stick to that for now. Thanks again Henty _______________________________________________ Masq maillist - [EMAIL PROTECTED] Admin requests can be handled at http://www.indyramp.com/masq-list/ -- THIS INCLUDES UNSUBSCRIBING! or email to [EMAIL PROTECTED] PLEASE read the HOWTO and search the archives before posting. You can start your search at http://www.indyramp.com/masq/ Please keep general linux/unix/pc/internet questions off the list.
