Connecting two computers with ethernet cable - windows

I'm new to networking. I need to transfer a lot of large files from a Windows 10 pc to Ubuntu 16.04 pc. I connected the two PCs with an ethernet cable and installed http-server for nodejs on Windows 10 pc and started it as follow:
http-server E:/ -a 192.168.0.130
Starting up http-server, serving E:/
Available on:
http://192.168.0.130:8080
Hit CTRL-C to stop the server.
On Ubuntu pc I opened my brower (Firefox) and entered 192.168.0.130 without success. How can I achieve connection between the two computers?

Have you configured IP addresses on both computers? Did you make sure to put them on the same IP network?
Also, if you connect computers directly to each other with an ethernet cable the network interface cards need to be able to detect and correct the fact that you are not using a "cross-over" ethernet cable. Almost all newer ethernet cards can do this so it probably won't be a problem.
I suspect you have not put IP addresses on the computers. You will need to do this manually since you are not connecting to a network that is dynamically assigning addresses via DHCP.

Related

Network Connect 2 virtual machines accross 2 different computers

I got an interesting idea to create a hadoop cluster by using 2 laptops connected to a router, but ran into a problem.
I am trying to network connect 2 virtual machines accross the lan using a VMware workstation as the figure above. After trying a lot i have managed to connect the hosts(the windows 10 ie), but i can't figure out how to the connect the virtual machine to each other.
Change the network adapter to Bridged adapter, then only it will be accessible to outside of the VMware host.
Try above and let me if you output
Alright this is how I managed to do. i left 1st system as it is, just replaced it with a ubuntu 16.04 virtual machine and a usb to ethernet adapter was added & in the vmware network adaptor was disabled & usb to ethernet adaptor was enabled.
The 2nd system was completely formated to ubuntu 16.04.
On connectinng to router everything worked Flawlessly with correct ip

Sending regular UDP packets in Windows 10

I currently have an effect here that drives me crazy.
I got a Windows 10 PC System in a local network at home ( A typical 192.168.178.X network with a Fritzbox as DNS and Gateway)
Everything runs fine. The Windows PC can connect to the internet, I can browse, play games in the internet etc.
Now I am currently playing around with a little device (ESP8266 and an OLED) which is connected via WLAN to the Fritzbox, while my Windows PC is via cable. The device shall receive UDP messages (no broadcast, just direct) and display them on its OLED.
I programmed the device and start it, then doing a test via my android mobile (also in the network via Wireless), using some UDP tester app from the store. Every UDP Packet is perfectly received and displayed on the device.
Now I want to test it from the Windows PC. I downloaded a free tool from the internet (Packet Sender). Entered the address and port and gave it some text to send.
The device does not receive anything at all. Strange #1.
Now I do some little coding in Java on the PC now. A simple "Hello World UDP Sender". Taken directly from some tutorial. (Activated IPV4 as Parameter)
The device does not receive anything. Strange #2.
On the Windows PC I have VirtualBox installed with an ubuntu as guest.
I start Netcat within it and start a UDP session. Every single Text I type in appears perfectly in the device. Strange #3.
Now I am confused and could need some help.
What do I miss? Is there any setting in Windows that prevents simple UDP Packets (No Broadcast) from being sent to any host in the same network?
I googled the net but did not find any clue.
EDIT:
The PC seems not to be the problem (maybe). I did a packet recording with the fritzbox and the UDP packets arrive there. They just do not seem to reach any wireless device in my home network.
I still did not figure out the exact problem, but I think it is related to either my Fritzbox and/or my computers "relation" to it. After I updated my Windows 10 with the anniversary update, my PC got a new IP assigned. Now everything works.

Ping between two different VMs on two different computers

I have two physical computers (windows 8 each of them) connected in a lan network. In both computers I have installed Oracle virtual box with windows server 2008. I want to ping from one Virtual Machine to the other one located in the other computer. How can I do it? For some reason I have the same IP on both virtual machines.
Maybe you have got the same MAC (hardware manufacturer's unique code) on your network interfaces in your two VMs so they are indistinguishable. You can check like this, and make a new random MAC address by clicking the green icon:
The VMs are likely on their own private networks behind software routers run by the VM program. Therefore, they are not visible to each other. This is the "NAT" (Network Address Translation") mode.
It's exactly as if two computers are behind two different DSL netboxes in two different homes. You cannot ping one from the other. You can only ping the netbox routers if you know their IP address.
To be able to ping between the two VMs, they need to take ownership of the host network card. This is called "Bridged Networking" in VirtualBox. Your host will be unable to use this network address as long as the guest VM is running.
Connect the virtual computers in the same lan network as the physical computers are!

How do I set up visual studio Remote Debugger to go over Ethernet?

I want to debug an app remotely on Windows RT (though this applies to any remote debugging, I guess), I don't want to open up my WiFi connection wide or handle complex software configuration every time I connect (firewall etc.).
I thought that maybe by using an Ethernet connection between my Surface and my dev machine, I could make the remote debugging work on top of that. Installing an Ethernet USB dongle on top of Surface seems to be easy, but I can't figure out how to make my dev machine actually find the Surface computer on it.
My set up is simple, dev machine connected to ethernet cable, connected to USB dongle, connected to Surface (Windows RT). Even when disabling WiFi, the remote debugger cannot find the debugee.
Do I need to manually set up the IP address or something?
Do I need to manually set up the IP address or something?
That's what I was thinking. What happens when you try to ping one machine from the the other? Does either machine run a DHCP server? If not you could run a DHCP server (probably on your dev machine) or setup a static IP address. Setting up DHCP may be harder at first but more convenient if you need to connect your tablet to other networks.
For testing it might be helpful to wire both devices to a router so you can configure and test Remote Debugging separately.

How to access cisco connection on Win7 from Mac OS X on local network

I've really benefitted from all the answers out here and now it's my turn to ask for help.
My company uses CISCO VPN. They won't give me the Shared Secret for the group so I am forced to use the windows VM to connect to my work network.
I've tried using the MAC CISCO ISPEC but there it is. Anyway, I'd like to use the connection in my windows vm from my MAC side. I tried setting up a openVPN server on the windows and connecting to that from MAC and connect the CISCO vpn. All a no go.
So any suggestions will be very welcome.
Thanks all.
Well it might sound strange but you're going to have to setup 2 virtual NICs on the virtual machine. The first NIC is going to be bridged with the real physical NIC on the OSX box and that's going to be your outside interface. The next virtual NIC is going to be a host-only and this is going to be your inside interface. This is the one you'll use for OSX to connect through your windows machine. Then you'll need to remove all IP and DHCP configuration from your physical NIC on OSX to let the virtual machine use that NIC.
Every time you want to use the VM and the VPN you're going to have to remove the config on your physical NIC in OSX and then re-add it when you're done.
The windows machine will need to use internet connection sharing to allow OSX to use its VPN connection.

Resources