Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Pages: [1] 2

Author Topic: IPv6 problem on Windows Server 2008  (Read 13471 times)

Vortiago

  • Newbie
  • *
  • Posts: 6
IPv6 problem on Windows Server 2008
« on: May 27, 2010, 11:54:02 AM »

Right, here's the problem.

I have a tunnel set up on a win2k8 machine, every other machine on the network gets a IPv6 from it and can access ipv6-sites and can also access them by their ipv6-address from another f.ex school.

The problem is that even though all other machines on the network get an address, the win2k8-machine can't access ipv6-sites and can't be pinged either. I find this realy strange and no matter my debugging I can't seem to find out what's wrong. So, anyone experienced anything similar? Any commands / info i should post here so you can give me more help?.
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2714
Re: IPv6 problem on Windows Server 2008
« Reply #1 on: May 27, 2010, 11:56:31 AM »

Unless you've allowed IPv6 ping through the firewall, you won't be able to ping the server...Ping replies are blocked by default.

To turn on, look in "Windows Firewall with advanced settings" or something like that
Logged

Vortiago

  • Newbie
  • *
  • Posts: 6
Re: IPv6 problem on Windows Server 2008
« Reply #2 on: May 27, 2010, 04:36:51 PM »

IPv6 pings should be allowed, the rule in the firewall is set to allow at least.

And ping isn't the 'main' problem. I don't realy care if I can ping it or not, i just wan't it to be able to browse other ipv6-enabled websites and be able to access it by ipv6.
Logged

jimb

  • Hero Member
  • *****
  • Posts: 805
  • ^^^ Warped picture
Re: IPv6 problem on Windows Server 2008
« Reply #3 on: May 27, 2010, 06:47:33 PM »

Not sure what's going on here, but in a similar suggestion to cholz's, check your firewall rules to make sure that they aren't blocking access out by the tunnel router itself while allowing traffic from your LAN hosts to pass.

Not sure what else it could be.  Does http://ipv6.whatismyv6.com/ work for you on that machine?
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2714
Re: IPv6 problem on Windows Server 2008
« Reply #4 on: May 27, 2010, 06:59:17 PM »

And if that site doesn't work it would help if you would post routing tables and the output of ipconfig \all
Logged

Vortiago

  • Newbie
  • *
  • Posts: 6
Re: IPv6 problem on Windows Server 2008
« Reply #5 on: May 28, 2010, 01:33:49 AM »

The website didn't work, so here's some output:

