how to solve NT_STATUS_HOST_UNREACHABLE in CentOS when connecting to (windows) file server via SAMBACreate SAMBA node trust relationship to Windows 2003 PDC serverSamba between Ubuntu server 10.10 and Windows Vista, Windows 7How can I clear the “authentication cache” in Windows 7 to a password protected samba share?How to prevent nginx from locking files on mounted samba partition in Centos 6samba to ask username password before listing shared foldersCentOS 7 firewall-cmd not foundHow to share apache /var/www using samba server in ubuntuCTDB failover and samba/openldap authentication failsSamba 4.9.0 ./configure lmdb error

Externally monitoring CPU/SSD activity without software access

What is this opening/position called, and what is white’s best move?

Grammar Question Regarding "Are the" or "Is the" When Referring to Something that May or May not be Plural

How to illustrate the Mean Value theorem?

Why are C64 games inconsistent with which joystick port they use?

Construct a word ladder

A Riley Respite

Alignment: "Breaking out" of environment (enumerate / minipage)

Why does this if-statement combining assignment and an equality check return true?

Is the derivative with respect to a fermion field Grassmann-odd?

number headings

What are the real benefits of using Salesforce DX?

Where's this lookout in Nova Scotia?

Should I disclose a colleague's illness (that I should not know) when others badmouth him

Could a 19.25mm revolver actually exist?

How should I introduce map drawing to my players?

How do I partition a matrx into blocks and replace zeros with dots?

What was the idiom for something that we take without a doubt?

Why aren't space telescopes put in GEO?

Is the taxi route omitted in low visibility (LVP)?

What to do when you've set the wrong ISO for your film?

How to use libraries with delays inside within a time critical STM32 HAL application?

Employer demanding to see degree after poor code review

How strong are Wi-Fi signals?



how to solve NT_STATUS_HOST_UNREACHABLE in CentOS when connecting to (windows) file server via SAMBA


Create SAMBA node trust relationship to Windows 2003 PDC serverSamba between Ubuntu server 10.10 and Windows Vista, Windows 7How can I clear the “authentication cache” in Windows 7 to a password protected samba share?How to prevent nginx from locking files on mounted samba partition in Centos 6samba to ask username password before listing shared foldersCentOS 7 firewall-cmd not foundHow to share apache /var/www using samba server in ubuntuCTDB failover and samba/openldap authentication failsSamba 4.9.0 ./configure lmdb error






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








0















I am using CentOS and I need to connect to a file server running on windows. My friend told me that I need to install SAMBA to be able to do that. and so I installed samba and when I try to check if the installation is successful, this command




smbclient //[hostname]/[sharename] -U [username]




gave me this




timeout connecting to XXX.XXX.XXX.XXX:XXX
Error Connecting to XXX.XXX.XXX.XXX (No route to host)
Connection to XXX.XXX.XXX.XXX failed (Error NT_STATUS_HOST_UNREACHABLE)




How do I fix this?



Here's the step by step instruction how I installed SAMBA. Kindly check if I'm missing something.





  1. Check if SAMBA is already installed using the command below :
    $ rpm -q samba


  2. If SAMBA is not yet installed. Type the command shown below to have a root access $ su –


  3. Then you will be asked to type in your password.


  4. Download and install the Linux SAMBA package using the command :
    yum install samba


  5. Configure the Linux Firewall so that it will allow the SAMBA traffic by following the steps below.
    a. Click the System >> Administration > Security Level and Firewall
    b. Type the root password> in the textbox provided
    c. In “Firewall Options” tab, Check the SAMBA > Combo box.
    d. Apply and press ok.



  6. Configure the SAMBA config file. In the terminal, you should have a root access, (do as told in number 2) and type in the command below.



    gedit /etc/samba/smb.conf


this will open the smb.conf and it is ready for any modification.



Spot the part of the config file which contains workgroup. Edit that
part, change the value to “workgroup”



 workgroup = workgroup


And add this section
[NetApps]



path = /data/network-applications 
writeable = yes
browseable = yes
valid users = administrator Save all the changes.


  1. Create a SAMBA user
    a. You must gain root privileges by doing the command in number 2.
    b. Add administrator as a user smbpasswd -a > administrator

    c. Then it will ask you to type the password for that > account.
    d. To know if you have any error with the configuration, use > this command Testparm


  2. Start SAMBA and NetBios Service
    a. To start the SAMBA and NetBios Service /etc/init.d/smb stop


  3. Accessing Windows Shares From CentOS
    a. Gain root privileges by doing number 2.
    b. Download and install samba-client $ Yum install > samba-client












