WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] latest GPLPV drivers 0.10.0.86 and microsoft.com

To: Ian Tobin <itobin@xxxxxxxxxxxxx>
Subject: Re: [Xen-users] latest GPLPV drivers 0.10.0.86 and microsoft.com
From: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Date: Fri, 4 Sep 2009 21:52:49 +0700
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 04 Sep 2009 07:55:45 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <039E0B4AA9103344A80DA55DDDC76A932395F2@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <039E0B4AA9103344A80DA55DDDC76A932395E9@xxxxxxxxxxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0177D04F@trantor> <039E0B4AA9103344A80DA55DDDC76A932395EA@xxxxxxxxxxxxxxxxxxxxxx> <7207d96f0909040426l78c4b7ces62ab0adba41da154@xxxxxxxxxxxxxx> <039E0B4AA9103344A80DA55DDDC76A932395EF@xxxxxxxxxxxxxxxxxxxxxx> <7207d96f0909040502u5ae95380qadd270a257be11bf@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0177D076@trantor> <039E0B4AA9103344A80DA55DDDC76A932395F1@xxxxxxxxxxxxxxxxxxxxxx> <7207d96f0909040546w20c9e1f6hee007bbf1bf1ee75@xxxxxxxxxxxxxx> <039E0B4AA9103344A80DA55DDDC76A932395F2@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, Sep 4, 2009 at 9:04 PM, Ian Tobin<itobin@xxxxxxxxxxxxx> wrote:
> Hi,
>
> Ok here is the results
>
> -----------------------------------------------------------------------------
>
> C:\Documents and Settings\support>nslookup www.microsoft.com
> Server:  ns1.externalresolver.rapidswitch.com
> Address:  87.117.198.200
>
> Non-authoritative answer:
> Name:    lb1.www.ms.akadns.net
> Address:  64.4.31.252
> Aliases:  www.microsoft.com, toggle.www.ms.akadns.net
>          g.www.ms.akadns.net
>
>
> C:\Documents and Settings\support>
>
> ---------------------------------------------------------------------------------
>
>
>
>
> -----------------------------------------------------------------------------------
>
> Microsoft Windows [Version 5.2.3790]
> (C) Copyright 1985-2003 Microsoft Corp.
>
> C:\Documents and Settings\support>ping www.microsoft.com
> Ping request could not find host www.microsoft.com. Please check the name and 
> try again.

Okay, so nslookup CAN find the host (64.4.31.252) but ping CAN NOT
find the host. The only time I have seen something like this is on
malware-infected servers.

Either way, it's not Xen issue anymore. Xen's networking can pass UDP
DNS traffic just fine (nslookup got the correct result). You might
have better luck asking MS guys why nslookup can succeed while ping
can't find the host, and how to fix the problem.

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>