|
Trouble on Vista 32
![[us]](/s/countries/us.gif) Shadow Hawkins on Tuesday, 11 November 2008 04:12:15
Well, I've hunted around in here for about 2 hours looking for the answer to why I can't get this silly thing to work. I've run all the netsh commands I've seen in several posts and rebooted. I'm currently using the tap901 driver and the GUI version of AICCU.
Here are the bits from an ipconfig:
Windows IP Configuration
Host Name . . . . . . . . . . . . : Michael-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection 4:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Win32 Adapter V9
Physical Address. . . . . . . . . : 00-FF-10-12-B1-4A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 00-12-5A-5E-A5-AA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet #
2
Physical Address. . . . . . . . . : 00-17-31-8F-0B-B7
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:81a8:102::(Preferred)
Link-local IPv6 Address . . . . . : fe80::3cf0:cd6f:d85e:958b%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.199(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, November 10, 2008 9:52:14 PM
Lease Expires . . . . . . . . . . : Tuesday, November 11, 2008 9:52:14 PM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection*:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{1F5CB7F7-AF0C-421C-994E-796892BF0
10E}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Can't ping, surf to, or do anything with an IPV6 address, DNS or numerical.
And suggestions?
Thanks!
Trouble on Vista 32
I'm currently using the tap901 driver and the GUI version of AICCU.
The tap901 driver (which is the correct one for Vista, as the others indeed won't work) is only supported by the console version of AICCU at the moment.
As such, you will need to use the console edition for the time being.
Trouble on Vista 32
Shadow Hawkins on Tuesday, 11 November 2008 04:49:39
Jeroen,
Thanks. That fixed the first part anyhow! Still not working for some reason. Here is the output of autotest from the command line app:
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
Name : My First Tunnel
Flag: HAS_IFHEAD not present
Flag: NEED_IFHEAD not present
[warning] Error opening registry key: SYSTEM\CurrentControlSet\Control\Class\{4D
36E972-E325-11CE-BFC1-08002BE10318}\Properties (t1)
Renaming adapter 'Local Area Connection 4' to 'aiccu' and using it
[tun-start] Trying \\.\Global\{1012B14A-FDDB-43EF-986E-FD028DA834BF}.tap
Flag: HAS_IFHEAD not present
Flag: NEED_IFHEAD not present
[AYIYA-start] : Anything in Anything (draft-02)
heartbeat_socket() - IPv4 : 192.168.0.199
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.0.199)
### This should return so called 'echo replies'
### If it doesn't then check your firewall settings
### Your local endpoint should always be pingable
### It could also indicate problems with your IPv4 stack
[AYIYA-tun->tundev] : (Socket to TUN) started
Pinging 192.168.0.199 with 32 bytes of data:
Reply from 192.168.0.199: bytes=32 time<1ms TTL=128
Reply from 192.168.0.199: bytes=32 time<1ms TTL=128
Reply from 192.168.0.199: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.0.199:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
######
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (209.197.16.66)
### These pings should reach the PoP and come back to you
### In case there are problems along the route between your
### host and the PoP this could not return replies
### Check your firewall settings if problems occur
Pinging 209.197.16.66 with 32 bytes of data:
Reply from 209.197.16.66: bytes=32 time=83ms TTL=46
Reply from 209.197.16.66: bytes=32 time=84ms TTL=46
Reply from 209.197.16.66: bytes=32 time=83ms TTL=46
Ping statistics for 209.197.16.66:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 83ms, Maximum = 84ms, Average = 83ms
######
####### [3/8] Traceroute to the PoP (209.197.16.66) over IPv4
### This traceroute should reach the PoP
### In case this traceroute fails then you have no connectivity
### to the PoP and this is most probably the problem
Tracing route to 209.197.16.66 over a maximum of 30 hops
1 25 ms 26 ms 23 ms 72.157.18.7
2 34 ms 34 ms 34 ms 72.157.38.17
3 34 ms 33 ms 33 ms 72.157.38.19
4 34 ms 33 ms 33 ms ixc01chs-ge-7-3-0.bellsouth.net [72.157.38.7]
5 28 ms 28 ms 28 ms 65.83.239.162
6 28 ms 29 ms 29 ms ixc01cae-ge-2-0-0.bellsouth.net [205.152.135.65]
7 33 ms 33 ms 33 ms ixc00ags-pos-2-0-0.bellsouth.net [65.83.239.98]
8 30 ms 30 ms 35 ms 205.152.226.85
9 33 ms 33 ms 33 ms axr00asm-so-2-2-0.bellsouth.net [65.83.239.2]
10 33 ms 32 ms 33 ms 65.83.238.72
11 48 ms 49 ms 48 ms 65.83.238.202
12 46 ms 45 ms 46 ms cr2.attga.ip.att.net [12.122.140.22]
13 45 ms 46 ms 45 ms tbr2.attga.ip.att.net [12.122.17.86]
14 44 ms 45 ms 45 ms ggr3.attga.ip.att.net [12.122.96.69]
15 50 ms 50 ms 50 ms 192.205.34.58
16 49 ms 51 ms 54 ms ae-71-52.ebr1.Atlanta2.Level3.net [4.68.103.60]
17 47 ms 53 ms 53 ms ae-63-60.ebr3.Atlanta2.Level3.net [4.69.138.4]
18 75 ms 71 ms 71 ms ae-2.ebr1.Washington1.Level3.net [4.69.132.86]
19 66 ms 67 ms 71 ms ae-91-91.csw4.Washington1.Level3.net [4.69.134.1
42]
20 67 ms 67 ms 67 ms ae-4-99.edge2.Washington4.Level3.net [4.68.17.21
1]
21 49 ms 50 ms 50 ms HIGHWINDS-N.edge2.Washington4.Level3.net [4.53.1
14.2]
22 95 ms 85 ms 87 ms 1-1.r2.da.hwng.net [209.197.1.130]
23 84 ms 84 ms 89 ms 1-3.r1.da1.hwng.net [209.197.8.9]
24 84 ms 84 ms 85 ms 209.197.16.66
Trace complete.
######
###### [4/8] Checking if we can ping IPv6 localhost (::1)
### This confirms if your IPv6 is working
### If ::1 doesn't reply then something is wrong with your IPv6 stack
Pinging ::1 from ::1 with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Ping statistics for ::1:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:1938:80:25::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
Pinging 2001:1938:80:25::2 with 32 bytes of data:
PING: transmit failed, error code 1231.
PING: transmit failed, error code 1231.
PING: transmit failed, error code 1231.
Ping statistics for 2001:1938:80:25::2:
Packets: Sent = 3, Received = 0, Lost = 3 (100% loss),
######
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1938:80:25::1)
### This confirms the reachability of the other side of the tunnel
### If it doesn't reply then check your interface and routing tables
### Don't forget to check your firewall (both IPv4 and IPv6) of course
### If the previous test was succesful then this could be both
### a firewalling and a routing/interface problem
Pinging 2001:1938:80:25::1 with 32 bytes of data:
PING: transmit failed, error code 1231.
PING: transmit failed, error code 1231.
PING: transmit failed, error code 1231.
Ping statistics for 2001:1938:80:25::1:
Packets: Sent = 3, Received = 0, Lost = 3 (100% loss),
######
###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net)
### This confirms that you can reach the central machine of SixXS
### If that one is reachable you should be able to reach most IPv6 destinations
### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connecti
on
### If your browser supports IPv6 and uses it of course.
'tracert6' is not recognized as an internal or external command,
operable program or batch file.
######
###### [8/8] Traceroute6 to (www.kame.net)
### This confirms that you can reach a Japanese IPv6 destination
### If that one is reachable you should be able to reach most IPv6 destinations
### You should also check http://www.kame.net which should display
### a animated kame (turtle), of course only when your browser supports and uses
IPv6
'tracert6' is not recognized as an internal or external command,
operable program or batch file.
######
###### ACCU Quick Connectivity Test (done)
### Either the above all works and gives no problems
### or it shows you where what goes wrong
### Check the SixXS FAQ (http://www.sixxs.net/faq/
### for more information and possible solutions or hints
### Don't forget to check the Forums (http://www.sixxs.net/forum/)
### for a helping hand.
### Passing the output of 'aiccu autotest >aiccu.log' is a good idea.
When the interface is up (i.e. aiccu is running and the interface is showing as up), Vista is saying it's a local only connection. Could that be the problem?
Trouble on Vista 32
Strange, 1231 appears to be "ERROR_NETWORK_UNREACHABLE 1231 0x4CF The network location cannot be reached. For information about network troubleshooting, see Windows Help.".
I would suggest that you (as an admin user with enough privileges, dunno how you get those in Vista though, but probably something to do with runas), execute from a cmd prompt: "netsh int ipv6 reset"
and then try again. If it doesn't work, start aiccu normally and then run "ipconfig /all" and "netsh int ipv6 show routes" and paste the outputs here.
Trouble on Vista 32
Shadow Hawkins on Tuesday, 11 November 2008 05:46:41
Here are the outputs from everything:
first aiccu:
C:\Users\Michael\Desktop\ipv6>aiccu-2008-03-15-windows-console.exe start
Succesfully retrieved tunnel information for T17867
[warning] Error opening registry key: SYSTEM\CurrentControlSet\Control\Class\{4D
36E972-E325-11CE-BFC1-08002BE10318}\Properties (t1)
Renaming adapter 'Local Area Connection 4' to 'aiccu' and using it
[AYIYA-start] : Anything in Anything (draft-02)
[AYIYA-tun->tundev] : (Socket to TUN) started
ipconfig:
C:\Users\Michael>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : Michael-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection 4:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Win32 Adapter V9
Physical Address. . . . . . . . . : 00-FF-10-12-B1-4A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b819:bc28:b93c:1f8d%33(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.31.141(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 00-12-5A-5E-A5-AA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet #
2
Physical Address. . . . . . . . . : 00-17-31-8F-0B-B7
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:81a8:102::(Preferred)
Link-local IPv6 Address . . . . . : fe80::3cf0:cd6f:d85e:958b%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.199(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, November 10, 2008 9:52:14 PM
Lease Expires . . . . . . . . . . : Tuesday, November 11, 2008 9:52:14 PM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection*:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{1F5CB7F7-AF0C-421C-994E-796892BF0
10E}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
routes:
C:\Users\Michael>netsh int ipv6 show route
Publish Type Met Prefix Idx Gateway/Interface Name
------- -------- --- ------------------------ --- ------------------------
No Manual 256 ::1/128 1 Loopback Pseudo-Interface
1
No Manual 256 2002:81a8:102::/48 10 Local Area Connection 2
No Manual 256 2002:81a8:102::/128 10 Local Area Connection 2
No Manual 256 fe80::/64 10 Local Area Connection 2
No Manual 256 fe80::/64 25 Bluetooth Network Connect
ion
No Manual 256 fe80::/64 33 Local Area Connection 4
No Manual 256 fe80::3cf0:cd6f:d85e:958b/128 10 Local Area Connectio
n 2
No Manual 256 fe80::b819:bc28:b93c:1f8d/128 33 Local Area Connectio
n 4
No Manual 256 fe80::b858:7cc1:5777:a4ac/128 25 Bluetooth Network Co
nnection
No Manual 256 ff00::/8 1 Loopback Pseudo-Interface
1
No Manual 256 ff00::/8 10 Local Area Connection 2
No Manual 256 ff00::/8 25 Bluetooth Network Connect
ion
No Manual 256 ff00::/8 33 Local Area Connection 4
Trouble on Vista 32
Shadow Hawkins on Tuesday, 11 November 2008 05:59:58
I got it. You HAVE to run the command line AICCU from an elevated prompt explicilty (i.e. a command shell with adminstrator privliges).
Just running it in the normal user mode and saying yes to the UAC prompt isn't enough.
Trouble on Vista 32
That makes sense a bit as one is configuring addresses by calling netsh and you'll probably need those privileges there.
I hope to be able to finally get on with finalizing the new AICCU and will make sure that Vista is properly tested and gives proper hints/errors otherwise.
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 11 November 2008 04:26:45
Posting is only allowed when you are