share|improve this question













migrated from stackoverflow.com Sep 19 '12 at 18:56


This question came from our site for professional and enthusiast programmers.


















  • Please let me know your farewell is Enable/Disable if Enable then configure your farewell via command line "iptables" or " system-config-farewell" use any method..

    – user165888
    Mar 22 '13 at 5:40






  • 1





    Actually you should check L3 connectivity via commands like ping|traceroute and L4 connectivity with telnet and tcpdump.

    – Navern
    May 24 '15 at 19:56

















0















I am using CentOS and I need to connect to a file server running on windows. My friend told me that I need to install SAMBA to be able to do that. and so I installed samba and when I try to check if the installation is successful, this command




smbclient //[hostname]/[sharename] -U [username]




gave me this




timeout connecting to XXX.XXX.XXX.XXX:XXX
Error Connecting to XXX.XXX.XXX.XXX (No route to host)
Connection to XXX.XXX.XXX.XXX failed (Error NT_STATUS_HOST_UNREACHABLE)




How do I fix this?



Here's the step by step instruction how I installed SAMBA. Kindly check if I'm missing something.





  1. Check if SAMBA is already installed using the command below :
    $ rpm -q samba


  2. If SAMBA is not yet installed. Type the command shown below to have a root access $ su –


  3. Then you will be asked to type in your password.


  4. Download and install the Linux SAMBA package using the command :
    yum install samba


  5. Configure the Linux Firewall so that it will allow the SAMBA traffic by following the steps below.
    a. Click the System >> Administration > Security Level and Firewall
    b. Type the root password> in the textbox provided
    c. In “Firewall Options” tab, Check the SAMBA > Combo box.
    d. Apply and press ok.



  6. Configure the SAMBA config file. In the terminal, you should have a root access, (do as told in number 2) and type in the command below.



    gedit /etc/samba/smb.conf


this will open the smb.conf and it is ready for any modification.



Spot the part of the config file which contains workgroup. Edit that
part, change the value to “workgroup”



 workgroup = workgroup


And add this section
[NetApps]



path = /data/network-applications 
writeable = yes
browseable = yes
valid users = administrator Save all the changes.


  1. Create a SAMBA user
    a. You must gain root privileges by doing the command in number 2.
    b. Add administrator as a user smbpasswd -a > administrator

    c. Then it will ask you to type the password for that > account.
    d. To know if you have any error with the configuration, use > this command Testparm


  2. Start SAMBA and NetBios Service
    a. To start the SAMBA and NetBios Service /etc/init.d/smb stop


  3. Accessing Windows Shares From CentOS
    a. Gain root privileges by doing number 2.
    b. Download and install samba-client $ Yum install > samba-client












share|improve this question













migrated from stackoverflow.com Sep 19 '12 at 18:56


This question came from our site for professional and enthusiast programmers.


















  • Please let me know your farewell is Enable/Disable if Enable then configure your farewell via command line "iptables" or " system-config-farewell" use any method..

    – user165888
    Mar 22 '13 at 5:40






  • 1





    Actually you should check L3 connectivity via commands like ping|traceroute and L4 connectivity with telnet and tcpdump.

    – Navern
    May 24 '15 at 19:56













0












0








0


1






I am using CentOS and I need to connect to a file server running on windows. My friend told me that I need to install SAMBA to be able to do that. and so I installed samba and when I try to check if the installation is successful, this command




smbclient //[hostname]/[sharename] -U [username]




gave me this




timeout connecting to XXX.XXX.XXX.XXX:XXX
Error Connecting to XXX.XXX.XXX.XXX (No route to host)
Connection to XXX.XXX.XXX.XXX failed (Error NT_STATUS_HOST_UNREACHABLE)




How do I fix this?



