Noel,
I agree that the IPv6 IP's, bogus or otherwise, could cause a problem but that does not alter the fact that JAMES is throwing the exception (that is not getting caught), nor do I understand why JAMES was changed from a scheme that works fine even with the bogus IP's (a17) to the current scheme that won't even finish extracting if this situation exists. Could you please explain the motivation behind the change? Was the previous DNS handler failing for other users or incompatible in some way with other OS's? I am just curious as to what prompted the change.
V/R, Greg
Noel J. Bergman wrote:
I see the following: IP Address. . . . . . . . . . . . : fe80::2a0:ccff:fe34:62c5%4
You are using Microsoft's IPv6
DNS Servers . . . . . . . . . . . : 205.152.144.235 205.152.132.235 fec0:0:0:ffff::1%1 <-+ fec0:0:0:ffff::2%1 <-| fec0:0:0:ffff::3%1 <-|
| These are the apparently bogus DNS entries that cause the problem. |
--- Noel
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
