telnet: connect to address 192.168.15.3: No route to host
hi fellas im a new member of this group . i m developing a socket programme . my one machine1 ip = 192.168.15.3 when send a string to machine2 ip = 192.168.15.2. the prg works fine but when i do this from machine2 to machine1 this doesnot work.
I pinged each other its fine but when i tried to telnet for 192.168.15.2 to 192.168.15.3 i got this error telnet: connect to address 192.168.15.3: No route to host my iptables is empty n SElinux is also disabled i dont understand the prb kindly help me out regards M.Ahmed |
Try updating your /etc/hosts file on both machines. This is what the entries look like:
Quote:
|
What the route command says? (on 192.168.15.2)
|
output of 'route'
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.15.0 * 255.255.255.0 U 0 0 0 eth0 169.254.0.0 * 255.255.0.0 U 0 0 0 eth0 default mywimax 0.0.0.0 UG 0 0 0 eth0 |
nothing happened with additions on /etc/hosts still the same error
|
But you are able to connect through ssh to 192.168.15.3?
Eventually try ssh -vvv for debug. Also, try a nmap scan for 192.168.15.3 and post the results. |
Quote:
|
Check out the firewall settings, I had problems similar to that and although I added rules to iptables it still didn't work because the firewall settings did have the trusted service selected.
System -> Administration -> Security Level and Firewall Then under trusted services select telnet and whatever else you wish to use. Regards, Chris |
The output of #route looks ok.
It looks like the 192.168.3 is not accepting telnet connections. Is port 23 open? |
No route to host ... means that the workstation thinks it cannot get there.
As you have configured both hosts on the same network ... I would say there is something wrong with the Ethernet interface. There was another recent post with this same problem ... it was found that the ethernet card driver was the cause. |
ssh is working i connect both machines with ssh
|
Quote:
It is also possible there is something odd with the switch between the machines. If it is manageable you could check the mac-address table on it, too. Hope this helps. ch |
Quote:
|
@ chris2430 : thanks ,in fact everyone for responding to my prb. It has worked the firewall settings for TCP was not in trusted side on the receiving end .
soon will be coming with others ThankU all. |
All times are GMT -5. The time now is 11:38 PM. |