On 1/17/08, Adilson Garcia <[EMAIL PROTECTED]> wrote:
> I saw in an forum that someone had the same problem with network
> connections, and had discovered that it was a bug in the new method of the
> Dns class from the Framework
AFAIR that was in server/client with >1 NIC and getting wrong IP, or
similar stuff (I don't remember exactly).
> So I´ve downloaded the source code of the Firebird .Net provider and
> searched for the dns class, and guess, there it was.
> Again, this is a bug from the framework that for some unknow reason can´t
> resolve the ip address
Please report this to the tracker. In free time I'll look what's wrong
and how ti fix it. (few moths (mabye years) we have discussing option,
that when in connection string will be IP instead of hostname we will
not try to resolve it, which in normal case is acceptable fast/slow,
but can help in some problems with weird network configurations).
--
Jiri {x2} Cincura (Microsoft Student Partner)
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Firebird-net-provider mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