Here's the step by step instruction how I installed SAMBA. Kindly check if I'm missing something.





  1. Check if SAMBA is already installed using the command below :
    $ rpm -q samba


  2. If SAMBA is not yet installed. Type the command shown below to have a root access $ su –


  3. Then you will be asked to type in your password.


  4. Download and install the Linux SAMBA package using the command :
    yum install samba


  5. Configure the Linux Firewall so that it will allow the SAMBA traffic by following the steps below.
    a. Click the System >> Administration > Security Level and Firewall
    b. Type the root password> in the textbox provided
    c. In “Firewall Options” tab, Check the SAMBA > Combo box.
    d. Apply and press ok.



  6. Configure the SAMBA config file. In the terminal, you should have a root access, (do as told in number 2) and type in the command below.



    gedit /etc/samba/smb.conf


this will open the smb.conf and it is ready for any modification.



Spot the part of the config file which contains workgroup. Edit that
part, change the value to “workgroup”



 workgroup = workgroup


And add this section
[NetApps]



path = /data/network-applications 
writeable = yes
browseable = yes
valid users = administrator Save all the changes.


  1. Create a SAMBA user
    a. You must gain root privileges by doing the command in number 2.
    b. Add administrator as a user smbpasswd -a > administrator

    c. Then it will ask you to type the password for that > account.
    d. To know if you have any error with the configuration, use > this command Testparm


  2. Start SAMBA and NetBios Service
    a. To start the SAMBA and NetBios Service /etc/init.d/smb stop


  3. Accessing Windows Shares From CentOS
    a. Gain root privileges by doing number 2.
    b. Download and install samba-client $ Yum install > samba-client












share|improve this question














I am using CentOS and I need to connect to a file server running on windows. My friend told me that I need to install SAMBA to be able to do that. and so I installed samba and when I try to check if the installation is successful, this command




smbclient //[hostname]/[sharename] -U [username]




gave me this




timeout connecting to XXX.XXX.XXX.XXX:XXX
Error Connecting to XXX.XXX.XXX.XXX (No route to host)
Connection to XXX.XXX.XXX.XXX failed (Error NT_STATUS_HOST_UNREACHABLE)




How do I fix this?



Here's the step by step instruction how I installed SAMBA. Kindly check if I'm missing something.





  1. Check if SAMBA is already installed using the command below :
    $ rpm -q samba


  2. If SAMBA is not yet installed. Type the command shown below to have a root access $ su –


  3. Then you will be asked to type in your password.


  4. Download and install the Linux SAMBA package using the command :
    yum install samba


  5. Configure the Linux Firewall so that it will allow the SAMBA traffic by following the steps below.
    a. Click the System >> Administration > Security Level and Firewall
    b. Type the root password> in the textbox provided
    c. In “Firewall Options” tab, Check the SAMBA > Combo box.
    d. Apply and press ok.



  6. Configure the SAMBA config file. In the terminal, you should have a root access, (do as told in number 2) and type in the command below.



    gedit /etc/samba/smb.conf


this will open the smb.conf and it is ready for any modification.



Spot the part of the config file which contains workgroup. Edit that
part, change the value to “workgroup”



 workgroup = workgroup


And add this section
[NetApps]



path = /data/network-applications 
writeable = yes
browseable = yes
valid users = administrator Save all the changes.


  1. Create a SAMBA user
    a. You must gain root privileges by doing the command in number 2.
    b. Add administrator as a user smbpasswd -a > administrator

    c. Then it will ask you to type the password for that > account.
    d. To know if you have any error with the configuration, use > this command Testparm


  2. Start SAMBA and NetBios Service
    a. To start the SAMBA and NetBios Service /etc/init.d/smb stop


  3. Accessing Windows Shares From CentOS
    a. Gain root privileges by doing number 2.
    b. Download and install samba-client $ Yum install > samba-client









centos samba file-server






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Sep 19 '12 at 10:45







srh snl











migrated from stackoverflow.com Sep 19 '12 at 18:56


This question came from our site for professional and enthusiast programmers.









migrated from stackoverflow.com Sep 19 '12 at 18:56


This question came from our site for professional and enthusiast programmers.














  • Please let me know your farewell is Enable/Disable if Enable then configure your farewell via command line "iptables" or " system-config-farewell" use any method..

    – user165888
    Mar 22 '13 at 5:40






  • 1





    Actually you should check L3 connectivity via commands like ping|traceroute and L4 connectivity with telnet and tcpdump.

    – Navern
    May 24 '15 at 19:56

















  • Please let me know your farewell is Enable/Disable if Enable then configure your farewell via command line "iptables" or " system-config-farewell" use any method..

    – user165888
    Mar 22 '13 at 5:40






  • 1





    Actually you should check L3 connectivity via commands like ping|traceroute and L4 connectivity with telnet and tcpdump.

    – Navern
    May 24 '15 at 19:56
















