VMware Linux suse ping command
Dear all,
i have linux suse installed on VMware, my pc is running Windows XP. i have a switch connected to my ethernet card (also through console cable) when im on windows i can ping the switch, but from linux i can't... does anyone knows a solution, knowing that mu ethcard is "Bridged" on VMware, i can ping 127.0.0.1 thanks for helping |
Hi,
Disconnect you NIC From VMware and again Connect it and then check by pinging the switch and also check your Linux iptables. Mahi_nix |
Quote:
|
Hi ziadh,
Did you add shared bridge network interface while creating the VM ? You need to have a shared bridge interface to connect to external network from your VM. In linux following command shows all the connected network interfaces Code:
/sbin/ifconfig |
Quote:
thx for the command |
Run Below Command
Code:
iptables -L if any ICMP incoming/outgoing packets are blocked then you have to remove that rule from iptables. Mahi_nix |
results printscreen
2 Attachment(s)
here are the results if
/ifconfig and /iptables -L i can connect to internet using eth0, put when pinging my other ethernet card eth1 (172.26.10.3 , which is the ip of the switch to be telneted), i get " destination unreachable"... any ideas? |
What does your netstat -nr command show in SUSE VM ?
|
netstat -nr printscreen
1 Attachment(s)
Quote:
|
Quote:
What does traceroute command shows in SUSE VM Code:
traceroute 172.26.10.3 |
Both cards are bridged, and i cant run "traceroute" on shell...
Quote:
|
Quote:
Find the path of traceroute by Code:
whereis traceroute Code:
/bin/traceroute 172.26.10.3 |
[QUOTE=vinaytp;4075891]That means traceroute is not in PATH.
Find the path of traceroute by Code:
whereis traceroute Code:
/bin/traceroute 172.26.10.3 |
That means traceroute is not in PATH.
Find the path of traceroute by Code:
whereis traceroute Code:
/bin/traceroute 172.26.10.3 |
That means traceroute is not in PATH.
Find the path of traceroute by Code:
whereis traceroute Code:
/bin/traceroute 172.26.10.3 |
Traceroute result
1 Attachment(s)
I tried to change IP add. of eth1 (172.26.10.2) instead of (172.26.10.1) to avoid conflict with IP configured on windows
arggg this problem is killing me |
i still need help plz! :(
|
Quote:
|
problem solved, finally
yess, i solved the problem, it was smth so stupid, but because im not familiar with VMware/linux it took me quite long time...
i did two things: 1- changed the IP address of the interface under VMware, so it doesnt have conflict with windows 2- changed ethernet connection (on VMware) from bridge to, custom: specific virtual network (i chose VMnet 2) and now it works! thanks to all ur replies and help! |
All times are GMT -5. The time now is 04:46 AM. |