Connect Ubuntu Server 16.04 to Windows 10 using Ethernet cable
0
EDIT:
ipconfig on Windows:
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::49d7:ec19:199f:b968%13
Autoconfiguration IPv4 Address. . : 169.254.185.104
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
SITUATION:
I was using Ubuntu Desktop 16.04 as my PC's OS for a long time. And there were no problems with Ethernet connection with my server that is running on Ubuntu Server 16.04.
But now I have to use Windows 10 as my OS. I didn't change settings on my server:
sudo nano /etc/natwork/intrfaces:
# The loopback network interfaces
auto lo
iface lo inet loopback
# The primary network interfaces
auto enp4s0f0
iface enp4s0f0 inet static
address 192.168.10.2
netmask 255.255.255.0
network 192.168.10.0
broadcast 192.168.10.255
PROBLEM:
When I run ping 192.168.10.2 -t in CMD on my PC I get:
Pinging 192.168.10.2 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Ping statistics for 192.168.10.2:
Packets: Sent = 5, Received = 0, Lost = 5 (100% loss),
So there is no connection, hovewer the Ethernet cable is working:
QUESTION:
How to solve this ploblem and why I'm getting this error?
Thanks for helping
16.04 networking server windows-10 ethernet
asked Dec 12 '18 at 19:14
Max MikhalchukMax Mikhalchuk
418
add a comment |
0
EDIT:
ipconfig on Windows:
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::49d7:ec19:199f:b968%13
Autoconfiguration IPv4 Address. . : 169.254.185.104
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
SITUATION:
I was using Ubuntu Desktop 16.04 as my PC's OS for a long time. And there were no problems with Ethernet connection with my server that is running on Ubuntu Server 16.04.
But now I have to use Windows 10 as my OS. I didn't change settings on my server:
sudo nano /etc/natwork/intrfaces:
# The loopback network interfaces
auto lo
iface lo inet loopback
# The primary network interfaces
auto enp4s0f0
iface enp4s0f0 inet static
address 192.168.10.2
netmask 255.255.255.0
network 192.168.10.0
broadcast 192.168.10.255
PROBLEM:
When I run ping 192.168.10.2 -t in CMD on my PC I get:
Pinging 192.168.10.2 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Ping statistics for 192.168.10.2:
Packets: Sent = 5, Received = 0, Lost = 5 (100% loss),
So there is no connection, hovewer the Ethernet cable is working:
QUESTION:
How to solve this ploblem and why I'm getting this error?
Thanks for helping
16.04 networking server windows-10 ethernet
asked Dec 12 '18 at 19:14
Max MikhalchukMax Mikhalchuk
418
2
Are you sure that your computer is on the same subnet? General failure usually means your Windows configuration is done incorrectly due to MTU or some other manual setup change.
– Thomas Ward♦
Dec 12 '18 at 19:16
@ThomasWard it seems that you're right. Windows subnet is255.255.0.0and Ubuntu subnet is255.255.255.0. So, I just need to change netmask on Ubuntu to255.255.0.0?
– Max Mikhalchuk
Dec 12 '18 at 19:33
1
Your WIndows OS only has an APIPA address, which will make it not possible to connect to 192.168.10.2. If you do not have a DHCP server on the network, assign a static IP to your windows machine (like 192.168.10.3/255.255.255.0). Make sure the address you assign is not in use by other devices.
– Oliver R.
Dec 12 '18 at 21:10
add a comment |
0
0
0
EDIT:
ipconfig on Windows:
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::49d7:ec19:199f:b968%13
Autoconfiguration IPv4 Address. . : 169.254.185.104
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
SITUATION:
I was using Ubuntu Desktop 16.04 as my PC's OS for a long time. And there were no problems with Ethernet connection with my server that is running on Ubuntu Server 16.04.
But now I have to use Windows 10 as my OS. I didn't change settings on my server:
sudo nano /etc/natwork/intrfaces:
# The loopback network interfaces
auto lo
iface lo inet loopback
# The primary network interfaces
auto enp4s0f0
iface enp4s0f0 inet static
address 192.168.10.2
netmask 255.255.255.0
network 192.168.10.0
broadcast 192.168.10.255
PROBLEM:
When I run ping 192.168.10.2 -t in CMD on my PC I get:
Pinging 192.168.10.2 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Ping statistics for 192.168.10.2:
Packets: Sent = 5, Received = 0, Lost = 5 (100% loss),
So there is no connection, hovewer the Ethernet cable is working:
QUESTION:
How to solve this ploblem and why I'm getting this error?
Thanks for helping
16.04 networking server windows-10 ethernet
asked Dec 12 '18 at 19:14
Max MikhalchukMax Mikhalchuk
418
EDIT:
ipconfig on Windows:
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::49d7:ec19:199f:b968%13
Autoconfiguration IPv4 Address. . : 169.254.185.104
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
SITUATION:
I was using Ubuntu Desktop 16.04 as my PC's OS for a long time. And there were no problems with Ethernet connection with my server that is running on Ubuntu Server 16.04.
But now I have to use Windows 10 as my OS. I didn't change settings on my server:
sudo nano /etc/natwork/intrfaces:
# The loopback network interfaces
auto lo
iface lo inet loopback
# The primary network interfaces
auto enp4s0f0
iface enp4s0f0 inet static
address 192.168.10.2
netmask 255.255.255.0
network 192.168.10.0
broadcast 192.168.10.255
PROBLEM:
When I run ping 192.168.10.2 -t in CMD on my PC I get:
Pinging 192.168.10.2 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Ping statistics for 192.168.10.2:
Packets: Sent = 5, Received = 0, Lost = 5 (100% loss),
So there is no connection, hovewer the Ethernet cable is working:
QUESTION:
How to solve this ploblem and why I'm getting this error?
Thanks for helping
16.04 networking server windows-10 ethernet
16.04 networking server windows-10 ethernet
asked Dec 12 '18 at 19:14
Max MikhalchukMax Mikhalchuk
418
asked Dec 12 '18 at 19:14
Max MikhalchukMax Mikhalchuk
418
edited Dec 12 '18 at 19:30
Max Mikhalchuk
asked Dec 12 '18 at 19:14
Max MikhalchukMax Mikhalchuk
418
asked Dec 12 '18 at 19:14
Max MikhalchukMax Mikhalchuk
418
asked Dec 12 '18 at 19:14
Max MikhalchukMax Mikhalchuk
418
418
2
Are you sure that your computer is on the same subnet? General failure usually means your Windows configuration is done incorrectly due to MTU or some other manual setup change.
– Thomas Ward♦
Dec 12 '18 at 19:16
@ThomasWard it seems that you're right. Windows subnet is255.255.0.0and Ubuntu subnet is255.255.255.0. So, I just need to change netmask on Ubuntu to255.255.0.0?
– Max Mikhalchuk
Dec 12 '18 at 19:33
1
Your WIndows OS only has an APIPA address, which will make it not possible to connect to 192.168.10.2. If you do not have a DHCP server on the network, assign a static IP to your windows machine (like 192.168.10.3/255.255.255.0). Make sure the address you assign is not in use by other devices.
– Oliver R.
Dec 12 '18 at 21:10
add a comment |
2
Are you sure that your computer is on the same subnet? General failure usually means your Windows configuration is done incorrectly due to MTU or some other manual setup change.
– Thomas Ward♦
Dec 12 '18 at 19:16
@ThomasWard it seems that you're right. Windows subnet is255.255.0.0and Ubuntu subnet is255.255.255.0. So, I just need to change netmask on Ubuntu to255.255.0.0?
– Max Mikhalchuk
Dec 12 '18 at 19:33
1
Your WIndows OS only has an APIPA address, which will make it not possible to connect to 192.168.10.2. If you do not have a DHCP server on the network, assign a static IP to your windows machine (like 192.168.10.3/255.255.255.0). Make sure the address you assign is not in use by other devices.
– Oliver R.
Dec 12 '18 at 21:10
2
2
Are you sure that your computer is on the same subnet? General failure usually means your Windows configuration is done incorrectly due to MTU or some other manual setup change.
– Thomas Ward♦
Dec 12 '18 at 19:16
Are you sure that your computer is on the same subnet? General failure usually means your Windows configuration is done incorrectly due to MTU or some other manual setup change.
– Thomas Ward♦
Dec 12 '18 at 19:16
@ThomasWard it seems that you're right. Windows subnet is
255.255.0.0 and Ubuntu subnet is 255.255.255.0. So, I just need to change netmask on Ubuntu to 255.255.0.0?– Max Mikhalchuk
Dec 12 '18 at 19:33
@ThomasWard it seems that you're right. Windows subnet is
255.255.0.0 and Ubuntu subnet is 255.255.255.0. So, I just need to change netmask on Ubuntu to 255.255.0.0?– Max Mikhalchuk
Dec 12 '18 at 19:33
1
1
Your WIndows OS only has an APIPA address, which will make it not possible to connect to 192.168.10.2. If you do not have a DHCP server on the network, assign a static IP to your windows machine (like 192.168.10.3/255.255.255.0). Make sure the address you assign is not in use by other devices.
– Oliver R.
Dec 12 '18 at 21:10
Your WIndows OS only has an APIPA address, which will make it not possible to connect to 192.168.10.2. If you do not have a DHCP server on the network, assign a static IP to your windows machine (like 192.168.10.3/255.255.255.0). Make sure the address you assign is not in use by other devices.
– Oliver R.
Dec 12 '18 at 21:10
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1100427%2fconnect-ubuntu-server-16-04-to-windows-10-using-ethernet-cable%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1100427%2fconnect-ubuntu-server-16-04-to-windows-10-using-ethernet-cable%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Are you sure that your computer is on the same subnet? General failure usually means your Windows configuration is done incorrectly due to MTU or some other manual setup change.
– Thomas Ward♦
Dec 12 '18 at 19:16
@ThomasWard it seems that you're right. Windows subnet is
255.255.0.0and Ubuntu subnet is255.255.255.0. So, I just need to change netmask on Ubuntu to255.255.0.0?– Max Mikhalchuk
Dec 12 '18 at 19:33
1
Your WIndows OS only has an APIPA address, which will make it not possible to connect to 192.168.10.2. If you do not have a DHCP server on the network, assign a static IP to your windows machine (like 192.168.10.3/255.255.255.0). Make sure the address you assign is not in use by other devices.
– Oliver R.
Dec 12 '18 at 21:10