Results 1 to 9 of 9

Thread: Windows Client over IPv6

  1. #1
    Join Date
    Oct 2011
    Posts
    17

    Default Windows Client over IPv6

    I have a (partially complete) dual-stack IPv4/IPv6 network. My Amanda server host and some of my Windows client hosts are IPv6 enabled.

    The ZWC Windows service doesn't seem to listen for IPv6 connections though, and I can't find out how to make it.

    It is only listening on IPv4:
    Code:
    C:\  netstat -a | findstr 10080
      TCP    0.0.0.0:10080          svr-addc-01:0          LISTENING
    How do I enable it on IPv6?

    Not being able to use IPv6 slows down my amcheck and amdump processes since the server attempts to talk IPv6 first, but waits for that to time-out before falling back to IPv4 (which does work).

  2. #2
    Join Date
    May 2009
    Posts
    82

    Default

    That's a good question.

    Every time I've tried to use V6 for something (never ZWC) I've had to shutdown the V4. I think there is a tunneling protocol enabled somewhere that causes this and I'm pretty sure V4 is set to take preference. I wonder what your ipconfig /all looks like?

  3. #3
    Join Date
    Oct 2011
    Posts
    17

    Default

    Sorry for the slow reply; it was a public holiday here yesterday
    Quote Originally Posted by jfarschman View Post
    Every time I've tried to use V6 for something (never ZWC) I've had to shutdown the V4.
    There (should) be no reason a service can't listen for both, either by binding twice (to inet and inet6) or just by binding to * instead of 0.0.0.0 or ::

    Quote Originally Posted by jfarschman View Post
    I think there is a tunneling protocol enabled somewhere that causes this and I'm pretty sure V4 is set to take preference.
    Teredo is on Windows by default these days, but shouldn't impact anything to do with Native IPv6. As I said, IPv6 is working fine for other things (eg, Active Directory and Email traffic).

    Quote Originally Posted by jfarschman View Post
    I wonder what your ipconfig /all looks like?
    Code:
    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : svr-addc-01
       Primary Dns Suffix  . . . . . . . : mydomain.local
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : Yes
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : mydomain.local
    
    Ethernet adapter LAN:
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : LAN
       Physical Address. . . . . . . . . : B4-99-BA-AB-10-AE
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:44b8:4126:xxxx:0:bbbb:addc:1(Preferred)
       Link-local IPv6 Address . . . . . : fe80::181e:9509:96f3:c270%15(Preferred)
       IPv4 Address. . . . . . . . . . . : 172.31.1.11(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 2001:44b8:4126:xxxx::f0
                                           172.31.1.1
       DHCPv6 IAID . . . . . . . . . . . : 397711802
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-E5-70-98-B4-99-BA-AB-10-AE
       DNS Servers . . . . . . . . . . . : 2001:44b8:4126:xxxx::f1
                                           2001:44b8:4126:xxxx::f2
                                           172.31.1.11
                                           192.168.1.10
                                           172.31.1.1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Tunnel adapter isatap.{A3A96E64-2B1D-4176-8AB8-C1EF133C7691}:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    
    Tunnel adapter Teredo Tunneling Pseudo-Interface:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

  4. #4
    Join Date
    May 2009
    Posts
    82

    Default

    Well, it seems like Fukawi has IPV6 working on both systems, but the ZWC services doesn't seem to have the ability to work on V6.

    Is that correct?

    If true you may wait until someone from Zmanda take a peek at the forums here.

  5. #5
    Join Date
    Oct 2011
    Posts
    17

    Default

    Quote Originally Posted by jfarschman View Post
    Well, it seems like Fukawi has IPV6 working on both systems, but the ZWC services doesn't seem to have the ability to work on V6.

    Is that correct?
    Spot on

  6. #6
    Join Date
    Sep 2008
    Posts
    112

    Default

    Hi,
    When you say that ZWCService does not work with IPv6, what exactly happens? Does the host check from Amanda server fail?

    Can you try the following workaround to see if the host check works:
    1. Open registry using regedit.exe.
    2. Go to HKLM\Software\Zmanda\ZWC\1.0\Install
    3. Edit the key 'Servers' and add the Amanda server name along with its IP using comma separated format.

    Regards,
    Prashant

  7. #7
    Join Date
    Oct 2011
    Posts
    17

    Default

    Quote Originally Posted by prashant View Post
    When you say that ZWCService does not work with IPv6, what exactly happens? Does the host check from Amanda server fail?
    Thanks to taking the time to reply
    As I mentioned in my OP, the ZWC service does not even listen for IPv6 connections. It only binds to the IPv4 "all addresses" address:
    Code:
    C:\  netstat -a | findstr 10080
      TCP    0.0.0.0:10080          svr-addc-01:0          LISTENING
    IF it was listening on IPv6 properly, there should be an entry in netstat like this:
    Code:
      TCP    [::]:10080          svr-addc-01:0          LISTENING
    Quote Originally Posted by prashant View Post
    Can you try the following workaround to see if the host check works:
    1. Open registry using regedit.exe.
    2. Go to HKLM\Software\Zmanda\ZWC\1.0\Install
    3. Edit the key 'Servers' and add the Amanda server name along with its IP using comma separated format.
    This makes no difference.

  8. #8
    Join Date
    Sep 2008
    Posts
    112

    Default

    Hi,
    I tested this in our environment and a check host did not work. Yes, you are right ZWC does not listen on IPv6. I have filed an enhancement bug and it will be fixed in the upcoming release. Meanwhile, you will have to IPv4 connection to backup a ZWC machine.

    Thank you for finding this out. :-)

    Regards,
    Prashant

  9. #9
    Join Date
    Oct 2011
    Posts
    17

    Default

    Quote Originally Posted by prashant View Post
    Yes, you are right ZWC does not listen on IPv6. I have filed an enhancement bug and it will be fixed in the upcoming release.
    I'm glad it's not just me or something I broke

    Quote Originally Posted by prashant View Post
    Thank you for finding this out. :-)
    Thank you for being so responsive in getting it fixed

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •