<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Helvetica, Arial, sans-serif">The problem seemed to have to
do with the fact that I had the IPV6 stack installed under WinXP. As
soon as I uninstalled it the client didn't have a problem enumerating
my adapter and reverse resolving my workstation's address. I wonder if
this is a bug in the python module that was used in the script? It
looks like the problem is in </font>winnet.enumerate_interfaces()
within the globus python script. <br>
<font face="Helvetica, Arial, sans-serif"><br>
</font>network query raised exception
<br>
Traceback (most recent call last):
<br>
File "\PROGRA~1\ACCESS~2\bin\globus_init.pyw", line 802, in
ThreadQueryFunc
<br>
self.interfaces = winnet.enumerate_interfaces()
<br>
<font face="Helvetica, Arial, sans-serif"><br>
-Doug B<br>
CISE/NSF<br>
</font><br>
Frank Sweetser wrote:
<blockquote cite="mid20040206020741.GA15623@erwin.wpi.edu" type="cite">
<pre wrap="">On Thu, Feb 05, 2004 at 03:35:08PM -0500, Douglas Baggett wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> File "C:\Python22\Lib\site-packages\DNS\Base.py", line 137, in conn
self.s.connect((self.ns,self.port))
File "<string>", line 1, in connect
gaierror: (7, 'getaddrinfo failed')
</pre>
</blockquote>
<pre wrap="">It seems like it's having problems doing a reverse lookup on my
hostname, but I'm able to reverse resolve my address using nslookup
without any problems. Is this a bug or is it something I should be
concerned with?
</pre>
</blockquote>
<pre wrap=""><!---->
Are you sure that nslookup is using DNS? I've caught windows nslookup
silently falling back to WINS resolution when DNS doesn't have an
answer.
</pre>
</blockquote>
</body>
</html>