![]() ![]() ![]() Now check the required ports 1 and you will be able to telnet these ports successfully. Iptables: Applying firewall rules: Ĭheck the policies by using the command iptables -L ~]# iptables -LĪCCEPT all - anywhere anywhere state RELATED,ESTABLISHEDĪCCEPT tcp - anywhere anywhere state NEW tcp dpt:sshĪCCEPT tcp - anywhere anywhere state NEW tcp dpt:krb524ĪCCEPT tcp - anywhere anywhere state NEW tcp dpt:personal-agentĪCCEPT tcp - anywhere anywhere state NEW tcp dpt:nfsĪCCEPT udp - anywhere anywhere state NEW udp dpt:nfs Iptables: Setting chains to policy ACCEPT: filter A INPUT -p tcp -m state -state NEW -m tcp -dport 111 -j ACCEPTĪfter updating the /etc/sysconfig/iptables file restart the iptables service to enable the policies on the internal firewall. A INPUT -p tcp -m state -state NEW -m tcp -dport 2049 -j ACCEPT Solution:Īdd the two lines shown below in the file /etc/sysconfig/iptables to accept the request comping on these ports 1. When it was diagnosed then I found that an internal firewall was enabled on the machine 174.11.1.11 that’s why I was not able to telnet the required ports. Telnet: Unable to connect to remote host: No route to host Reason: 5 and later Junos Space works with VMware vSphere 4. Telnet: connect to address 174.11.1.11: No route to host This section explains how to upgrade the software, which includes both the host OS and the Junos OS. Policies were already applied on the external firewall for communication between these two servers on these ports. ![]() I was getting the error “telnet: Unable to connect to remote host: No route to host” in RHEL 6.8 while trying to telnet the port numbers 1 (these ports being used for NFS) from a machine to another machine 174.11.1.11 which was NFS server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |