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;
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.
Check if SAMBA is already installed using the command below :
$ rpm -q samba
If SAMBA is not yet installed. Type the command shown below to have a root access $ su –
Then you will be asked to type in your password.
Download and install the Linux SAMBA package using the command :
yum install samba
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.
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.
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
Start SAMBA and NetBios Service
a. To start the SAMBA and NetBios Service /etc/init.d/smb stop
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
migrated from stackoverflow.com Sep 19 '12 at 18:56
This question came from our site for professional and enthusiast programmers.
add a comment |
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.
Check if SAMBA is already installed using the command below :
$ rpm -q samba
If SAMBA is not yet installed. Type the command shown below to have a root access $ su –
Then you will be asked to type in your password.
Download and install the Linux SAMBA package using the command :
yum install samba
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.
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.
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
Start SAMBA and NetBios Service
a. To start the SAMBA and NetBios Service /etc/init.d/smb stop
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
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
add a comment |
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.
Check if SAMBA is already installed using the command below :
$ rpm -q samba
If SAMBA is not yet installed. Type the command shown below to have a root access $ su –
Then you will be asked to type in your password.
Download and install the Linux SAMBA package using the command :
yum install samba
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.
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.
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
Start SAMBA and NetBios Service
a. To start the SAMBA and NetBios Service /etc/init.d/smb stop
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
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.
Check if SAMBA is already installed using the command below :
$ rpm -q samba
If SAMBA is not yet installed. Type the command shown below to have a root access $ su –
Then you will be asked to type in your password.
Download and install the Linux SAMBA package using the command :
yum install samba
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.
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.
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
Start SAMBA and NetBios Service
a. To start the SAMBA and NetBios Service /etc/init.d/smb stop
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
centos samba file-server
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
add a comment |
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
add a comment |
1 Answer
1
active
oldest
votes
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.
add a comment |
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
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
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.
add a comment |
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.
add a comment |
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.
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.
answered Oct 17 '14 at 11:17
RalphRalph
1
1
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
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