Please let me know your farewell is Enable/Disable if Enable then configure your farewell via command line "iptables" or " system-config-farewell" use any method..

– user165888
Mar 22 '13 at 5:40





Please let me know your farewell is Enable/Disable if Enable then configure your farewell via command line "iptables" or " system-config-farewell" use any method..

– user165888
Mar 22 '13 at 5:40




1




1





Actually you should check L3 connectivity via commands like ping|traceroute and L4 connectivity with telnet and tcpdump.

– Navern
May 24 '15 at 19:56





Actually you should check L3 connectivity via commands like ping|traceroute and L4 connectivity with telnet and tcpdump.

– Navern
May 24 '15 at 19:56










1 Answer
1






active

oldest

votes


















0














I'm writing this from the samba server's perspective.



If you don't have access to a gui or prefer to do things in the command line you can replace step 5 with:



First, work out which ports samba is listening on. This can be done with this command:



netstat -tulpn | egrep "samba|smbd|nmbd|winbind"



You'll see something like this:



tcp 0 0 127.0.0.1:139 0.0.0.0:* LISTEN 43270/smbd

tcp 0 0 10.0.0.1:139 0.0.0.0:* LISTEN 43270/smbd

tcp 0 0 10.0.0.1:88 0.0.0.0:* LISTEN 43273/samba

tcp 0 0 127.0.0.1:88 0.0.0.0:* LISTEN 43273/samba

tcp 0 0 127.0.0.1:445 0.0.0.0:* LISTEN 43270/smbd

tcp 0 0 10.0.0.1:445 0.0.0.0:* LISTEN 43270/smbd



The above example shows, that the services are listening on localhost (127.0.0.1) and the interface with IP 10.0.0.1 - each on the listed ports (139, 88, 445, and so on). Further information about samba port usage can be found here: https://wiki.samba.org/index.php/Samba_port_usage



