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

["Ian Tobin" <itobin@xxxxxxxxxxxxx>]

Hi,

I appreciate what your saying and I agree its not a specific gplpv issue (sorry 
for thinking it was) but it can't be a malware problem as i built the new image 
(twice) from scratch (CD mounted) and has had the same problem. It worked until 
i enabled remote desktop and rebooted, probably coincidence but im lost.

In my 20 years of windows admin ive never seen this issue before so its a new 
one on me.

Thanks for your advice though, its been of great help, keep up the great 
support!  I just hope i can find a resolution that may help others who may face 
the same issue.

Ian


-----Original Message-----
From: Fajar A. Nugraha [mailto:fajar@xxxxxxxxx] 
Sent: 04 September 2009 15:53
To: Ian Tobin
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] latest GPLPV drivers 0.10.0.86 and microsoft.com

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