<html>
<body>
Ah, good find. I'll do some testing with the IPV6 stack installed and see
if I can reproduce this.<br><br>
(Also entered into bugzilla as bug 852).<br><br>
--bob<br><br>
At 07:16 AM 2/6/2004, Douglas Baggett wrote:<br>
<blockquote type=cite class=cite cite><font face="Helvetica, Helvetica">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, Helvetica"><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, Helvetica"><br>
-Doug B<br>
CISE/NSF<br>
</font><br>
Frank Sweetser wrote: <br>
<blockquote type=cite class=cite cite><br>
<pre>On Thu, Feb 05, 2004 at 03:35:08PM -0500, Douglas Baggett wrote:
</pre><blockquote type=cite class=cite cite><blockquote type=cite class=cite cite><br>
<pre> 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><br>
<pre>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><br>
<pre>
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></blockquote></body>
</html>