Cannot ping Windows 7 machine from Linux machines on same LAN [closed] - linux

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 8 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
All firewalls are turned off.
I have 3 Fedora 20 machines and 1 Windows 7 machine on the same 172.x.x.x LAN.
They all have static IP addresses and same subnet. (255.255.255.0)
The Fedora machines can all ping each other.
The Windows 7 machine can ping all 3 Fedora machines.
The Fedora machines, however, cannot ping the Windows 7 machine. I get the response: Destination Host Unreachable.
I ran Wireshark on the Windows machine. ICMP messages show up when pinging from Windows to Fedora, but not the other way around.
To further complicate matters, all machines also have a second network adapter hooked up to a second 10.x.x.x network. On THIS network, all machines CAN ping each other, Windows to Fedora AND Fedora to Windows. It's just the 172.x network where the Fedora machines cannot ping the Windows machine.
I know
there are tons of posts out there already for "cannot ping" issues,
but I haven't been able to find anything that helps with this
specific scenario. Or when I do, it turns out to have been a firewall
issue, and there is no firewall running on these machines.
Any thoughts?
Thank you.

On the Windows machines, make sure that the Network Discovery protocol is turned on. You can doublecheck this by clicking on "Network" in Explorer, and there may be a prompt at the top of the Explorer window that asks you to turn it on. The reason it may work on the 10.x.x.x network is because it may recognize that network as a Home or Work network, but the 172.x.x.x network as a public network. The settings are separate for each type of network.

When pinging from Fedora to Windows on the 172.x.x.x network, it's possible that the source IP of the ping packet is getting set to the IP address on the 10.x.x.x network. This may cause the packet to get dropped immediately by Windows since a packet arrived on the 172.x.x.x interface with a source IP that belongs to the subnet on another interface. This can be easily confirmed by tcpdump/wireshark on Fedora.
======== EDIT ========
So we have confirmed that when Fedora (172.124.16.128) pings Windows (172.124.16.39), the destination MAC address is set to 00:00:00:00:00:00, which is incorrect. The target MAC should be the MAC address of the network interface on Windows that has the IP address of 172.124.16.39 configured on it.
The process of resolving IP to MAC addresses is done by ARP (Address Resolution Protocol), and should happen automatically in the background. To debug why the MAC address isn't getting resolved properly, please clear all ARP cache on Fedora (Google how to clear ARP cache on Linux), start capturing packets, then see what happens with the ARP packets. If you have trouble understanding the packets, you can post them here, and I will take a look.

Related

How to connect to a Linux (Debian) VM from the host (Windows 7) using VNC? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I have a Debian 8 VM using Virtualbox running on a Windows 7.
I've installed TightVNC server on my Debian vm, and UltraVNC on my Windows 7 host, but every ip I try (with the port 5901) returns a "failed to connect to server".
How do I find the correct ip address of the VM in order to connect to its vnc server from the host machine? Is there any other configuration needed?
You can enter into the configuration of the GUEST host.
In configuration / Screen / Remote Screen
check the enable checkbox. (take care of port number)
Then, you only need to open a RDC client (just the Remote access of windows), Put the IP of the HOST machine (and the port like 10.10.10.10:3389) and you are connected fron Anywhere to the Guest machine.
if you need to use VNC, then you need to bridge the tap (ethernet) or need to bypass the port to the machine to reach it from the network.
If you need to connect only with VNC from HOST to GUEST, just read the IP of the ethernet interface of the GUEST, and just connect to this IP From the HOST PC.
You can type in a console IP ADDR to get the IP of the Debian GUEST.

