How to have Windows 10 server connect on IPv6 address

Forums / NoMachine for Windows / How to have Windows 10 server connect on IPv6 address

Tagged: 

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #10597
    panluowei
    Participant

    Hi,

    I have a dual stack (IPv4 and IPv6) Windows 10 NoMachine Server. Clients can connect fine to NX:, but not the ipv6 address. Is there something special that needs configuring on the server?

    BTW, this works fine with a Linux NoMachine Server (i.e. clients can connect to NX:, NX:, SSH:, and SSH: with no problem.

    With firewall disabled an “nmap” shows the Windows 10 only listening on the ipv4 ports, and the linux system listening on both (see below). How do I get the Windows 10 to listen on the ipv6 address?

    thanks

    ———– windows 10 ipv4 and ipv6 nmaps ———————-

    $ nmap

    Starting Nmap 6.40 ( http://nmap.org ) at 2016-03-16 15:44 EDT

    Nmap scan report for ()

    Host is up (0.00087s latency).

    Not shown: 996 closed ports

    PORT STATE SERVICE

    135/tcp open msrpc

    3389/tcp open ms-wbt-server

    4000/tcp open remoteanything

    5357/tcp open wsdapi

    $ nmap -6

    Starting Nmap 6.40 ( http://nmap.org ) at 2016-03-16 15:43 EDT

    Nmap scan report for

    Host is up (0.080s latency).

    All 1000 scanned ports on are filtered

    ———– linux ipv4 and ipv6 nmaps ——————————

    $ nmap

    Starting Nmap 6.40 ( http://nmap.org ) at 2016-03-16 15:44 EDT

    Nmap scan report for ()

    Host is up (0.00040s latency).

    Not shown: 996 closed ports

    PORT STATE SERVICE

    22/tcp open ssh

    4000/tcp open remoteanything

    5800/tcp open vnc-http

    5900/tcp open vnc

    Nmap done: 1 IP address (1 host up) scanned in 0.08 seconds

    $ nmap -6

    Starting Nmap 6.40 ( http://nmap.org ) at 2016-03-16 15:44 EDT

    Nmap scan report for

    Host is up (0.00063s latency).

    Not shown: 996 closed ports

    PORT STATE SERVICE

    22/tcp open ssh

    4000/tcp open remoteanything

    5800/tcp open vnc-http

    5900/tcp open vnc

    #10608
    panluowei
    Participant

    After troubleshooting, I don’t think this is a NoMachine configuration question. I think it is a Windows 10 ipv6 dns lookup issue.

    #10618
    kroy
    Contributor

    We couldn’t reproduce such problem in our lab. It’s possible that is system configuration issue. Can you run debug, reproduce problem and send to forum[at]nomachine[dot]com? You can find instructions about collecting logs here: https://www.nomachine.com/DT04M00076.

Viewing 3 posts - 1 through 3 (of 3 total)

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.