All ports are closed - Ubuntu 17

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












OK, so I have dabbled with Linux for a while but nothing too serious (so bear with me). Have set up Ubuntu as a main desktop and wanted to add a networked printer. Have set this up while ago using Lubuntu and all worked fine. However, this time I am struggling and have read a large number of threads but nothing helps. I cannot print and am getting various errors mainly saying that the printer is not found etc. I have used nmap and am getting "all 1000 scanned ports on (printer IP) are closed". This is rather odd, it's an out of the box install.
Have tried disabling iptables, same result. On the machine where I have lubuntu installed I get
Port State Service
91000/tcp open jetdirect



I can ping the IP address of the printer



Any idea what might be wrong? Is there something wrong with my network profile? firewall? Something different?










share|improve this question

















  • 1




    That doesn't sound right. What commands did you use? E.g. if my network was 192.168.1.x, I would do nmap -sP 192.168.1.0/24 to verify the devices. This also checks that you have a working network. If my printer was 192.168.1.10, I would then do: nmap -sS -F 192.168.1.10 to look for the JetDirect port. How does that compare with what you did?
    – Martin W
    Apr 17 at 20:05















up vote
0
down vote

favorite












OK, so I have dabbled with Linux for a while but nothing too serious (so bear with me). Have set up Ubuntu as a main desktop and wanted to add a networked printer. Have set this up while ago using Lubuntu and all worked fine. However, this time I am struggling and have read a large number of threads but nothing helps. I cannot print and am getting various errors mainly saying that the printer is not found etc. I have used nmap and am getting "all 1000 scanned ports on (printer IP) are closed". This is rather odd, it's an out of the box install.
Have tried disabling iptables, same result. On the machine where I have lubuntu installed I get
Port State Service
91000/tcp open jetdirect



I can ping the IP address of the printer



Any idea what might be wrong? Is there something wrong with my network profile? firewall? Something different?










share|improve this question

















  • 1




    That doesn't sound right. What commands did you use? E.g. if my network was 192.168.1.x, I would do nmap -sP 192.168.1.0/24 to verify the devices. This also checks that you have a working network. If my printer was 192.168.1.10, I would then do: nmap -sS -F 192.168.1.10 to look for the JetDirect port. How does that compare with what you did?
    – Martin W
    Apr 17 at 20:05













up vote
0
down vote

favorite









up vote
0
down vote

favorite











OK, so I have dabbled with Linux for a while but nothing too serious (so bear with me). Have set up Ubuntu as a main desktop and wanted to add a networked printer. Have set this up while ago using Lubuntu and all worked fine. However, this time I am struggling and have read a large number of threads but nothing helps. I cannot print and am getting various errors mainly saying that the printer is not found etc. I have used nmap and am getting "all 1000 scanned ports on (printer IP) are closed". This is rather odd, it's an out of the box install.
Have tried disabling iptables, same result. On the machine where I have lubuntu installed I get
Port State Service
91000/tcp open jetdirect



I can ping the IP address of the printer



Any idea what might be wrong? Is there something wrong with my network profile? firewall? Something different?










share|improve this question













OK, so I have dabbled with Linux for a while but nothing too serious (so bear with me). Have set up Ubuntu as a main desktop and wanted to add a networked printer. Have set this up while ago using Lubuntu and all worked fine. However, this time I am struggling and have read a large number of threads but nothing helps. I cannot print and am getting various errors mainly saying that the printer is not found etc. I have used nmap and am getting "all 1000 scanned ports on (printer IP) are closed". This is rather odd, it's an out of the box install.
Have tried disabling iptables, same result. On the machine where I have lubuntu installed I get
Port State Service
91000/tcp open jetdirect



I can ping the IP address of the printer



Any idea what might be wrong? Is there something wrong with my network profile? firewall? Something different?







networking printing iptables






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Apr 17 at 19:54









Chris

1




1







  • 1




    That doesn't sound right. What commands did you use? E.g. if my network was 192.168.1.x, I would do nmap -sP 192.168.1.0/24 to verify the devices. This also checks that you have a working network. If my printer was 192.168.1.10, I would then do: nmap -sS -F 192.168.1.10 to look for the JetDirect port. How does that compare with what you did?
    – Martin W
    Apr 17 at 20:05













  • 1




    That doesn't sound right. What commands did you use? E.g. if my network was 192.168.1.x, I would do nmap -sP 192.168.1.0/24 to verify the devices. This also checks that you have a working network. If my printer was 192.168.1.10, I would then do: nmap -sS -F 192.168.1.10 to look for the JetDirect port. How does that compare with what you did?
    – Martin W
    Apr 17 at 20:05








1




1




That doesn't sound right. What commands did you use? E.g. if my network was 192.168.1.x, I would do nmap -sP 192.168.1.0/24 to verify the devices. This also checks that you have a working network. If my printer was 192.168.1.10, I would then do: nmap -sS -F 192.168.1.10 to look for the JetDirect port. How does that compare with what you did?
– Martin W
Apr 17 at 20:05





That doesn't sound right. What commands did you use? E.g. if my network was 192.168.1.x, I would do nmap -sP 192.168.1.0/24 to verify the devices. This also checks that you have a working network. If my printer was 192.168.1.10, I would then do: nmap -sS -F 192.168.1.10 to look for the JetDirect port. How does that compare with what you did?
– Martin W
Apr 17 at 20:05











1 Answer
1






active

oldest

votes

















up vote
0
down vote













OK, sorry, just answered my own question. I did some more digging and the realised that my stupid sky router has given out the IP of my printer (fixed) to my machine. Totally odd, even though I have reserved the IP of that printer. Gave my machine a temporary fixed IP which is different from the printer and it's now working as on my other machine.






share|improve this answer




















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "89"
    ;
    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',
    convertImagesToLinks: true,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1025915%2fall-ports-are-closed-ubuntu-17%23new-answer', 'question_page');

    );

    Post as a guest






























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    OK, sorry, just answered my own question. I did some more digging and the realised that my stupid sky router has given out the IP of my printer (fixed) to my machine. Totally odd, even though I have reserved the IP of that printer. Gave my machine a temporary fixed IP which is different from the printer and it's now working as on my other machine.






    share|improve this answer
























      up vote
      0
      down vote













      OK, sorry, just answered my own question. I did some more digging and the realised that my stupid sky router has given out the IP of my printer (fixed) to my machine. Totally odd, even though I have reserved the IP of that printer. Gave my machine a temporary fixed IP which is different from the printer and it's now working as on my other machine.






      share|improve this answer






















        up vote
        0
        down vote










        up vote
        0
        down vote









        OK, sorry, just answered my own question. I did some more digging and the realised that my stupid sky router has given out the IP of my printer (fixed) to my machine. Totally odd, even though I have reserved the IP of that printer. Gave my machine a temporary fixed IP which is different from the printer and it's now working as on my other machine.






        share|improve this answer












        OK, sorry, just answered my own question. I did some more digging and the realised that my stupid sky router has given out the IP of my printer (fixed) to my machine. Totally odd, even though I have reserved the IP of that printer. Gave my machine a temporary fixed IP which is different from the printer and it's now working as on my other machine.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Apr 17 at 20:04









        Chris

        1




        1



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1025915%2fall-ports-are-closed-ubuntu-17%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            pylint3 and pip3 broken

            Missing snmpget and snmpwalk

            How to enroll fingerprints to Ubuntu 17.10 with VFS491