Make a note of port and associated tcp/udp, then add lines that open these ports and protocols in /etc/sysconfig/iptables (it's probably a good plan to back up iptables before editing).



If we take the top line of output from the example above, we'd want to open TCP port 139 in iptables. This can be done by adding the following line of text to /etc/sysconfig/iptables:



-A INPUT -m state --state NEW -m tcp -p tcp --dport 139 -j ACCEPT



Say if you wanted to open UDP port 137 you could do it by adding the following line of text to /etc/sysconfig/iptables



-A INPUT -m state --state NEW -m udp -p ucp --dport 137 -j ACCEPT



You'd need to keep adding lines for any other ports that you need to have open.



Then save your changes, and restart IPtables (service iptables restart).



Hope that helps.






share|improve this answer























    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "2"
    ;
    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%2fserverfault.com%2fquestions%2f429991%2fhow-to-solve-nt-status-host-unreachable-in-centos-when-connecting-to-windows-f%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














    I'm writing this from the samba server's perspective.



    If you don't have access to a gui or prefer to do things in the command line you can replace step 5 with:



    First, work out which ports samba is listening on. This can be done with this command:



    netstat -tulpn | egrep "samba|smbd|nmbd|winbind"



    You'll see something like this:



    tcp 0 0 127.0.0.1:139 0.0.0.0:* LISTEN 43270/smbd

    tcp 0 0 10.0.0.1:139 0.0.0.0:* LISTEN 43270/smbd

    tcp 0 0 10.0.0.1:88 0.0.0.0:* LISTEN 43273/samba

    tcp 0 0 127.0.0.1:88 0.0.0.0:* LISTEN 43273/samba

    tcp 0 0 127.0.0.1:445 0.0.0.0:* LISTEN 43270/smbd

    tcp 0 0 10.0.0.1:445 0.0.0.0:* LISTEN 43270/smbd



    The above example shows, that the services are listening on localhost (127.0.0.1) and the interface with IP 10.0.0.1 - each on the listed ports (139, 88, 445, and so on). Further information about samba port usage can be found here: https://wiki.samba.org/index.php/Samba_port_usage



    Make a note of port and associated tcp/udp, then add lines that open these ports and protocols in /etc/sysconfig/iptables (it's probably a good plan to back up iptables before editing).



    If we take the top line of output from the example above, we'd want to open TCP port 139 in iptables. This can be done by adding the following line of text to /etc/sysconfig/iptables:



    -A INPUT -m state --state NEW -m tcp -p tcp --dport 139 -j ACCEPT



    Say if you wanted to open UDP port 137 you could do it by adding the following line of text to /etc/sysconfig/iptables



    -A INPUT -m state --state NEW -m udp -p ucp --dport 137 -j ACCEPT



    You'd need to keep adding lines for any other ports that you need to have open.



    Then save your changes, and restart IPtables (service iptables restart).



    Hope that helps.






    share|improve this answer



























      0














      I'm writing this from the samba server's perspective.



      If you don't have access to a gui or prefer to do things in the command line you can replace step 5 with:



      First, work out which ports samba is listening on. This can be done with this command:



      netstat -tulpn | egrep "samba|smbd|nmbd|winbind"



      You'll see something like this:



      tcp 0 0 127.0.0.1:139 0.0.0.0:* LISTEN 43270/smbd

      tcp 0 0 10.0.0.1:139 0.0.0.0:* LISTEN 43270/smbd

      tcp 0 0 10.0.0.1:88 0.0.0.0:* LISTEN 43273/samba

      tcp 0 0 127.0.0.1:88 0.0.0.0:* LISTEN 43273/samba

      tcp 0 0 127.0.0.1:445 0.0.0.0:* LISTEN 43270/smbd

      tcp 0 0 10.0.0.1:445 0.0.0.0:* LISTEN 43270/smbd



      The above example shows, that the services are listening on localhost (127.0.0.1) and the interface with IP 10.0.0.1 - each on the listed ports (139, 88, 445, and so on). Further information about samba port usage can be found here: https://wiki.samba.org/index.php/Samba_port_usage



      Make a note of port and associated tcp/udp, then add lines that open these ports and protocols in /etc/sysconfig/iptables (it's probably a good plan to back up iptables before editing).



      If we take the top line of output from the example above, we'd want to open TCP port 139 in iptables. This can be done by adding the following line of text to /etc/sysconfig/iptables:



      -A INPUT -m state --state NEW -m tcp -p tcp --dport 139 -j ACCEPT



      Say if you wanted to open UDP port 137 you could do it by adding the following line of text to /etc/sysconfig/iptables



      -A INPUT -m state --state NEW -m udp -p ucp --dport 137 -j ACCEPT



      You'd need to keep adding lines for any other ports that you need to have open.



      Then save your changes, and restart IPtables (service iptables restart).



      Hope that helps.






      share|improve this answer

























        0












        0








        0







        I'm writing this from the samba server's perspective.



        If you don't have access to a gui or prefer to do things in the command line you can replace step 5 with:



        First, work out which ports samba is listening on. This can be done with this command:



        netstat -tulpn | egrep "samba|smbd|nmbd|winbind"



        You'll see something like this:



        tcp 0 0 127.0.0.1:139 0.0.0.0:* LISTEN 43270/smbd

        tcp 0 0 10.0.0.1:139 0.0.0.0:* LISTEN 43270/smbd

        tcp 0 0 10.0.0.1:88 0.0.0.0:* LISTEN 43273/samba

        tcp 0 0 127.0.0.1:88 0.0.0.0:* LISTEN 43273/samba

        tcp 0 0 127.0.0.1:445 0.0.0.0:* LISTEN 43270/smbd

        tcp 0 0 10.0.0.1:445 0.0.0.0:* LISTEN 43270/smbd



        The above example shows, that the services are listening on localhost (127.0.0.1) and the interface with IP 10.0.0.1 - each on the listed ports (139, 88, 445, and so on). Further information about samba port usage can be found here: https://wiki.samba.org/index.php/Samba_port_usage



        Make a note of port and associated tcp/udp, then add lines that open these ports and protocols in /etc/sysconfig/iptables (it's probably a good plan to back up iptables before editing).



        If we take the top line of output from the example above, we'd want to open TCP port 139 in iptables. This can be done by adding the following line of text to /etc/sysconfig/iptables:



        -A INPUT -m state --state NEW -m tcp -p tcp --dport 139 -j ACCEPT



        Say if you wanted to open UDP port 137 you could do it by adding the following line of text to /etc/sysconfig/iptables



        -A INPUT -m state --state NEW -m udp -p ucp --dport 137 -j ACCEPT



        You'd need to keep adding lines for any other ports that you need to have open.



        Then save your changes, and restart IPtables (service iptables restart).



        Hope that helps.






        share|improve this answer













        I'm writing this from the samba server's perspective.



        If you don't have access to a gui or prefer to do things in the command line you can replace step 5 with:



        First, work out which ports samba is listening on. This can be done with this command:



        netstat -tulpn | egrep "samba|smbd|nmbd|winbind"



        You'll see something like this:



        tcp 0 0 127.0.0.1:139 0.0.0.0:* LISTEN 43270/smbd

        tcp 0 0 10.0.0.1:139 0.0.0.0:* LISTEN 43270/smbd

        tcp 0 0 10.0.0.1:88 0.0.0.0:* LISTEN 43273/samba

        tcp 0 0 127.0.0.1:88 0.0.0.0:* LISTEN 43273/samba

        tcp 0 0 127.0.0.1:445 0.0.0.0:* LISTEN 43270/smbd

        tcp 0 0 10.0.0.1:445 0.0.0.0:* LISTEN 43270/smbd



        The above example shows, that the services are listening on localhost (127.0.0.1) and the interface with IP 10.0.0.1 - each on the listed ports (139, 88, 445, and so on). Further information about samba port usage can be found here: https://wiki.samba.org/index.php/Samba_port_usage



        Make a note of port and associated tcp/udp, then add lines that open these ports and protocols in /etc/sysconfig/iptables (it's probably a good plan to back up iptables before editing).



        If we take the top line of output from the example above, we'd want to open TCP port 139 in iptables. This can be done by adding the following line of text to /etc/sysconfig/iptables:



        -A INPUT -m state --state NEW -m tcp -p tcp --dport 139 -j ACCEPT



        Say if you wanted to open UDP port 137 you could do it by adding the following line of text to /etc/sysconfig/iptables



        -A INPUT -m state --state NEW -m udp -p ucp --dport 137 -j ACCEPT



        You'd need to keep adding lines for any other ports that you need to have open.



        Then save your changes, and restart IPtables (service iptables restart).



        Hope that helps.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Oct 17 '14 at 11:17









        RalphRalph

        1




        1



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Server Fault!


            • 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%2fserverfault.com%2fquestions%2f429991%2fhow-to-solve-nt-status-host-unreachable-in-centos-when-connecting-to-windows-f%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

            Wikipedia:Vital articles Мазмуну Biography - Өмүр баян Philosophy and psychology - Философия жана психология Religion - Дин Social sciences - Коомдук илимдер Language and literature - Тил жана адабият Science - Илим Technology - Технология Arts and recreation - Искусство жана эс алуу History and geography - Тарых жана география Навигация менюсу

            Bruxelas-Capital Índice Historia | Composición | Situación lingüística | Clima | Cidades irmandadas | Notas | Véxase tamén | Menú de navegacióneO uso das linguas en Bruxelas e a situación do neerlandés"Rexión de Bruxelas Capital"o orixinalSitio da rexiónPáxina de Bruselas no sitio da Oficina de Promoción Turística de Valonia e BruxelasMapa Interactivo da Rexión de Bruxelas-CapitaleeWorldCat332144929079854441105155190212ID28008674080552-90000 0001 0666 3698n94104302ID540940339365017018237

            What should I write in an apology letter, since I have decided not to join a company after accepting an offer letterShould I keep looking after accepting a job offer?What should I do when I've been verbally told I would get an offer letter, but still haven't gotten one after 4 weeks?Do I accept an offer from a company that I am not likely to join?New job hasn't confirmed starting date and I want to give current employer as much notice as possibleHow should I address my manager in my resignation letter?HR delayed background verification, now jobless as resignedNo email communication after accepting a formal written offer. How should I phrase the call?What should I do if after receiving a verbal offer letter I am informed that my written job offer is put on hold due to some internal issues?Should I inform the current employer that I am about to resign within 1-2 weeks since I have signed the offer letter and waiting for visa?What company will do, if I send their offer letter to another company