|
weird problem in vista
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Monday, 17 August 2009 17:10:04
Hello,
I am trying to get my first IPv6 connection started. I looked through the wiki, found the "configuring for vista" but still got troubles. I dont know if it is my network or the firewall.
I had some difficulties in step 8, with the "DNS lookup". In the end could fix this. Step 9 was ok, but step 11 caused problems.
This is what I got:
C:\Windows\system32>netsh int ipv6 show subinterface
MTU MediaSenseState Bytes in Bytes uit Interface
------ --------------- --------- --------- -------------
4294967295 1 0 0 Loopback Pseudo-Interface 1
1500 2 0 0 Draadloze netwerkverbinding 2
1280 5 0 0 LAN-verbinding* 7
1500 1 0 0 LAN-verbinding
1280 5 0 0 LAN-verbinding* 14
1500 5 0 0 Bluetooth-netwerkverbinding
1280 5 0 0 LAN-verbinding* 23
1500 1 0 0 LAN-verbinding 2
C:\Windows\system32>netsh int ipv6 show address
Interface 1: Loopback Pseudo-Interface 1
Adrestype DAD-status Geldig Voorkeur Adres
--------- ----------- ---------- ---------- ------------------------
Overig Voorkeur infinite infinite ::1
Interface 13: Draadloze netwerkverbinding 2
Adrestype DAD-status Geldig Voorkeur Adres
--------- ----------- ---------- ---------- ------------------------
Overig Afgeschaft infinite infinite fe80::9c24:135c:e281:76c0%13
Interface 9: LAN-verbinding
Adrestype DAD-status Geldig Voorkeur Adres
--------- ----------- ---------- ---------- ------------------------
Overig Voorkeur infinite infinite fe80::cdba:13de:5b5b:679c%9
Interface 26: LAN-verbinding* 14
Adrestype DAD-status Geldig Voorkeur Adres
--------- ----------- ---------- ---------- ------------------------
Overig Afgeschaft infinite infinite fe80::100:7f:fffe%26
Interface 12: Bluetooth-netwerkverbinding
Adrestype DAD-status Geldig Voorkeur Adres
--------- ----------- ---------- ---------- ------------------------
Overig Afgeschaft infinite infinite fe80::15ad:9473:8baa:c42d%12
Interface 31: LAN-verbinding 2
Adrestype DAD-status Geldig Voorkeur Adres
--------- ----------- ---------- ---------- ------------------------
Handmatig Voorkeur infinite infinite 2002:81a8:102::
Overig Voorkeur infinite infinite fe80::ec64:1393:a216:ab00%31
C:\Windows\system32>netsh int ipv6 show routes
De volgende opdracht is niet gevonden: int ipv6 show routes.
The following command is not found: int ipv6 show routes
C:\Windows\system32>ipconfig /all
Windows IP-configuratie
Hostnaam . . . . . . . . . . . . : laptop-julius
Primair DNS-achtervoegsel . . . . :
Knooppunttype . . . . . . . . . . : gemengd
IP-routering ingeschakeld . . . . : nee
WINS-proxy ingeschakeld . . . . . : nee
DNS-achtervoegselzoeklijst. . . . : SpeedNet
Ethernet-adapter LAN-verbinding 2:
Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : TAP-Win32 Adapter V9
Fysiek adres. . . . . . . . . . . : 00-FF-DB-AB-41-79
DHCP ingeschakeld . . . . . . . . : ja
Autom. configuratie ingeschakeld : ja
IPv6-adres. . . . . . . . . . . . : 2002:81a8:102::(voorkeur)
Link-local IPv6-adres . . . . . . : fe80::ec64:1393:a216:ab00%31(voorkeur)
Automatisch geconf.IPv4-adres . . : 169.254.171.0(voorkeur)
Subnetmasker. . . . . . . . . . . : 255.255.0.0
Standaardgateway. . . . . . . . . :
DNS-servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS via TCPIP . . . . . . . . : ingeschakeld
Ethernet-adapter Bluetooth-netwerkverbinding:
Mediumstatus. . . . . . . . . . . : medium ontkoppeld
Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : Bluetooth-apparaat (Personal Area Netw
)
Fysiek adres. . . . . . . . . . . : 00-1A-92-79-F7-99
DHCP ingeschakeld . . . . . . . . : ja
Autom. configuratie ingeschakeld : ja
Ethernet-adapter LAN-verbinding:
Verbindingsspec. DNS-achtervoegsel: SpeedNet
Beschrijving. . . . . . . . . . . : Realtek RTL8168/8111 Family PCI-E Giga
Ethernet NIC (NDIS 6.0)
Fysiek adres. . . . . . . . . . . : 00-1A-92-CE-EA-70
DHCP ingeschakeld . . . . . . . . : ja
Autom. configuratie ingeschakeld : ja
Link-local IPv6-adres . . . . . . : fe80::cdba:13de:5b5b:679c%9(voorkeur)
IPv4-adres. . . . . . . . . . . . : 192.168.0.88(voorkeur)
Subnetmasker. . . . . . . . . . . : 255.255.255.0
Lease verkregen . . . . . . . . . : maandag 17 augustus 2009 15:55:42
Lease verlopen. . . . . . . . . . : maandag 28 september 2009 7:55:41
Standaardgateway. . . . . . . . . : 192.168.0.1
DHCP-server . . . . . . . . . . . : 192.168.0.1
DNS-servers . . . . . . . . . . . : 192.168.1.1
192.168.0.1
NetBIOS via TCPIP . . . . . . . . : ingeschakeld
Adapter voor draadloos LAN Draadloze netwerkverbinding 2:
Mediumstatus. . . . . . . . . . . : medium ontkoppeld
Verbindingsspec. DNS-achtervoegsel: SpeedNet
Beschrijving. . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network
nection #2
Fysiek adres. . . . . . . . . . . : 00-18-DE-C6-E9-D5
DHCP ingeschakeld . . . . . . . . : ja
Autom. configuratie ingeschakeld : ja
Tunnel-adapter LAN-verbinding* 7:
Mediumstatus. . . . . . . . . . . : medium ontkoppeld
Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : isatap.{BE61D58C-DCB8-4576-9595-3365A4
72E}
Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP ingeschakeld . . . . . . . . : nee
Autom. configuratie ingeschakeld : ja
Tunnel-adapter LAN-verbinding* 14:
Mediumstatus. . . . . . . . . . . : medium ontkoppeld
Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Fysiek adres. . . . . . . . . . . : 02-00-54-55-4E-01
DHCP ingeschakeld . . . . . . . . : nee
Autom. configuratie ingeschakeld : ja
Tunnel-adapter LAN-verbinding* 23:
Mediumstatus. . . . . . . . . . . : medium ontkoppeld
Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : isatap.home.nl
Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP ingeschakeld . . . . . . . . : nee
Autom. configuratie ingeschakeld : ja
This is my log from Aiccu:
Tunnel Information for T22717:
PoP Id : nlhaa01
IPv6 Local : 2001:1af8:fe00:1a4::2/64
IPv6 Remote : 2001:1af8:fe00:1a4::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
Name : My First Tunnel
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.0.88)
### 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
Pingen naar 192.168.0.88 met 32 bytes aan gegevens:
Algemene fout.
Algemene fout.
Algemene fout.
Ping-statistieken voor 192.168.0.88:
Pakketten: verzonden = 3, ontvangen = 0, verloren = 3
(100% verlies).
######
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (94.75.219.73)
### 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
Pingen naar 94.75.219.73 met 32 bytes aan gegevens:
Algemene fout.
Algemene fout.
Algemene fout.
Ping-statistieken voor 94.75.219.73:
Pakketten: verzonden = 3, ontvangen = 0, verloren = 3
(100% verlies).
######
####### [3/8] Traceroute to the PoP (94.75.219.73) 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
Traceren van de route naar nlhaa01.sixxs.net [94.75.219.73]
via maximaal 30 hops:
1 Algemene fout.
De trace is voltooid.
######
###### [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
Pingen naar ::1 van ::1 met 32 bytes aan gegevens:
Algemene fout.
Algemene fout.
Algemene fout.
Ping-statistieken voor ::1:
Pakketten: verzonden = 3, ontvangen = 0, verloren = 3
(100% verlies).
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:1af8:fe00:1a4::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
Pingen naar 2001:1af8:fe00:1a4::2 met 32 bytes aan gegevens:
PING: verzenden mislukt. Foutcode 1231.
PING: verzenden mislukt. Foutcode 1231.
PING: verzenden mislukt. Foutcode 1231.
Ping-statistieken voor 2001:1af8:fe00:1a4::2:
Pakketten: verzonden = 3, ontvangen = 0, verloren = 3
(100% verlies).
######
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1af8:fe00:1a4::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
Pingen naar 2001:1af8:fe00:1a4::1 met 32 bytes aan gegevens:
PING: verzenden mislukt. Foutcode 1231.
PING: verzenden mislukt. Foutcode 1231.
PING: verzenden mislukt. Foutcode 1231.
Ping-statistieken voor 2001:1af8:fe00:1a4::1:
Pakketten: verzonden = 3, ontvangen = 0, verloren = 3
(100% verlies).
######
###### [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 connection
### If your browser supports IPv6 and uses it of course.
######
###### [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
######
###### 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.
weird problem in vista
![[us]](/s/countries/us.gif) Shadow Hawkins on Monday, 17 August 2009 18:05:04
So what problems are you actually having?
weird problem in vista
Shadow Hawkins on Monday, 17 August 2009 18:46:25
I can only establish IPv4 connections, not IPv6, whatever I try. Logging in with the sixxs program works, DNS for IPv6 works too. Opening websites however creates a problem, so does ping and tracert. The weirdest thing I find is that the ping with the IPv4 to any adress doesnt work either, including my own. Pinging to 127.0.0.1 works.
weird problem in vista
Shadow Hawkins on Monday, 17 August 2009 18:52:14
Does your adapter have an IPv6 address assigned? Are you doing DHCPv6 or running an RA server? (I'm sure it's listed above, but I wasn't able to figure anything out.)
If Vista does not have an IPv6 address assigned to the interface, you will be unable to browse the web over IPv6
weird problem in vista
![[fi]](/s/countries/fi.gif) Shadow Hawkins on Monday, 17 August 2009 18:54:53
Did you read the Vista config properly?
Either I understand Dutch even worse than I think, or you may have run step 8 for wrong adapter...
https://www.sixxs.net/wiki/Configuring_Windows_Vista
...
* Run the following command to work-around the issue with Vista and AICCU IPv6 "AAAA" DNS lookups with a virtual interface:
netsh int ipv6 add address "Local Area Connection" 2002:81a8:102::
* Make sure to replace "Local Area Connection" with your actual physical ethernet (wired or wireless) network interface name if the name is different on your computer.
....
The idea is to run that on physical real adapter to disable IPv6 DNS there, and not to do that for TAP-adapter. To me it looked like you had ran the command for the TAP-adapter:
Verbindingsspec. DNS-achtervoegsel: Beschrijving. . . . . . . . . . . : TAP-Win32 Adapter V9 Fysiek adres. . . . . . . . . . . : 00-FF-DB-AB-41-79 DHCP ingeschakeld . . . . . . . . : ja Autom. configuratie ingeschakeld : ja IPv6-adres. . . . . . . . . . . . : 2002:81a8:102::(voorkeur)
weird problem in vista
Shadow Hawkins on Monday, 17 August 2009 22:33:30
Seemed that caused the problem. Now I can get IPv4 traffic but I have no IPv6 stack. (ping ::1 gives error)
I think its because of another (something I call shitty) problem: Norman personal Firewall. Blocks all IPv6 traffic, and I dont know how I can stop it...
Next stop: Norman support.
weird problem in vista
Generally these "firewalls" insert themselves in the Winsock queue, as they don't support AF_INET6 (IPv6), they don't allow it true and just drop it. Technically, as it is a firewall this is correct, but actually they should have support for IPv6 ages ago. Solution: uninstall that junk.
Windows Firewall does IPv6 perfectly fine, thus why bother with it?
If you want the nice "app X is going to listen on Y" messages, just install Windows Defender, which might be default in Vista.
weird problem in vista
Shadow Hawkins on Tuesday, 18 August 2009 14:33:10
FYI Defender is installed in Vista by default
As for the firewall issue...we had the same problem with Panda...if we turned off HTTP scanning/filtering, the problem went away
weird problem in vista
Shadow Hawkins on Tuesday, 18 August 2009 16:07:17
Uninstalled norman, still trouble with ping...
The "renaming to sixxs" isnt working. It still shows the old "LAN-verbinding 2". It could be because of the warning i received when starting aiccu:
(from aiccu start)
Succesfully retrieved tunnel information for T22717
sock_printf() : "QUIT Deer Stop"
Tunnel Information for T22717:
PoP Id : nlhaa01
IPv6 Local : 2001:1af8:fe00:1a4::2/64
IPv6 Remote : 2001:1af8:fe00:1a4::1/64
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 'sixxs' to 'aiccu' and using it
[tun-start] Trying \\.\Global\{DBAB4179-402E-4216-B0E5-33A39C493AE5}.tap
Flag: HAS_IFHEAD not present
Flag: NEED_IFHEAD not present
[AYIYA-start] : Anything in Anything (draft-02)
[AYIYA-tun->tundev] : (Socket to TUN) started
The problem I first had with the wrong address is solved:
Interface 9: LAN-verbinding
Adrestype DAD-status Geldig Voorkeur Adres
--------- ----------- ---------- ---------- ------------------------
Handmatig Voorkeur infinite infinite 2002:81a8:102::
Overig Voorkeur infinite infinite fe80::cdba:13de:5b5b:679c%9
weird problem in vista
Shadow Hawkins on Tuesday, 18 August 2009 18:12:23
You might try to rename the adapter to "Aiccu" by hand in Vista. There is a rename option available for each connection in "Control Panel\Network Connections".
Also my Vista gives an error in Aiccu console, but still works:
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\{
36E972-E325-11CE-BFC1-08002BE10318}\Properties (t1)
Found interface named 'aiccu', with guid {98023785-FE5F-4BB1-A4E5-187A73181C38
using it
[tun-start] Trying \\.\Global\{98023785-FE5F-4BB1-A4E5-187A73181C38}.tap
Flag: HAS_IFHEAD not present
Flag: NEED_IFHEAD not present
[AYIYA-start] : Anything in Anything (draft-02)
[AYIYA-tun->tundev] : (Socket to TUN) started
Luckily I have a hardware IPv6-tunnel-enabling cheap home router (a Trendnet TEW-652BRP reflashed to be D-link DIR-615rev.C ), so there is no need to struggle with Aiccu settings in Vista.
weird problem in vista
Shadow Hawkins on Tuesday, 18 August 2009 18:52:01
Well, at this stage the last successive one is [4/8] from the autotest... I can ping ::1 and the local stuff but not the tunnel endpoint. The onliest firewall is the windows firewall.
Sorry it is dutch, but I dont have an english version available.
Some information:
C:\Windows\system32>netsh int ipv6 show address
Interface 1: Loopback Pseudo-Interface 1
Adrestype DAD-status Geldig Voorkeur Adres
--------- ----------- ---------- ---------- ------------------------
Overig Voorkeur infinite infinite ::1
Interface 13: Draadloze netwerkverbinding 2
Adrestype DAD-status Geldig Voorkeur Adres
--------- ----------- ---------- ---------- ------------------------
Overig Afgeschaft infinite infinite fe80::9c24:135c:e281:76c0%13
Interface 9: LAN-verbinding
Adrestype DAD-status Geldig Voorkeur Adres
--------- ----------- ---------- ---------- ------------------------
Handmatig Voorkeur infinite infinite 2002:81a8:102::
Overig Voorkeur infinite infinite fe80::cdba:13de:5b5b:679c%9
Interface 26: LAN-verbinding* 14
Adrestype DAD-status Geldig Voorkeur Adres
--------- ----------- ---------- ---------- ------------------------
Openbaar Voorkeur infinite infinite 2001:0:d5c7:a2d6:2c88:16f6:3f57:fef
4
Overig Voorkeur infinite infinite fe80::2c88:16f6:3f57:fef4%26
Interface 12: Bluetooth-netwerkverbinding
Adrestype DAD-status Geldig Voorkeur Adres
--------- ----------- ---------- ---------- ------------------------
Overig Afgeschaft infinite infinite fe80::15ad:9473:8baa:c42d%12
Interface 31: aiccu
Adrestype DAD-status Geldig Voorkeur Adres
--------- ----------- ---------- ---------- ------------------------
Overig Voorkeur infinite infinite fe80::ec64:1393:a216:ab00%31
C:\Windows\system32>netsh int ipv6 show routes
De volgende opdracht is niet gevonden: int ipv6 show routes.
C:\Windows\system32>netsh int ipv6 show route
Public. Type Met Voorvoegsel Idx Naam gateway/interface
------- -------- --- ------------------------ --- ------------------------
Nee Handmatig 256 ::1/128 1 Loopback Pseudo-Interface
1
Nee Handmatig 8 2001::/32 26 LAN-verbinding* 14
Nee Handmatig 256 2001:0:d5c7:a2d6:2c88:16f6:3f57:fef4/128 26 LAN-verbi
nding* 14
Nee Handmatig 256 2002:81a8:102::/64 9 LAN-verbinding
Nee Handmatig 256 2002:81a8:102::/128 9 LAN-verbinding
Nee Handmatig 256 fe80::/64 31 aiccu
Nee Handmatig 256 fe80::/64 9 LAN-verbinding
Nee Handmatig 256 fe80::/64 12 Bluetooth-netwerkverbindi
ng
Nee Handmatig 256 fe80::/64 13 Draadloze netwerkverbindi
ng 2
Nee Handmatig 256 fe80::/64 26 LAN-verbinding* 14
Nee Handmatig 256 fe80::15ad:9473:8baa:c42d/128 12 Bluetooth-netwerkver
binding
Nee Handmatig 256 fe80::2c88:16f6:3f57:fef4/128 26 LAN-verbinding* 14
Nee Handmatig 256 fe80::9c24:135c:e281:76c0/128 13 Draadloze netwerkver
binding 2
Nee Handmatig 256 fe80::cdba:13de:5b5b:679c/128 9 LAN-verbinding
Nee Handmatig 256 fe80::ec64:1393:a216:ab00/128 31 aiccu
Nee Handmatig 256 ff00::/8 1 Loopback Pseudo-Interface
1
Nee Handmatig 256 ff00::/8 26 LAN-verbinding* 14
Nee Handmatig 256 ff00::/8 31 aiccu
Nee Handmatig 256 ff00::/8 9 LAN-verbinding
Nee Handmatig 256 ff00::/8 12 Bluetooth-netwerkverbindi
ng
Nee Handmatig 256 ff00::/8 13 Draadloze netwerkverbindi
ng 2
C:\Windows\system32>ipconfig /all
Windows IP-configuratie
Hostnaam . . . . . . . . . . . . : laptop-julius
Primair DNS-achtervoegsel . . . . :
Knooppunttype . . . . . . . . . . : gemengd
IP-routering ingeschakeld . . . . : nee
WINS-proxy ingeschakeld . . . . . : nee
Ethernet-adapter aiccu:
Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : TAP-Win32 Adapter V9
Fysiek adres. . . . . . . . . . . : 00-FF-DB-AB-41-79
DHCP ingeschakeld . . . . . . . . : ja
Autom. configuratie ingeschakeld : ja
Link-local IPv6-adres . . . . . . : fe80::ec64:1393:a216:ab00%31(voorkeur)
Automatisch geconf.IPv4-adres . . : 169.254.171.0(voorkeur)
Subnetmasker. . . . . . . . . . . : 255.255.0.0
Standaardgateway. . . . . . . . . :
DNS-servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS via TCPIP . . . . . . . . : ingeschakeld
Ethernet-adapter Bluetooth-netwerkverbinding:
Mediumstatus. . . . . . . . . . . : medium ontkoppeld
Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : Bluetooth-apparaat (Personal Area Network
)
Fysiek adres. . . . . . . . . . . : 00-1A-92-79-F7-99
DHCP ingeschakeld . . . . . . . . : ja
Autom. configuratie ingeschakeld : ja
Ethernet-adapter LAN-verbinding:
Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : Realtek RTL8168/8111 Family PCI-E Gigabit
Ethernet NIC (NDIS 6.0)
Fysiek adres. . . . . . . . . . . : 00-1A-92-CE-EA-70
DHCP ingeschakeld . . . . . . . . : ja
Autom. configuratie ingeschakeld : ja
IPv6-adres. . . . . . . . . . . . : 2002:81a8:102::(voorkeur)
Link-local IPv6-adres . . . . . . : fe80::cdba:13de:5b5b:679c%9(voorkeur)
IPv4-adres. . . . . . . . . . . . : 192.168.1.11(voorkeur)
Subnetmasker. . . . . . . . . . . : 255.255.255.0
Lease verkregen . . . . . . . . . : dinsdag 18 augustus 2009 15:54:07
Lease verlopen. . . . . . . . . . : vrijdag 21 augustus 2009 15:54:06
Standaardgateway. . . . . . . . . : 192.168.1.1
DHCP-server . . . . . . . . . . . : 192.168.1.1
DNS-servers . . . . . . . . . . . : 192.168.1.1
NetBIOS via TCPIP . . . . . . . . : ingeschakeld
Adapter voor draadloos LAN Draadloze netwerkverbinding 2:
Mediumstatus. . . . . . . . . . . : medium ontkoppeld
Verbindingsspec. DNS-achtervoegsel: SpeedNet
Beschrijving. . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Con
nection #2
Fysiek adres. . . . . . . . . . . : 00-18-DE-C6-E9-D5
DHCP ingeschakeld . . . . . . . . : ja
Autom. configuratie ingeschakeld : ja
Tunnel-adapter LAN-verbinding* 7:
Mediumstatus. . . . . . . . . . . : medium ontkoppeld
Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : isatap.{BE61D58C-DCB8-4576-9595-3365A41C3
72E}
Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP ingeschakeld . . . . . . . . : nee
Autom. configuratie ingeschakeld : ja
Tunnel-adapter LAN-verbinding* 14:
Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Fysiek adres. . . . . . . . . . . : 02-00-54-55-4E-01
DHCP ingeschakeld . . . . . . . . : nee
Autom. configuratie ingeschakeld : ja
IPv6-adres. . . . . . . . . . . . : 2001:0:d5c7:a2d6:2c88:16f6:3f57:fef4(voor
keur)
Link-local IPv6-adres . . . . . . : fe80::2c88:16f6:3f57:fef4%26(voorkeur)
Standaardgateway. . . . . . . . . :
NetBIOS via TCPIP . . . . . . . . : uitgeschakeld
Tunnel-adapter LAN-verbinding* 23:
Mediumstatus. . . . . . . . . . . : medium ontkoppeld
Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : isatap.home.nl
Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP ingeschakeld . . . . . . . . : nee
Autom. configuratie ingeschakeld : ja
weird problem in vista
Shadow Hawkins on Tuesday, 18 August 2009 19:22:43
You still have the Teredo adapter active:
Tunnel-adapter LAN-verbinding* 14:
Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Fysiek adres. . . . . . . . . . . : 02-00-54-55-4E-01
DHCP ingeschakeld . . . . . . . . : nee
Autom. configuratie ingeschakeld : ja
IPv6-adres. . . . . . . . . . . . : 2001:0:d5c7:a2d6:2c88:16f6:3f57:fef4(voor
keur)
And it is shown as route:
Nee Handmatig 8 2001::/32 26 LAN-verbinding* 14
Nee Handmatig 256 2001:0:d5c7:a2d6:2c88:16f6:3f57:fef4/128 26 LAN-verbi
nding* 14
According to the same Wiki article, you have to disable it.
|
![[ch]](/s/countries/ch.gif)
on Monday, 17 August 2009 23:28:20
Posting is only allowed when you are