A problem with win2k3 ipv6 setup
Carmen Sandiego on Tuesday, 13 April 2004 11:13:06
Hello. I havew a problem with my tunnel on a win2003 server. I have used the script but I cannot use v6. I can ping my v6 but nothing other. this is my configuration:
netsh interface ipv6 show interface
Querying active state...
Idx Met MTU State Name
--- ---- ----- ------------ -----
19 1 1280 Disconnected SixXS
4 0 1500 Connected Local Area Connection 2
3 1 1280 Connected 6to4 Pseudo-Interface
2 1 1280 Connected Automatic Tunneling Pseudo-Interface
1 0 1500 Connected Loopback Pseudo-Interface
netsh interface ipv6 show neigh
Interface 19: SixXS
Internet Address Physical Address Type
--------------------------------------------- ----------------- -----------
2001:838:1:1:210:dcff:fe20:7c7c 62.24.229.120 Permanent
fe80::13:5230:e903 82.48.233.3 Permanent
3ffe:4005:1000:20::2 82.48.233.3 Permanent
Interface 4: Local Area Connection 2
Internet Address Physical Address Type
--------------------------------------------- ----------------- -----------
fe80::2e0:4cff:fea8:1bef 00-e0-4c-a8-1b-ef Permanent
2002:c0a8:1432:4:2e0:4cff:fea8:1bef 00-e0-4c-a8-1b-ef Permanent
fec0::4:2e0:4cff:fea8:1bef 00-e0-4c-a8-1b-ef Permanent
fe80::20c:6eff:fec9:4f93 00-0c-6e-c9-4f-93 Stale
fec0::4:20c:6eff:fec9:4f93 00-0c-6e-c9-4f-93 Stale (router
2001:6f8:900:1d3::2 Unreachable Incomplete
2001:6b8:0:700::1 Unreachable Incomplete
2001:838:1:1:210:dcff:fe20:7c7c Unreachable Incomplete
fec0:0:0:ffff::3 Unreachable Incomplete
fec0:0:0:ffff::2 Unreachable Incomplete
fec0:0:0:ffff::1 Unreachable Incomplete
Interface 2: Automatic Tunneling Pseudo-Interface
Internet Address Physical Address Type
--------------------------------------------- ----------------- -----------
fe80::5efe:192.168.20.1 127.0.0.1 Permanent
Interface 1: Loopback Pseudo-Interface
Internet Address Physical Address Type
--------------------------------------------- ----------------- -----------
fe80::1 Permanent
::1 Permanent
Thanks a lot for the help.
A problem with win2k3 ipv6 setup
Shadow Hawkins on Tuesday, 13 April 2004 12:13:15 19 1 1280 Disconnected SixXS
disconnected says enough :)
you should use this script to get eveything working (works for me)
at least as far I can figure out from what you posted here
netsh interface ipv6 reset
netsh interface ipv6 add v6v4tunnel SixXS 82.48.233.3 62.24.229.120
netsh interface ipv6 add address SixXS 3ffe:4005:1000:20::2
netsh interface ipv6 add route 3ffe:4005:1000:20::2/127 SixXS
netsh interface ipv6 add route 0::/0 SixXS
netsh firewall set adapter SixXS icmp all=enable
A problem with win2k3 ipv6 setup
Carmen Sandiego on Tuesday, 13 April 2004 12:24:47
Yes, I use this script, but it don't work.. and I've tried on two 2003 server, but the result is the same. I don't know why the sixx's interface is disconnected..
thanks a lot.
A problem with win2k3 ipv6 setup
Shadow Hawkins on Tuesday, 13 April 2004 13:29:29
Do you have a Firewall running somewhere? or a NAT box?
Cause you have to get Protocol 41 to the Win2k3 machine (not to be confuced with UDP / TCP port 41)
Posting is only allowed when you are logged in. |