Tigervnc connection refused when using IP address, and accepted with 127.0.0.1












0















I am using Ubuntu 18.04 LTS. I performed an apt get tigervnc-standalone-server adn tigervnc-common. I am using an xstartup from another host that is running the same setup. When I attempt to connect to the box with the tigervnc client, I get a connection refused 61 message. If go directly on the box and attempt to vncviewer 10.207.0.201:5901 I also get a connection refused message, BUT if I do a vncviewer 127.0.0.1:5901, I can connect. Here is some back ground information.



richmaes@portal01:~$ nmap localhost

Starting Nmap 7.60 ( https://nmap.org ) at 2019-02-07 17:33 PST
Nmap scan report for localhost (127.0.0.1)
Host is up (0.000040s latency).
Not shown: 995 closed ports
PORT STATE SERVICE
22/tcp open ssh
139/tcp open netbios-ssn
445/tcp open microsoft-ds
631/tcp open ipp
5901/tcp open vnc-1

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


AND then interestingly enough (my eyes pop out of my head) because 5901 is there if I use the home address but not if I use its static address.



richmaes@portal01:~$ nmap 10.207.0.102

Starting Nmap 7.60 ( https://nmap.org ) at 2019-02-07 17:42 PST
Nmap scan report for portal01 (10.207.0.102)
Host is up (0.000051s latency).
Not shown: 997 closed ports
PORT STATE SERVICE
22/tcp open ssh
139/tcp open netbios-ssn
445/tcp open microsoft-ds


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



And I confirm that I am really know what my local IP is.



richmaes@portal01:~$ ifconfig -a
enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.207.0.102 netmask 255.255.255.0 broadcast 10.207.0.255
inet6 fe80::56bf:64ff:fe63:43d0 prefixlen 64 scopeid 0x20<link>
ether 54:bf:64:63:43:d0 txqueuelen 1000 (Ethernet)
RX packets 4295 bytes 3015163 (3.0 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1526 bytes 150636 (150.6 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xef180000-ef1a0000


vncserver is listening on port 5901 according to nmap relative to home address only. I have checked that there are not rules in iptables or ufw. What is happening here?



richmaes@portal01:~$ sudo iptables --list
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination


And the Firewall



richmaes@portal01:~$ sudo ufw status verbose
Status: inactive









share|improve this question



























    0















    I am using Ubuntu 18.04 LTS. I performed an apt get tigervnc-standalone-server adn tigervnc-common. I am using an xstartup from another host that is running the same setup. When I attempt to connect to the box with the tigervnc client, I get a connection refused 61 message. If go directly on the box and attempt to vncviewer 10.207.0.201:5901 I also get a connection refused message, BUT if I do a vncviewer 127.0.0.1:5901, I can connect. Here is some back ground information.



    richmaes@portal01:~$ nmap localhost

    Starting Nmap 7.60 ( https://nmap.org ) at 2019-02-07 17:33 PST
    Nmap scan report for localhost (127.0.0.1)
    Host is up (0.000040s latency).
    Not shown: 995 closed ports
    PORT STATE SERVICE
    22/tcp open ssh
    139/tcp open netbios-ssn
    445/tcp open microsoft-ds
    631/tcp open ipp
    5901/tcp open vnc-1

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


    AND then interestingly enough (my eyes pop out of my head) because 5901 is there if I use the home address but not if I use its static address.



    richmaes@portal01:~$ nmap 10.207.0.102

    Starting Nmap 7.60 ( https://nmap.org ) at 2019-02-07 17:42 PST
    Nmap scan report for portal01 (10.207.0.102)
    Host is up (0.000051s latency).
    Not shown: 997 closed ports
    PORT STATE SERVICE
    22/tcp open ssh
    139/tcp open netbios-ssn
    445/tcp open microsoft-ds


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



    And I confirm that I am really know what my local IP is.



    richmaes@portal01:~$ ifconfig -a
    enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 10.207.0.102 netmask 255.255.255.0 broadcast 10.207.0.255
    inet6 fe80::56bf:64ff:fe63:43d0 prefixlen 64 scopeid 0x20<link>
    ether 54:bf:64:63:43:d0 txqueuelen 1000 (Ethernet)
    RX packets 4295 bytes 3015163 (3.0 MB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 1526 bytes 150636 (150.6 KB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    device interrupt 16 memory 0xef180000-ef1a0000


    vncserver is listening on port 5901 according to nmap relative to home address only. I have checked that there are not rules in iptables or ufw. What is happening here?



    richmaes@portal01:~$ sudo iptables --list
    Chain INPUT (policy ACCEPT)
    target prot opt source destination

    Chain FORWARD (policy ACCEPT)
    target prot opt source destination

    Chain OUTPUT (policy ACCEPT)
    target prot opt source destination


    And the Firewall



    richmaes@portal01:~$ sudo ufw status verbose
    Status: inactive









    share|improve this question

























      0












      0








      0








      I am using Ubuntu 18.04 LTS. I performed an apt get tigervnc-standalone-server adn tigervnc-common. I am using an xstartup from another host that is running the same setup. When I attempt to connect to the box with the tigervnc client, I get a connection refused 61 message. If go directly on the box and attempt to vncviewer 10.207.0.201:5901 I also get a connection refused message, BUT if I do a vncviewer 127.0.0.1:5901, I can connect. Here is some back ground information.



      richmaes@portal01:~$ nmap localhost

      Starting Nmap 7.60 ( https://nmap.org ) at 2019-02-07 17:33 PST
      Nmap scan report for localhost (127.0.0.1)
      Host is up (0.000040s latency).
      Not shown: 995 closed ports
      PORT STATE SERVICE
      22/tcp open ssh
      139/tcp open netbios-ssn
      445/tcp open microsoft-ds
      631/tcp open ipp
      5901/tcp open vnc-1

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


      AND then interestingly enough (my eyes pop out of my head) because 5901 is there if I use the home address but not if I use its static address.



      richmaes@portal01:~$ nmap 10.207.0.102

      Starting Nmap 7.60 ( https://nmap.org ) at 2019-02-07 17:42 PST
      Nmap scan report for portal01 (10.207.0.102)
      Host is up (0.000051s latency).
      Not shown: 997 closed ports
      PORT STATE SERVICE
      22/tcp open ssh
      139/tcp open netbios-ssn
      445/tcp open microsoft-ds


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



      And I confirm that I am really know what my local IP is.



      richmaes@portal01:~$ ifconfig -a
      enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
      inet 10.207.0.102 netmask 255.255.255.0 broadcast 10.207.0.255
      inet6 fe80::56bf:64ff:fe63:43d0 prefixlen 64 scopeid 0x20<link>
      ether 54:bf:64:63:43:d0 txqueuelen 1000 (Ethernet)
      RX packets 4295 bytes 3015163 (3.0 MB)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 1526 bytes 150636 (150.6 KB)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
      device interrupt 16 memory 0xef180000-ef1a0000


      vncserver is listening on port 5901 according to nmap relative to home address only. I have checked that there are not rules in iptables or ufw. What is happening here?



      richmaes@portal01:~$ sudo iptables --list
      Chain INPUT (policy ACCEPT)
      target prot opt source destination

      Chain FORWARD (policy ACCEPT)
      target prot opt source destination

      Chain OUTPUT (policy ACCEPT)
      target prot opt source destination


      And the Firewall



      richmaes@portal01:~$ sudo ufw status verbose
      Status: inactive









      share|improve this question














      I am using Ubuntu 18.04 LTS. I performed an apt get tigervnc-standalone-server adn tigervnc-common. I am using an xstartup from another host that is running the same setup. When I attempt to connect to the box with the tigervnc client, I get a connection refused 61 message. If go directly on the box and attempt to vncviewer 10.207.0.201:5901 I also get a connection refused message, BUT if I do a vncviewer 127.0.0.1:5901, I can connect. Here is some back ground information.



      richmaes@portal01:~$ nmap localhost

      Starting Nmap 7.60 ( https://nmap.org ) at 2019-02-07 17:33 PST
      Nmap scan report for localhost (127.0.0.1)
      Host is up (0.000040s latency).
      Not shown: 995 closed ports
      PORT STATE SERVICE
      22/tcp open ssh
      139/tcp open netbios-ssn
      445/tcp open microsoft-ds
      631/tcp open ipp
      5901/tcp open vnc-1

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


      AND then interestingly enough (my eyes pop out of my head) because 5901 is there if I use the home address but not if I use its static address.



      richmaes@portal01:~$ nmap 10.207.0.102

      Starting Nmap 7.60 ( https://nmap.org ) at 2019-02-07 17:42 PST
      Nmap scan report for portal01 (10.207.0.102)
      Host is up (0.000051s latency).
      Not shown: 997 closed ports
      PORT STATE SERVICE
      22/tcp open ssh
      139/tcp open netbios-ssn
      445/tcp open microsoft-ds


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



      And I confirm that I am really know what my local IP is.



      richmaes@portal01:~$ ifconfig -a
      enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
      inet 10.207.0.102 netmask 255.255.255.0 broadcast 10.207.0.255
      inet6 fe80::56bf:64ff:fe63:43d0 prefixlen 64 scopeid 0x20<link>
      ether 54:bf:64:63:43:d0 txqueuelen 1000 (Ethernet)
      RX packets 4295 bytes 3015163 (3.0 MB)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 1526 bytes 150636 (150.6 KB)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
      device interrupt 16 memory 0xef180000-ef1a0000


      vncserver is listening on port 5901 according to nmap relative to home address only. I have checked that there are not rules in iptables or ufw. What is happening here?



      richmaes@portal01:~$ sudo iptables --list
      Chain INPUT (policy ACCEPT)
      target prot opt source destination

      Chain FORWARD (policy ACCEPT)
      target prot opt source destination

      Chain OUTPUT (policy ACCEPT)
      target prot opt source destination


      And the Firewall



      richmaes@portal01:~$ sudo ufw status verbose
      Status: inactive






      firewall iptables ubuntu-18.04 tigervnc






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 8 at 1:47









      Rich MaesRich Maes

      1087




      1087






















          1 Answer
          1






          active

          oldest

          votes


















          0














          Douugh!,
          /etc/vnf.conf needed a



          $localhost = "no";





          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1403368%2ftigervnc-connection-refused-when-using-ip-address-and-accepted-with-127-0-0-1%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Douugh!,
            /etc/vnf.conf needed a



            $localhost = "no";





            share|improve this answer




























              0














              Douugh!,
              /etc/vnf.conf needed a



              $localhost = "no";





              share|improve this answer


























                0












                0








                0







                Douugh!,
                /etc/vnf.conf needed a



                $localhost = "no";





                share|improve this answer













                Douugh!,
                /etc/vnf.conf needed a



                $localhost = "no";






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Feb 8 at 2:02









                Rich MaesRich Maes

                1087




                1087






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1403368%2ftigervnc-connection-refused-when-using-ip-address-and-accepted-with-127-0-0-1%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    How do I know what Microsoft account the skydrive app is syncing to?

                    When does type information flow backwards in C++?

                    Grease: Live!