You can't go across a Firewall with any "Domain stuff".
I don't know about FoxPro itself but the FoxPro Database Server should make
itself available as a type of "Service" just like an other Database Server
would, therefore what you have to do is "publish" the Datbase Server using
the Firewall. Then you contact the external side of the Firewall *as if* it
was the Database Server and the Firewall will handle the communication
between itself and the Database Server.
Check the Firewall's documentation on how to do this. Different vendors use
different names for it,...the definitions of terms have become "chaos" with
Firewall Vendors, so some may call it "publishing" some may call it NAT,
some may call it Static NAT, some may call it Reverse-NAT, some may call it
One-toOne-NAT. You'll have to sort that out yourself.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"Jose Mariscal" <jm*******@ttcmarketingsolutions.com> wrote in message
news:#s**************@TK2MSFTNGP11.phx.gbl...
I know this was posted earlier, but I am re-posting it due ot my failure
to provide certain info. I appreciate any and all help concerning this!
We have web server A, sitting outside out firewall in the DMZ
Database server (FoxPro) B, sitting inside out firewall
No trusts, seperate domains.
Webserver A, running just ASP (No ASP.NET) needs to access a DB on B, but
just times out
with no error (bottom of page says done).
I have a strong feeling it is because we need to do cross domain
pemissions. I know how to set this up for ASPNET, but not just ASP.
Help Anyone?