All of lore.kernel.org
 help / color / mirror / Atom feed
From: pembriar <pembriar@yahoo.com>
To: xen-devel@lists.xensource.com
Subject: Windows PV drivers 0.8.5 - network problems
Date: Fri, 28 Mar 2008 13:06:27 -0700 (PDT)	[thread overview]
Message-ID: <16361077.post@talk.nabble.com> (raw)


GPL PV Windows drivers version: 0.8.5

We are having issues with the PV network driver (XEN Net Device Driver)
installed on a Windows 2003 Standard 32-bit DomU VM.  This windows VM is
able to use the PV network driver for basic connectivity like getting onto
the network and pinging systems, BUT it is having the following problems on
more advanced functions:

1. DNS activity.  It is unable to use primary/secondary DNS servers to
perform any DNS lookups (forward/reverse name lookups) via NSLOOKUP.  Any
nslookup requests generate "Can't find server name" and "timed out" errors. 
We use the dns servers we have access in the ADC.  

2. WEB access.  We are also unable to use our web proxy using the PV NIC
driver to display web pages properly. 

3. RDP remote access to the VM is not working, although VNC remote access is
available.

Note 1: When I switch back to the original non-Paravirtualized network
driver (Realtek), we do not have any of these problems.

Note 2: There are no port access issues indicative here; I'm able to telnet
to all 3 services (DNS/HTTP/RDP) through their respective ports (ie.,
53/80/3389). 

Any help would be greatly appreciated!
-- 
View this message in context: http://www.nabble.com/Windows-PV-drivers-0.8.5---network-problems-tp16361077p16361077.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

             reply	other threads:[~2008-03-28 20:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 20:06 pembriar [this message]
2008-03-29  0:19 ` Windows PV drivers 0.8.5 - network problems James Harper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16361077.post@talk.nabble.com \
    --to=pembriar@yahoo.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.