[Mono-list] Bug in Mono Dns resolution (unable to connect to virtual machine)

[Alexandre Miguel Pedro Gomes]

Another bug I found is that resolving the InstanceName to a port (via Sql
Monitor Browser udp port 1434) had a very small timeout value (100ms) which
is very low in case the network path has high latency or the server is under
heavy load. I created another bug and attached the patch for this problem
here: https://bugzilla.novell.com/show_bug.cgi?id=351911

I believe both can be approved at the same time.

On Jan 6, 2008 12:56 AM, Alexandre Miguel Pedro Gomes <alexmipego at gmail.com>
wrote:

> Hi,
>
> I've been trying to connect to an Sql Server instance inside a guest
> virtual machine (VirtualBox) and using Ubuntu 7.10 as host. The networking
> is setup using bridge utils as instructed by the VirtualBox manuals.
>
> I was unable to connect getting several "Sql Server Not found" and
> timeouts from the host but not from a separate windows box running .Net
> 2.0. I tracked down the problem and found that the method GetHostEntry was
> recuring an HostEntry with 1 and only 1 IP which was 127.0.0.1. I assume
> this has something to do with the bridge and the internal C mono code
> getting this IP but after some trials with .Net to several machines and
> virtual machine with similar configurations I found that .Net only returned
> the IP specified in the parameters even if the host had more IPs attributed.
>
>
> From my observations, and that makes sense after all if one specifies an
> IP there is no logic to try to get more IPs, I've created a patch that
> successfully fixed my problem.
>
> I've created bug #351908 (
> https://bugzilla.novell.com/show_bug.cgi?id=351908) and included the patch
> there.
>
> Cheers,
>
> --
> Alexandre Gomes, Portugal




-- 
Alexandre Gomes, Portugal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-list/attachments/20080106/622d2f69/attachment-0001.html