configure virtualbox vms to use proxy settings of host [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I have about 6 VMs for testing purpose in Virtualbox. We have a proxy at work and I do not have a proxy at home. so I switch the settings now and then to get internet inside the VMs. But there has to be a way that the VMs adapt the system settings of my host, or am I wrong? Google didn't help quite good yet. I just found an article about a Microsoft loop back interface, but nothing for Linux. By the way I use Linux just since October, so I am fairly new with this operation system
Some system details:
Host:
arch-Linux with gnome shell and virtualbox 5.0.12
Guests:
Ubuntu, win7, win8, centos6 with nat bridge for internet purpose and host-only adapter for internal network
Anybody experience in the matter who can help me?
I had the same problems you had. I wanted to configure VM's over a corporate proxy. Googling did not help me either. After lots of trials and errors, i finally managed to connect to the internet.
What i did is to configure proxy settings in Guest OS.
I am using ubuntu as Guest OS and its easy to configure the proxy settings as follows:
sudo gedit /etc/apt/apt.conf
It opens the following file:
Acquire::http::Proxy "http://username:pass#myProxyAddress:port/";
Acquire::https::Proxy "https://username:pass#myProxyAddress:port/";
Acquire::ftp::Proxy "ftp://username:pass#myProxyAddress:port/";
Acquire::socks::Proxy "socks://username:pass#myProxyAddress:port/";
And you should change the username, pass, myProxyAddress and port with your own information. It should be good to go. Some apps like FireFox may still not be able to work so you can configure them manually.
I have done this in Ubuntu but it theoretically work for all linux systems. I don't how to configure system wide proxy for windows or would it solve the problem but it should also work for it.
Hope it helps.
ps: Virtual Host Adapter was blocking my Host OS (Windows). You can either bridge or disable the network adapter so that Host and Guest OS can connect to the internet.
You can try this. I tested it on CentOS with NAT model.
192.168.217.1 is gateway address, and port is proxy port in host.
export ALL_PROXY=http://192.168.217.1:port
Please check you have allow LAN connection to your proxy.

Connecting WinSCP with Ubuntu on VirtualBox [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I'm trying to connect Winscp with virtual machine. I'm working on Windows,and this problem is killing me for 5 hours. Studied a lot of examples, but I can't find out what is the problem. I tried to connect with putty to, but connection is every time refused. Tried to connect with every protocol, but didn't help. I even can't install ssh into Ubuntu, because something is blocking but not firewall(failed to fetch us archive ubuntu com). Port forwarding too wasn't very helpful.
1st Adapter is NAT, and second host-only.
Problem is that I need to enter home directory, and add some files, so I'm trying to find the easiest way to do this.
I would really appreciate any help. Here is my ifconfig, ip a, and interfaces picture.
1
Thanks!
Use the following step to configure.
1- Run ipconfig /all on your windows machine and see which ip are assigned to your virtual adopters.
2- Assign the same range ip to your virtual machine. For example:
If on virtual adopter ip is: 192.168.130.1
Then assign ip to your vm as: 192.168.130.*
and set gateway to : 192.168.130.1
and restart the service network and check the reachability by pinging from both side.
3- If You able to ping then you will be able to use internate on your VM. Then install the ssh.
Now you will be able to use.

Can't access localhost in LAMP [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
First of all, I'm beginner at this, so don't be too harsh.
Yesterday, I wanted to make Linux Server. Installed LAMP, PhpMyAdmin. Man the websites IP static. I installed moodle on my website server. Then I closed VirtualBox and went to sleep.
Today when I runned my server and tried to access /phpmyadmin or (ipaddress)/moodle it says that webpage isn't available. Does this mean I have to do everything from the scratch again?
I'd appreciate any help.
I tried command sudo service apache2 start , but nothing changes.
Run this command in Terminal:
sudo service apache2 restart
OR
sudo restart apache2
Try the Answer on this Post
There are a lot of basic troubleshooting steps to take here.
You mentioned "localhost" in your question, but this doesn't sound like the local host; if you're connecting to your guest machine from the host machine then both machines will treat it as a networking connection (because it is networking). How that networking is configured will depend on your VirtualBox configuration.
Are you sure the virtual machine is running, the IP address is assigned, and networking is, well, working? Try pinging the virtual/guest machine from the host machine. After pausing and resuming, one of my Debian machines used to always pick up a DHCP address on the host-networking adapter despite being set to a static address in /etc/network/interfaces. Look at ifconfig to verify the IP address listed is what you expect.
Are you sure Apache is running? Try accessing it from within the guest machine on http://localhost -- by telnet to port 80, command-line tool, or full-on web browser.
Are other services working? Try to connect remotely to whatever you have running: SSH, FTP, IMAP, MySQL, NTP -- try to connect and see if the problem is the network or the service.

Accessing a VM (ESXi) by its hostname doesn't work [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I've set up a VM running Debian Squeeze within VMware ESXi 5.0. It has a running webserver and some other stuff. My goal is to access this machine by its hostname from other computers in my local network. This isn't working, currently I can only access this VM with its IP address.
In my network is a Windows Server 2003 running (as a domain controller with an AD), which is also a DHCP server.
My VM correctly gets an IP address from the subnet 192.168.115.0/24. It can also ping and access other machines from the network by their name after I installed winbind. But the other way around doesn't work, other machines can't find the hostname of this VM.
I have captured the process when my Win7 machine tries to ping this VM by its hostname. Wireshark shows me the following (.100 is the server, .103 is my local machine):
43 2.700104 192.168.115.103 192.168.115.100 NBNS 92 Name query NB INFORMATIX2<00>
44 2.700487 192.168.115.100 192.168.115.103 NBNS 98 Name query response, Requested name does not exist
45 2.720377 192.168.115.103 192.168.115.255 NBNS 92 Name query NB INFORMATIX2<00>
So I guess my server doesn't know the VM, despite having delivered an IP address to it.
What is wrong here?
Ok, I found the problem. The cause was that my Linux machine hasn't enabled dynamic DNS updates (see also manpage of dhclient.conf, section 'DYNAMIC DNS'). This thread had the right hint for me - I have to edit my dhclient.conf and add send host-name "debian-vm"; to it. Despite what is written at the manpage, the hostname is sufficient - I don't need the fqdn.
Now it works - I can access my VM from every other machine in my network. To verify this, I looked at DHCP server settings from the Win2k3 server and checked the leases. Now the name of my VM is shown in the column 'name' - it was empty before the change.
I have to add another piece of information: If you setup the DHCP server of Win2k3 to deliver a specific IP to the MAC address of your VM, it is necessary to activate "updates of DNS-A and -PTR entries for clients which do not request updates" in the properties of your DNS reservation.

Resources