> > I am on Vista now and had the IPv6 installed and
> > enabled by default.  Before I disabled (i.e.
> > unchecked for this connection) IPv6, the proxy
> > address for CatchURL would come up with a v6 address
> > (hex digits).  So I disabled it and now get - for
> > the address - only :::1.
> 
> Disabling IPv6 was the only workaround I remember
> seeing in the forum.  If you're seeing :::1 I
> suspect you didn't disable it properly. (or didn't
> reboot)
>



I have to say "properly" was the key word here.  I didn't know there was more
than one way to do it.  So since you mentioned, I went searching.  And found
this:
<http://technet.microsoft.com/en-us/network/cc987595.aspx#EKG>
which says "In the Network Connections folder, obtain properties on all of
your connections and adapters and clear the check box next to the Internet
Protocol version 6 (TCP/IPv6) component in the list under This connection uses
the following items."
Which I had done.  And rebooted :)
Next it says:
"This method disables IPv6 on your LAN interfaces and connections, but does
not disable IPv6 on tunnel interfaces or the IPv6 loopback interface."

Well, well, well.  "Loopback interface"?  Sounds like somethin' CatchURL might
be using LOL

So the fix was in the next bullet point:

"Add the following registry value (DWORD type) set to 0xFFFFFFFF:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents

This method disables IPv6 on all your LAN interfaces, connections, and tunnel
interfaces but does not disable the IPv6 loopback interface. You must restart
the computer for this registry value to take effect."

So I guess you can't disable the IPv6 loopback interface but CatchURL worked
as it should have after making that registry edit and restarting.

Another source said to set DisabledComponents to "1" which I tried and it
didn't make a difference.  Yet another said to change it to simply "FF" which
I didn't try since I saw the technote about setting it to FFFFFFFF.  I think
that only the first 6 bits have any effect so FFFFFFFF, 0xFF, and 0x3F are
probably equivalent.  For more info, see:
<http://technet.microsoft.com/en-us/library/bb878057.aspx>
Anyway...

If this was mentioned anywhere else in this forum or other resources, it did
not appear in any of my searches.  So I apologize if it's redundant
information, but I hope it will appear when the next guy/gal comes along
trying to find the same fix.

Thanks for pointing me in the right direction!
--
~B^D