Using an Ethernet cable to connect an Ubuntu 18.10 computer to a Windows 7 computer
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I believe modern Ethernet adapters can switch 'gender' as needed, so I can connect two computers with a standard straight through cable. I have had a go at following the advice on
here
but am not getting very far. Can anyone give me instructions for this pair of operating systems?
ethernet
New contributor
add a comment |Â
up vote
0
down vote
favorite
I believe modern Ethernet adapters can switch 'gender' as needed, so I can connect two computers with a standard straight through cable. I have had a go at following the advice on
here
but am not getting very far. Can anyone give me instructions for this pair of operating systems?
ethernet
New contributor
How far did you get? What problem did you encounter?
â NickD
2 hours ago
Nothing happened, I wasn't sure what to do after making those settings. I then tried a different tack and installed NitroShare on both. Initially I got "Unable to listen on port 40818", but that went (no thanks to anything that I did) and I have now successfully sent a file from Linux to Windows which appeared in DownloadsNitroShare. If I try running NitroShare on Windows in order to send a file back, I get "Unable to listen on port 40818". Others trying this might like to know whether they need to fiddle with the "Wired Settings" like I did or whether just using NitroShare would be enough.
â ChrisOfBristol
1 hour ago
Instead of assuming, you should definitely check your network card hardware to make sure it supports crossover and regular connection. Best is to make or buy a crossover cable, better is to use a small switch or even a home-grade router w/ switch ports available.
â ivanivan
1 hour ago
It seems that it if you don't see much happening and start NS more than once, in some versions, instead of warning you of this, you just get the "Unable to listen.." message. Sorted when you shut the later instances. I've now got it to start properly on Windows, but it shows no devices, must be something I need to do to tell it what is connected...
â ChrisOfBristol
35 mins ago
OP, you should be able to do it with just about any Ethernet cable today. I began studying telecommunications in 2005 and as of today I have yet to see a Fast Ethernet or Gigabit Ethernet card that doesn't support Auto-MDIX. That said, one way you can test if it's the fault of an Ethernet card that doesn't support it, is by plugging both of your devices to your home modem's Ethernet ports (most gateways have a built-in switch) -- if they can see each other through the switch but not directly, then it is your Ethernet cards' fault and you'll need a crossover cable.
â RAKK
2 mins ago
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I believe modern Ethernet adapters can switch 'gender' as needed, so I can connect two computers with a standard straight through cable. I have had a go at following the advice on
here
but am not getting very far. Can anyone give me instructions for this pair of operating systems?
ethernet
New contributor
I believe modern Ethernet adapters can switch 'gender' as needed, so I can connect two computers with a standard straight through cable. I have had a go at following the advice on
here
but am not getting very far. Can anyone give me instructions for this pair of operating systems?
ethernet
ethernet
New contributor
New contributor
edited 14 mins ago
New contributor
asked 2 hours ago
ChrisOfBristol
111
111
New contributor
New contributor
How far did you get? What problem did you encounter?
â NickD
2 hours ago
Nothing happened, I wasn't sure what to do after making those settings. I then tried a different tack and installed NitroShare on both. Initially I got "Unable to listen on port 40818", but that went (no thanks to anything that I did) and I have now successfully sent a file from Linux to Windows which appeared in DownloadsNitroShare. If I try running NitroShare on Windows in order to send a file back, I get "Unable to listen on port 40818". Others trying this might like to know whether they need to fiddle with the "Wired Settings" like I did or whether just using NitroShare would be enough.
â ChrisOfBristol
1 hour ago
Instead of assuming, you should definitely check your network card hardware to make sure it supports crossover and regular connection. Best is to make or buy a crossover cable, better is to use a small switch or even a home-grade router w/ switch ports available.
â ivanivan
1 hour ago
It seems that it if you don't see much happening and start NS more than once, in some versions, instead of warning you of this, you just get the "Unable to listen.." message. Sorted when you shut the later instances. I've now got it to start properly on Windows, but it shows no devices, must be something I need to do to tell it what is connected...
â ChrisOfBristol
35 mins ago
OP, you should be able to do it with just about any Ethernet cable today. I began studying telecommunications in 2005 and as of today I have yet to see a Fast Ethernet or Gigabit Ethernet card that doesn't support Auto-MDIX. That said, one way you can test if it's the fault of an Ethernet card that doesn't support it, is by plugging both of your devices to your home modem's Ethernet ports (most gateways have a built-in switch) -- if they can see each other through the switch but not directly, then it is your Ethernet cards' fault and you'll need a crossover cable.
â RAKK
2 mins ago
add a comment |Â
How far did you get? What problem did you encounter?
â NickD
2 hours ago
Nothing happened, I wasn't sure what to do after making those settings. I then tried a different tack and installed NitroShare on both. Initially I got "Unable to listen on port 40818", but that went (no thanks to anything that I did) and I have now successfully sent a file from Linux to Windows which appeared in DownloadsNitroShare. If I try running NitroShare on Windows in order to send a file back, I get "Unable to listen on port 40818". Others trying this might like to know whether they need to fiddle with the "Wired Settings" like I did or whether just using NitroShare would be enough.
â ChrisOfBristol
1 hour ago
Instead of assuming, you should definitely check your network card hardware to make sure it supports crossover and regular connection. Best is to make or buy a crossover cable, better is to use a small switch or even a home-grade router w/ switch ports available.
â ivanivan
1 hour ago
It seems that it if you don't see much happening and start NS more than once, in some versions, instead of warning you of this, you just get the "Unable to listen.." message. Sorted when you shut the later instances. I've now got it to start properly on Windows, but it shows no devices, must be something I need to do to tell it what is connected...
â ChrisOfBristol
35 mins ago
OP, you should be able to do it with just about any Ethernet cable today. I began studying telecommunications in 2005 and as of today I have yet to see a Fast Ethernet or Gigabit Ethernet card that doesn't support Auto-MDIX. That said, one way you can test if it's the fault of an Ethernet card that doesn't support it, is by plugging both of your devices to your home modem's Ethernet ports (most gateways have a built-in switch) -- if they can see each other through the switch but not directly, then it is your Ethernet cards' fault and you'll need a crossover cable.
â RAKK
2 mins ago
How far did you get? What problem did you encounter?
â NickD
2 hours ago
How far did you get? What problem did you encounter?
â NickD
2 hours ago
Nothing happened, I wasn't sure what to do after making those settings. I then tried a different tack and installed NitroShare on both. Initially I got "Unable to listen on port 40818", but that went (no thanks to anything that I did) and I have now successfully sent a file from Linux to Windows which appeared in DownloadsNitroShare. If I try running NitroShare on Windows in order to send a file back, I get "Unable to listen on port 40818". Others trying this might like to know whether they need to fiddle with the "Wired Settings" like I did or whether just using NitroShare would be enough.
â ChrisOfBristol
1 hour ago
Nothing happened, I wasn't sure what to do after making those settings. I then tried a different tack and installed NitroShare on both. Initially I got "Unable to listen on port 40818", but that went (no thanks to anything that I did) and I have now successfully sent a file from Linux to Windows which appeared in DownloadsNitroShare. If I try running NitroShare on Windows in order to send a file back, I get "Unable to listen on port 40818". Others trying this might like to know whether they need to fiddle with the "Wired Settings" like I did or whether just using NitroShare would be enough.
â ChrisOfBristol
1 hour ago
Instead of assuming, you should definitely check your network card hardware to make sure it supports crossover and regular connection. Best is to make or buy a crossover cable, better is to use a small switch or even a home-grade router w/ switch ports available.
â ivanivan
1 hour ago
Instead of assuming, you should definitely check your network card hardware to make sure it supports crossover and regular connection. Best is to make or buy a crossover cable, better is to use a small switch or even a home-grade router w/ switch ports available.
â ivanivan
1 hour ago
It seems that it if you don't see much happening and start NS more than once, in some versions, instead of warning you of this, you just get the "Unable to listen.." message. Sorted when you shut the later instances. I've now got it to start properly on Windows, but it shows no devices, must be something I need to do to tell it what is connected...
â ChrisOfBristol
35 mins ago
It seems that it if you don't see much happening and start NS more than once, in some versions, instead of warning you of this, you just get the "Unable to listen.." message. Sorted when you shut the later instances. I've now got it to start properly on Windows, but it shows no devices, must be something I need to do to tell it what is connected...
â ChrisOfBristol
35 mins ago
OP, you should be able to do it with just about any Ethernet cable today. I began studying telecommunications in 2005 and as of today I have yet to see a Fast Ethernet or Gigabit Ethernet card that doesn't support Auto-MDIX. That said, one way you can test if it's the fault of an Ethernet card that doesn't support it, is by plugging both of your devices to your home modem's Ethernet ports (most gateways have a built-in switch) -- if they can see each other through the switch but not directly, then it is your Ethernet cards' fault and you'll need a crossover cable.
â RAKK
2 mins ago
OP, you should be able to do it with just about any Ethernet cable today. I began studying telecommunications in 2005 and as of today I have yet to see a Fast Ethernet or Gigabit Ethernet card that doesn't support Auto-MDIX. That said, one way you can test if it's the fault of an Ethernet card that doesn't support it, is by plugging both of your devices to your home modem's Ethernet ports (most gateways have a built-in switch) -- if they can see each other through the switch but not directly, then it is your Ethernet cards' fault and you'll need a crossover cable.
â RAKK
2 mins ago
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
ChrisOfBristol is a new contributor. Be nice, and check out our Code of Conduct.
ChrisOfBristol is a new contributor. Be nice, and check out our Code of Conduct.
ChrisOfBristol is a new contributor. Be nice, and check out our Code of Conduct.
ChrisOfBristol is a new contributor. Be nice, and check out our Code of Conduct.
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f479450%2fusing-an-ethernet-cable-to-connect-an-ubuntu-18-10-computer-to-a-windows-7-compu%23new-answer', 'question_page');
);
Post as a guest
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
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
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
How far did you get? What problem did you encounter?
â NickD
2 hours ago
Nothing happened, I wasn't sure what to do after making those settings. I then tried a different tack and installed NitroShare on both. Initially I got "Unable to listen on port 40818", but that went (no thanks to anything that I did) and I have now successfully sent a file from Linux to Windows which appeared in DownloadsNitroShare. If I try running NitroShare on Windows in order to send a file back, I get "Unable to listen on port 40818". Others trying this might like to know whether they need to fiddle with the "Wired Settings" like I did or whether just using NitroShare would be enough.
â ChrisOfBristol
1 hour ago
Instead of assuming, you should definitely check your network card hardware to make sure it supports crossover and regular connection. Best is to make or buy a crossover cable, better is to use a small switch or even a home-grade router w/ switch ports available.
â ivanivan
1 hour ago
It seems that it if you don't see much happening and start NS more than once, in some versions, instead of warning you of this, you just get the "Unable to listen.." message. Sorted when you shut the later instances. I've now got it to start properly on Windows, but it shows no devices, must be something I need to do to tell it what is connected...
â ChrisOfBristol
35 mins ago
OP, you should be able to do it with just about any Ethernet cable today. I began studying telecommunications in 2005 and as of today I have yet to see a Fast Ethernet or Gigabit Ethernet card that doesn't support Auto-MDIX. That said, one way you can test if it's the fault of an Ethernet card that doesn't support it, is by plugging both of your devices to your home modem's Ethernet ports (most gateways have a built-in switch) -- if they can see each other through the switch but not directly, then it is your Ethernet cards' fault and you'll need a crossover cable.
â RAKK
2 mins ago