'ipconfig /all':
Code: [Select]
Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : NETGEAR WG311v3 54Mbps Wireless PCI Adapter
   Physical Address. . . . . . . . . : 00-1E-2A-B5-23-D7
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:470:27:19f::(Preferred)
   IPv6 Address. . . . . . . . . . . : 2001:470:27:19f::1(Preferred)
   IPv6 Address. . . . . . . . . . . : 2001:470:27:19f:4064:6c80:90db:f064(Preferred)
   IPv6 Address. . . . . . . . . . . : 2001:470:28:19f:4064:6c80:90db:f064(Preferred)
   Link-local IPv6 Address . . . . . : fe80::4064:6c80:90db:f064%12(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.10(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1
   DNS Servers . . . . . . . . . . . : 127.0.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : SiS 900-Based PCI Fast Ethernet Adapter
   Physical Address. . . . . . . . . : 00-0C-76-BC-5E-AC
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 8:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{B015812A-3B43-40E2-A668-ABF3F83F894F}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::5efe:192.168.1.10%13(Preferred)
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 127.0.0.1
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 9:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter IP6Tunnel:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:470:27:19f::2(Preferred)
   Link-local IPv6 Address . . . . . : fe80::ac18:cd95:c2cd:c7e%15(Preferred)
   Default Gateway . . . . . . . . . : 2001:470:27:19f::1
   DNS Servers . . . . . . . . . . . : 127.0.0.1
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 13:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{3E24FDE3-C98D-4846-92B6-3FBE6AFCA709}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::5efe:169.254.75.122%14(Preferred)
   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. . . . . . . . : Disabled

'route print':
Code: [Select]
===========================================================================
Interface List
 12 ...00 1e 2a b5 23 d7 ...... NETGEAR WG311v3 54Mbps Wireless PCI Adapter
 10 ...00 0c 76 bc 5e ac ...... SiS 900-Based PCI Fast Ethernet Adapter
  1 ........................... Software Loopback Interface 1
 13 ...00 00 00 00 00 00 00 e0  isatap.{B015812A-3B43-40E2-A668-ABF3F83F894F}
 11 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
 15 ...00 00 00 00 00 00 00 e0  Microsoft Direct Point-to-point Adapater
 14 ...00 00 00 00 00 00 00 e0  isatap.{3E24FDE3-C98D-4846-92B6-3FBE6AFCA709}
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1     192.168.1.10    281
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      192.168.1.0    255.255.255.0         On-link      192.168.1.10    281
     192.168.1.10  255.255.255.255         On-link      192.168.1.10    281
    192.168.1.255  255.255.255.255         On-link      192.168.1.10    281
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link      192.168.1.10    281
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link      192.168.1.10    281
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
          0.0.0.0          0.0.0.0      192.168.1.1  Default
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
 15    261 ::/0                     2001:470:27:19f::1
  1    306 ::1/128                  On-link
 15    261 2001:470:27:19f::/64     On-link
 12    281 2001:470:27:19f::/64     On-link
 12    281 2001:470:27:19f::/128    On-link
 12    281 2001:470:27:19f::1/128   On-link
 15    261 2001:470:27:19f::2/128   On-link
 12    281 2001:470:27:19f:4064:6c80:90db:f064/128
                                    On-link
 12    281 2001:470:28:19f::/64     On-link
 12    281 2001:470:28:19f::/128    On-link
 12    281 2001:470:28:19f:4064:6c80:90db:f064/128
                                    On-link
 15    261 fe80::/64                On-link
 12    281 fe80::/64                On-link
 14    266 fe80::5efe:169.254.75.122/128
                                    On-link
 13    286 fe80::5efe:192.168.1.10/128
                                    On-link
 12    281 fe80::4064:6c80:90db:f064/128
                                    On-link
 15    261 fe80::ac18:cd95:c2cd:c7e/128
                                    On-link
  1    306 ff00::/8                 On-link
 15    261 ff00::/8                 On-link
 12    281 ff00::/8                 On-link
===========================================================================
Persistent Routes:
 If Metric Network Destination      Gateway
  0 4294967295 ::/0                     2001:470:27:19f::1
  0 4294967295 2001:470:28:19f::/64     On-link
  0 4294967295 2001:470:27:19f::/64     On-link
===========================================================================
Logged

jimb

  • Hero Member
  • *****
  • Posts: 805
  • ^^^ Warped picture
Re: IPv6 problem on Windows Server 2008
« Reply #6 on: May 28, 2010, 02:07:41 AM »

It looks to me like you have the wrong IPv6 addresses on your LAN interface, which appears to be a wifi adapter.  Make sure you're using your routed /64 on the internal LAN interface, and the client IPv6 address on your tunnel interface.

It appears you have address or static routes for 2001:470:27:19f::/64 on both your tunnel and the wireless interface.  That's just wrong.  :P
« Last Edit: May 28, 2010, 02:11:37 AM by jimb »
Logged

Vortiago

  • Newbie
  • *
  • Posts: 6
Re: IPv6 problem on Windows Server 2008
« Reply #7 on: May 28, 2010, 05:00:30 AM »

Well, managed to get it to work on the local network (Can now ping and access local machines by their ipv6 address).
But the external network is still not responding.

IPv6 Route Table:
Code: [Select]
IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
 13      6 ::/0                     2001:470:27:19f::1
  1    306 ::1/128                  On-link
 13    261 2001:470:27:19f::/64     On-link
 13    261 2001:470:27:19f::2/128   On-link
 12    281 2001:470:28:19f::/64     On-link
 12    281 2001:470:28:19f::1/128   On-link
 12    281 2001:470:28:19f:4064:6c80:90db:f064/128
                                    On-link
 13    261 fe80::/64                On-link
 12    281 fe80::/64                On-link
 13    261 fe80::41d:511a:562:65d7/128
                                    On-link
 12    281 fe80::4064:6c80:90db:f064/128
                                    On-link
  1    306 ff00::/8                 On-link
 13    261 ff00::/8                 On-link
 12    281 ff00::/8                 On-link
===========================================================================
Persistent Routes:
 If Metric Network Destination      Gateway
  0 4294967295 2001:470:28:19f::/64     On-link
===========================================================================

Ping ipv6.google.com:
Code: [Select]
Pinging ipv6.l.google.com [2a00:1450:8003::67] from 2001:470:27:19f::2 with 32 bytes of data:
Request timed out.
Request timed out.

Netsh show address:
Code: [Select]
Interface 12: Wireless Network Connection

Addr Type  DAD State   Valid Life Pref. Life Address
---------  ----------- ---------- ---------- ------------------------
Manual     Preferred     infinite   infinite 2001:470:28:19f::1
Public     Preferred     infinite   infinite 2001:470:28:19f:4064:6c80:90db:f064
Other      Preferred     infinite   infinite fe80::4064:6c80:90db:f064%12

Interface 11: Local Area Connection* 9

Addr Type  DAD State   Valid Life Pref. Life Address
---------  ----------- ---------- ---------- ------------------------
Other      Deprecated    infinite   infinite fe80::100:7f:fffe%11

Interface 13: Tunnelbroker

Addr Type  DAD State   Valid Life Pref. Life Address
---------  ----------- ---------- ---------- ------------------------
Manual     Preferred     infinite   infinite 2001:470:27:19f::2
Other      Preferred     infinite   infinite fe80::41d:511a:562:65d7%13

Interface 10: Local Area Connection

Addr Type  DAD State   Valid Life Pref. Life Address
---------  ----------- ---------- ---------- ------------------------
Other      Deprecated    infinite   infinite fe80::683a:29e:1d48:4b7a%10

Interface 12: Wireless Network Connection

Addr Type  DAD State   Valid Life Pref. Life Address
---------  ----------- ---------- ---------- ------------------------
Anycast    Preferred     infinite   infinite 2001:470:28:19f::

So close, yet so far away :/
Logged

jimb

  • Hero Member
  • *****
  • Posts: 805
  • ^^^ Warped picture
Re: IPv6 problem on Windows Server 2008
« Reply #8 on: May 28, 2010, 05:04:25 PM »

Do you have forwarding and publish set for the addresses?  There was another thread that had basically cookbook on how to set this stuff up on a Windows box.  May wanna search for it.
Logged

Vortiago

  • Newbie
  • *
  • Posts: 6
Re: IPv6 problem on Windows Server 2008
« Reply #9 on: May 29, 2010, 02:29:27 PM »

It was that post I followed.

Gave up having the win-box set up as the ipv6-router and went back to having it on my dd-wrt box.

The reason I went away from having it like that was the fact that my win2k8 box won't autoconfigure itself into having a ipv6 address, and now I'm back to that :(

Seriously strange stuff going around.
Logged

jimb

  • Hero Member
  • *****
  • Posts: 805
  • ^^^ Warped picture
Re: IPv6 problem on Windows Server 2008
« Reply #10 on: May 30, 2010, 03:37:18 PM »

That's odd.  Maybe a peculiarity of win2k8?  All my windows boxes autoconfig just fine.  XP, Win7, etc.  I'm almost sure there have been other Win2k8 users who have used it and autoconfed just fine too.  Maybe there's a bit you have to flip in 2k8 to make it happen?

I was actually looking for a netsh command to turn OFF autoconfig in XP that I could have sworn I saw before, but couldn't find when I looked for it.  :)
Logged

Vortiago

  • Newbie
  • *
  • Posts: 6
Re: IPv6 problem on Windows Server 2008
« Reply #11 on: May 30, 2010, 03:49:57 PM »

Ye, been looking around to see if I could find anything like that but to no avail :/

I've now set a ipv6 address manually, but that also got its quirks. When I set it manually I can ping and access other ipv6-resources like ipv6.google.com. But no one can ping my machine or get access to the services running on it. (This is even true when I completely disable the windows firewall, what an odd OS) When I try to ping it I get met with a 'Destination host unreachable.'.
Logged

jimb

  • Hero Member
  • *****
  • Posts: 805
  • ^^^ Warped picture
Re: IPv6 problem on Windows Server 2008
« Reply #12 on: May 30, 2010, 03:56:10 PM »

That is verrry odd.  All I can say is look closely at all your settings and make sure you didn't fat-finger something.  :P
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2714
Re: IPv6 problem on Windows Server 2008
« Reply #13 on: May 30, 2010, 05:59:50 PM »

well, all i can say is that both server 2008 and server 2008 r2 are set for autoconfig right out of the box
Logged

armanjackson

  • readonly_member
  • Newbie
  • *
  • Posts: 3
Re: IPv6 problem on Windows Server 2008
« Reply #14 on: June 17, 2010, 06:11:11 AM »

I'm not understand whats going on .You have to check your firewall setting and IP address. Also check your IPv6 ping should be allowed.
Logged
Pages: [1] 2