Sponsored Content
Operating Systems Linux SuSE unable to ping virtualbox machine Post 302361314 by woofie on Tuesday 13th of October 2009 02:00:57 AM
Old 10-13-2009
unable to ping virtualbox machine

I current have Windows 7 running Virtualbox - OpenSUSE.

From SUSE I can ping the Windows box 10.10.x.x no problems.

But from the windows box I can't ping SUSE. I have tried disabling the firewall and sill no luck. Tried pinging host name and still no luck.

The network gives an IP from router with DHCP of 10.10.x.x and the virtual box has a ip of 10.0.2.15 (SUSE IP for br0)

when I do a traceroute;
traceroute to 10.10.x.x (10.10.x.x), 30 hops max, 40 byte packets using UDP
1 10.0.2.2 (10.0.2.2) 0.177 ms 0.152 ms 0.145 ms
2 10.0.2.2 (10.0.2.2) 0.350 ms 0.466 ms 0.219 ms

I can get a ping for 10.0.2.2 but have o idea what this address is for.

Does anyone know why I would not be able to ping the SUSE box from Windows? Or know of any guides I could have a read of? Google and a few other search have not come up with anything helpful so far Smilie
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

ping to machine and count responses

if i wanted to ping all the machines in a given directory (/etc/hosts) and return a total count of responses how would i go about scripting that? complete newbie...so be gentle if ; then //$1 = /etc/hosts cd "$1" //this puts me into the directory i need...but how do i send ... (2 Replies)
Discussion started by: trostycp
2 Replies

2. UNIX for Dummies Questions & Answers

unable to ping

DEar all i am receiving this error on start and then unable to ping (dlpid): unable to open network adapter driver (/dev/mdi/e3h0) what to do ? (2 Replies)
Discussion started by: sak900354
2 Replies

3. IP Networking

Unable to ping the gateway IP itself

We are unable to bring one of our linux boxes into the network once it was restarted. But once we stop and start the network service. We are able to ping the gateway and get into network. After a minute or two we get the following reponse for the ping command 64 bytes from 124.168.215.40:... (6 Replies)
Discussion started by: chrisanto_2000
6 Replies

4. IP Networking

Unable to ping freebsd machine using fully qualified domain name

hi all. am unable to ping a freebsd machine using fully qualified domain name from a windows machine. i have already set the fqdn for the machine. plz advise me. thanks. (2 Replies)
Discussion started by: coolatt
2 Replies

5. Solaris

not able to ping base OS from virtual machine

I have a vista on my PC . I have created a Solaris 10 server on it using VM ware . I have selected bridge mode to connect my PC and virtual machine together .I have alloted ip 192.168.1.2 to my virtual machine and 192.168.1.11 to my PC . I am able to ping the virtual machine from the base machine... (1 Reply)
Discussion started by: asalman.qazi
1 Replies

6. UNIX for Advanced & Expert Users

start virtual machine in Virtualbox giving username and password.

i have found a way to start vm with commanda as follows - VBoxManage startvm <uuid>|<name> it is installed inside oracle virtualbox. in vmware we have a way to do this -- $vmware-cmd -v -H localhost -U user -P password /var/lib/vmware-server/Virtual\ Machines/Ubuntu/Ubuntu.vmx... (0 Replies)
Discussion started by: upvan111
0 Replies

7. AIX

Unable to ping localhost

Hi all, I have gone through many posts related to this issue,but my issue wasn't resolved hence creating new thread. I am unable to ping localhost. ping localhost tries to ping localhost which is defined in DNS. My /etc/hosts has entry for localhost as 127.0.0.1 loopback localhost. ... (8 Replies)
Discussion started by: chpsam
8 Replies

8. Linux

Unable to connect to Server machine from a client machine using ftp service

Hi, Could you please help me with the below issue.. I'm running RHEL6 OS on both server (192.168.0.10) and client machines (192.168.0.1). I'm trying to connect to server from the client machine using ftp service. I have installed vsftpd daemon on both the machines. I'm getting... (4 Replies)
Discussion started by: raosr020
4 Replies

9. IP Networking

Cant ping Linux machine from Windows

Hi I have established LAN with the help of D-Link router. I am having 2 desktops ethernet connection managed by this D-Link router. One PC is with Windows 7 OS Second PC is with Redhat Linux 6.1 Both the PCs now stands connected to internet via this D-Link router. I could ping windows PC... (12 Replies)
Discussion started by: videsh77
12 Replies
TRACEPATH(8)						 System Manager's Manual: iputils					      TRACEPATH(8)

NAME
tracepath, tracepath6 - traces path to a network host discovering MTU along this path SYNOPSIS
tracepath [-n] [-b] [-l pktlen] [-p port] destination DESCRIPTION
It traces path to destination discovering MTU along this path. It uses UDP port port or some random port. It is similar to traceroute, only does not require superuser privileges and has no fancy options. tracepath6 is good replacement for traceroute6 and classic example of application of Linux error queues. The situation with IPv4 is worse, because commercial IP routers do not return enough information in ICMP error messages. Probably, it will change, when they will be updated. For now it uses Van Jacobson's trick, sweeping a range of UDP ports to maintain trace history. OPTIONS
-n Print primarily IP addresses numerically. -b Print both of host names and IP addresses. -l Sets the initial packet length to pktlen instead of 65535 for tracepath or 128000 for tracepath6. -p Sets the initial destination port to use. OUTPUT
root@mops:~ # tracepath6 3ffe:2400:0:109::2 1?: [LOCALHOST] pmtu 1500 1: dust.inr.ac.ru 0.411ms 2: dust.inr.ac.ru asymm 1 0.390ms pmtu 1480 2: 3ffe:2400:0:109::2 463.514ms reached Resume: pmtu 1480 hops 2 back 2 The first column shows TTL of the probe, followed by colon. Usually value of TTL is obtained from reply from network, but sometimes reply does not contain necessary information and we have to guess it. In this case the number is followed by ?. The second column shows the network hop, which replied to the probe. It is either address of router or word [LOCALHOST], if the probe was not sent to the network. The rest of line shows miscellaneous information about path to the correspinding network hop. As rule it contains value of RTT. Addition- ally, it can show Path MTU, when it changes. If the path is asymmetric or the probe finishes before it reach prescribed hop, difference between number of hops in forward and backward direction is shown following keyword async. This information is not reliable. F.e. the third line shows asymmetry of 1, it is because the first probe with TTL of 2 was rejected at the first hop due to Path MTU Discovery. The last line summarizes information about all the path to the destination, it shows detected Path MTU, amount of hops to the destination and our guess about amount of hops from the destination to us, which can be different when the path is asymmetric. SEE ALSO
traceroute(8), traceroute6(8), ping(8). AUTHOR
tracepath was written by Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>. SECURITY
No security issues. This lapidary deserves to be elaborated. tracepath is not a privileged program, unlike traceroute, ping and other beasts of this kind. tracepath may be executed by everyone who has some access to network, enough to send UDP datagrams to investigated destination using given port. AVAILABILITY
tracepath is part of iputils package and the latest versions are available in source form at http://www.skbuff.net/iputils/iputils-cur- rent.tar.bz2. iputils-121221 10 June 2014 TRACEPATH(8)
All times are GMT -4. The time now is 11:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy