Sharing a Windows 7 wifi connection with a Raspberry PI
up vote
2
down vote
favorite
I have a Windows 7 PC that is using a Wireless network connection that I want to share on the PI. I have a working CAT 5 cable that I am using to connect the Win 7 PC to the PI. I have configured the Windows 7 PC to share the network, Windows states: Unidentified network shared.
However on the PI I get nothing, I've tried several IP based commands and I can't seem to identify anything.
I had it working from a direct cable before, but now I'm using the cable from the PC I cant seem to get it to work.
I have followed the commands on the R.Pi site, but anything I try doesn't seem to work.
I'm using Raspbian “Wheezy”.
windows-7 linux internet-connection connection-sharing raspberry-pi
edited Dec 9 '12 at 14:43
jonsca
2,897112539
asked Dec 8 '12 at 23:57
Welsh King
11114
add a comment |
up vote
2
down vote
favorite
I have a Windows 7 PC that is using a Wireless network connection that I want to share on the PI. I have a working CAT 5 cable that I am using to connect the Win 7 PC to the PI. I have configured the Windows 7 PC to share the network, Windows states: Unidentified network shared.
However on the PI I get nothing, I've tried several IP based commands and I can't seem to identify anything.
I had it working from a direct cable before, but now I'm using the cable from the PC I cant seem to get it to work.
I have followed the commands on the R.Pi site, but anything I try doesn't seem to work.
I'm using Raspbian “Wheezy”.
windows-7 linux internet-connection connection-sharing raspberry-pi
edited Dec 9 '12 at 14:43
jonsca
2,897112539
asked Dec 8 '12 at 23:57
Welsh King
11114
Apparently the NIC on the R-Pi is auto-sensing. So plain/cross cables should not be the problem here. Might want to add that to the post before you get people asking you to try it with a cross cable. Also, does the Pi detect link? Does the PC detect it? What happens if you plug either end of the cable in a switch, does the link come up (if not, faulty cable, not faulty type but broken).
– Hennes
Dec 9 '12 at 0:04
hi ive started trying 'sudo /etc/init.d/networking stop|start and its now saying "DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6, it tries this several times and then drops out with No DHCPOFFERS recieved. Unable to obtain a lease on first try. Exiting. Failed to bring up eth0.
– Welsh King
Dec 9 '12 at 0:21
DHCP on Windows 7 is turned on
– Welsh King
Dec 9 '12 at 0:28
What happens if you set up a static route (pi: ifconfig eth0 172.16.1.1 netmask 255.255.255.0, windows same with 172.16.1.2, set up routes (in case those do not get set automatically) and try to ping the other? That should allow ping.
– Hennes
Dec 9 '12 at 0:36
ive just tried something simlar setting both to be the same. The network service starts, but nothing works, when i do a ping it just sits there.
– Welsh King
Dec 9 '12 at 0:41
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I have a Windows 7 PC that is using a Wireless network connection that I want to share on the PI. I have a working CAT 5 cable that I am using to connect the Win 7 PC to the PI. I have configured the Windows 7 PC to share the network, Windows states: Unidentified network shared.
However on the PI I get nothing, I've tried several IP based commands and I can't seem to identify anything.
I had it working from a direct cable before, but now I'm using the cable from the PC I cant seem to get it to work.
I have followed the commands on the R.Pi site, but anything I try doesn't seem to work.
I'm using Raspbian “Wheezy”.
windows-7 linux internet-connection connection-sharing raspberry-pi
edited Dec 9 '12 at 14:43
jonsca
2,897112539
asked Dec 8 '12 at 23:57
Welsh King
11114
I have a Windows 7 PC that is using a Wireless network connection that I want to share on the PI. I have a working CAT 5 cable that I am using to connect the Win 7 PC to the PI. I have configured the Windows 7 PC to share the network, Windows states: Unidentified network shared.
However on the PI I get nothing, I've tried several IP based commands and I can't seem to identify anything.
I had it working from a direct cable before, but now I'm using the cable from the PC I cant seem to get it to work.
I have followed the commands on the R.Pi site, but anything I try doesn't seem to work.
I'm using Raspbian “Wheezy”.
windows-7 linux internet-connection connection-sharing raspberry-pi
windows-7 linux internet-connection connection-sharing raspberry-pi
edited Dec 9 '12 at 14:43
jonsca
2,897112539
asked Dec 8 '12 at 23:57
Welsh King
11114
edited Dec 9 '12 at 14:43
jonsca
2,897112539
asked Dec 8 '12 at 23:57
Welsh King
11114
edited Dec 9 '12 at 14:43
jonsca
2,897112539
edited Dec 9 '12 at 14:43
jonsca
2,897112539
edited Dec 9 '12 at 14:43
jonsca
2,897112539
2,897112539
asked Dec 8 '12 at 23:57
Welsh King
11114
asked Dec 8 '12 at 23:57
Welsh King
11114
asked Dec 8 '12 at 23:57
Welsh King
11114
11114
Apparently the NIC on the R-Pi is auto-sensing. So plain/cross cables should not be the problem here. Might want to add that to the post before you get people asking you to try it with a cross cable. Also, does the Pi detect link? Does the PC detect it? What happens if you plug either end of the cable in a switch, does the link come up (if not, faulty cable, not faulty type but broken).
– Hennes
Dec 9 '12 at 0:04
hi ive started trying 'sudo /etc/init.d/networking stop|start and its now saying "DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6, it tries this several times and then drops out with No DHCPOFFERS recieved. Unable to obtain a lease on first try. Exiting. Failed to bring up eth0.
– Welsh King
Dec 9 '12 at 0:21
DHCP on Windows 7 is turned on
– Welsh King
Dec 9 '12 at 0:28
What happens if you set up a static route (pi: ifconfig eth0 172.16.1.1 netmask 255.255.255.0, windows same with 172.16.1.2, set up routes (in case those do not get set automatically) and try to ping the other? That should allow ping.
– Hennes
Dec 9 '12 at 0:36
ive just tried something simlar setting both to be the same. The network service starts, but nothing works, when i do a ping it just sits there.
– Welsh King
Dec 9 '12 at 0:41
add a comment |
Apparently the NIC on the R-Pi is auto-sensing. So plain/cross cables should not be the problem here. Might want to add that to the post before you get people asking you to try it with a cross cable. Also, does the Pi detect link? Does the PC detect it? What happens if you plug either end of the cable in a switch, does the link come up (if not, faulty cable, not faulty type but broken).
– Hennes
Dec 9 '12 at 0:04
hi ive started trying 'sudo /etc/init.d/networking stop|start and its now saying "DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6, it tries this several times and then drops out with No DHCPOFFERS recieved. Unable to obtain a lease on first try. Exiting. Failed to bring up eth0.
– Welsh King
Dec 9 '12 at 0:21
DHCP on Windows 7 is turned on
– Welsh King
Dec 9 '12 at 0:28
What happens if you set up a static route (pi: ifconfig eth0 172.16.1.1 netmask 255.255.255.0, windows same with 172.16.1.2, set up routes (in case those do not get set automatically) and try to ping the other? That should allow ping.
– Hennes
Dec 9 '12 at 0:36
ive just tried something simlar setting both to be the same. The network service starts, but nothing works, when i do a ping it just sits there.
– Welsh King
Dec 9 '12 at 0:41
Apparently the NIC on the R-Pi is auto-sensing. So plain/cross cables should not be the problem here. Might want to add that to the post before you get people asking you to try it with a cross cable. Also, does the Pi detect link? Does the PC detect it? What happens if you plug either end of the cable in a switch, does the link come up (if not, faulty cable, not faulty type but broken).
– Hennes
Dec 9 '12 at 0:04
Apparently the NIC on the R-Pi is auto-sensing. So plain/cross cables should not be the problem here. Might want to add that to the post before you get people asking you to try it with a cross cable. Also, does the Pi detect link? Does the PC detect it? What happens if you plug either end of the cable in a switch, does the link come up (if not, faulty cable, not faulty type but broken).
– Hennes
Dec 9 '12 at 0:04
hi ive started trying 'sudo /etc/init.d/networking stop|start and its now saying "DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6, it tries this several times and then drops out with No DHCPOFFERS recieved. Unable to obtain a lease on first try. Exiting. Failed to bring up eth0.
– Welsh King
Dec 9 '12 at 0:21
hi ive started trying 'sudo /etc/init.d/networking stop|start and its now saying "DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6, it tries this several times and then drops out with No DHCPOFFERS recieved. Unable to obtain a lease on first try. Exiting. Failed to bring up eth0.
– Welsh King
Dec 9 '12 at 0:21
DHCP on Windows 7 is turned on
– Welsh King
Dec 9 '12 at 0:28
DHCP on Windows 7 is turned on
– Welsh King
Dec 9 '12 at 0:28
What happens if you set up a static route (pi: ifconfig eth0 172.16.1.1 netmask 255.255.255.0, windows same with 172.16.1.2, set up routes (in case those do not get set automatically) and try to ping the other? That should allow ping.
– Hennes
Dec 9 '12 at 0:36
What happens if you set up a static route (pi: ifconfig eth0 172.16.1.1 netmask 255.255.255.0, windows same with 172.16.1.2, set up routes (in case those do not get set automatically) and try to ping the other? That should allow ping.
– Hennes
Dec 9 '12 at 0:36
ive just tried something simlar setting both to be the same. The network service starts, but nothing works, when i do a ping it just sits there.
– Welsh King
Dec 9 '12 at 0:41
ive just tried something simlar setting both to be the same. The network service starts, but nothing works, when i do a ping it just sits there.
– Welsh King
Dec 9 '12 at 0:41
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
The simplest solution would be to just enable ICS, but that does not seem to work with Win7 Starter Edition or if the NIC of the wireless adapter does not have any "share" option (perhaps caused by the network adapter driver).
Another way is to bridge the wireless and the wired connections by selecting them both and then just selecting the appropriate option from the context menu.
Or you could use e.g. Connectify to accomplish what you want, but that requires a software installation.
edited Mar 20 '17 at 10:17
Community♦
1
answered Dec 9 '12 at 13:59
mousio
618513
im using ICS on Windows 7 Premium, but when i use it it says it cant find DHCP "DHCPDISCOVER on eth0 to 255.255.255.255 port 67" Cant bridge the connection as it requires 2 lan connections.
– Welsh King
Dec 9 '12 at 15:01
add a comment |
up vote
0
down vote
On Windows 10 (which seems to have all the same network features):
- Right-click the WiFi icon on the taskbar.
- Open Network and sharing center.
- Select Change adapter settings on the left.
- Right-click the adapter you want to use and select Properties.
- Click Sharing.
- Click Allow other users to connect through this computer's internet connection.
- If necessary, select your ethernet port.
I use this when I need to configure a new install on my Raspberry Pi. It works like a charm. Plus the Pi does not need a crossover cable, as it configures that automatically.
edited Dec 27 '16 at 21:40
Kamil Maciorowski
23.2k155072
answered Dec 27 '16 at 17:53
user173724
314313
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
The simplest solution would be to just enable ICS, but that does not seem to work with Win7 Starter Edition or if the NIC of the wireless adapter does not have any "share" option (perhaps caused by the network adapter driver).
Another way is to bridge the wireless and the wired connections by selecting them both and then just selecting the appropriate option from the context menu.
Or you could use e.g. Connectify to accomplish what you want, but that requires a software installation.
edited Mar 20 '17 at 10:17
Community♦
1
answered Dec 9 '12 at 13:59
mousio
618513
im using ICS on Windows 7 Premium, but when i use it it says it cant find DHCP "DHCPDISCOVER on eth0 to 255.255.255.255 port 67" Cant bridge the connection as it requires 2 lan connections.
– Welsh King
Dec 9 '12 at 15:01
add a comment |
up vote
0
down vote
The simplest solution would be to just enable ICS, but that does not seem to work with Win7 Starter Edition or if the NIC of the wireless adapter does not have any "share" option (perhaps caused by the network adapter driver).
Another way is to bridge the wireless and the wired connections by selecting them both and then just selecting the appropriate option from the context menu.
Or you could use e.g. Connectify to accomplish what you want, but that requires a software installation.
edited Mar 20 '17 at 10:17
Community♦
1
answered Dec 9 '12 at 13:59
mousio
618513
im using ICS on Windows 7 Premium, but when i use it it says it cant find DHCP "DHCPDISCOVER on eth0 to 255.255.255.255 port 67" Cant bridge the connection as it requires 2 lan connections.
– Welsh King
Dec 9 '12 at 15:01
add a comment |
up vote
0
down vote
up vote
0
down vote
The simplest solution would be to just enable ICS, but that does not seem to work with Win7 Starter Edition or if the NIC of the wireless adapter does not have any "share" option (perhaps caused by the network adapter driver).
Another way is to bridge the wireless and the wired connections by selecting them both and then just selecting the appropriate option from the context menu.
Or you could use e.g. Connectify to accomplish what you want, but that requires a software installation.
edited Mar 20 '17 at 10:17
Community♦
1
answered Dec 9 '12 at 13:59
mousio
618513
The simplest solution would be to just enable ICS, but that does not seem to work with Win7 Starter Edition or if the NIC of the wireless adapter does not have any "share" option (perhaps caused by the network adapter driver).
Another way is to bridge the wireless and the wired connections by selecting them both and then just selecting the appropriate option from the context menu.
Or you could use e.g. Connectify to accomplish what you want, but that requires a software installation.
edited Mar 20 '17 at 10:17
Community♦
1
answered Dec 9 '12 at 13:59
mousio
618513
edited Mar 20 '17 at 10:17
Community♦
1
edited Mar 20 '17 at 10:17
Community♦
1
edited Mar 20 '17 at 10:17
Community♦
1
1
answered Dec 9 '12 at 13:59
mousio
618513
answered Dec 9 '12 at 13:59
mousio
618513
answered Dec 9 '12 at 13:59
mousio
618513
618513
im using ICS on Windows 7 Premium, but when i use it it says it cant find DHCP "DHCPDISCOVER on eth0 to 255.255.255.255 port 67" Cant bridge the connection as it requires 2 lan connections.
– Welsh King
Dec 9 '12 at 15:01
add a comment |
im using ICS on Windows 7 Premium, but when i use it it says it cant find DHCP "DHCPDISCOVER on eth0 to 255.255.255.255 port 67" Cant bridge the connection as it requires 2 lan connections.
– Welsh King
Dec 9 '12 at 15:01
im using ICS on Windows 7 Premium, but when i use it it says it cant find DHCP "DHCPDISCOVER on eth0 to 255.255.255.255 port 67" Cant bridge the connection as it requires 2 lan connections.
– Welsh King
Dec 9 '12 at 15:01
im using ICS on Windows 7 Premium, but when i use it it says it cant find DHCP "DHCPDISCOVER on eth0 to 255.255.255.255 port 67" Cant bridge the connection as it requires 2 lan connections.
– Welsh King
Dec 9 '12 at 15:01
add a comment |
up vote
0
down vote
On Windows 10 (which seems to have all the same network features):
- Right-click the WiFi icon on the taskbar.
- Open Network and sharing center.
- Select Change adapter settings on the left.
- Right-click the adapter you want to use and select Properties.
- Click Sharing.
- Click Allow other users to connect through this computer's internet connection.
- If necessary, select your ethernet port.
I use this when I need to configure a new install on my Raspberry Pi. It works like a charm. Plus the Pi does not need a crossover cable, as it configures that automatically.
edited Dec 27 '16 at 21:40
Kamil Maciorowski
23.2k155072
answered Dec 27 '16 at 17:53
user173724
314313
add a comment |
up vote
0
down vote
On Windows 10 (which seems to have all the same network features):
- Right-click the WiFi icon on the taskbar.
- Open Network and sharing center.
- Select Change adapter settings on the left.
- Right-click the adapter you want to use and select Properties.
- Click Sharing.
- Click Allow other users to connect through this computer's internet connection.
- If necessary, select your ethernet port.
I use this when I need to configure a new install on my Raspberry Pi. It works like a charm. Plus the Pi does not need a crossover cable, as it configures that automatically.
edited Dec 27 '16 at 21:40
Kamil Maciorowski
23.2k155072
answered Dec 27 '16 at 17:53
user173724
314313
add a comment |
up vote
0
down vote
up vote
0
down vote
On Windows 10 (which seems to have all the same network features):
- Right-click the WiFi icon on the taskbar.
- Open Network and sharing center.
- Select Change adapter settings on the left.
- Right-click the adapter you want to use and select Properties.
- Click Sharing.
- Click Allow other users to connect through this computer's internet connection.
- If necessary, select your ethernet port.
I use this when I need to configure a new install on my Raspberry Pi. It works like a charm. Plus the Pi does not need a crossover cable, as it configures that automatically.
edited Dec 27 '16 at 21:40
Kamil Maciorowski
23.2k155072
answered Dec 27 '16 at 17:53
user173724
314313
On Windows 10 (which seems to have all the same network features):
- Right-click the WiFi icon on the taskbar.
- Open Network and sharing center.
- Select Change adapter settings on the left.
- Right-click the adapter you want to use and select Properties.
- Click Sharing.
- Click Allow other users to connect through this computer's internet connection.
- If necessary, select your ethernet port.
I use this when I need to configure a new install on my Raspberry Pi. It works like a charm. Plus the Pi does not need a crossover cable, as it configures that automatically.
edited Dec 27 '16 at 21:40
Kamil Maciorowski
23.2k155072
answered Dec 27 '16 at 17:53
user173724
314313
edited Dec 27 '16 at 21:40
Kamil Maciorowski
23.2k155072
edited Dec 27 '16 at 21:40
Kamil Maciorowski
23.2k155072
edited Dec 27 '16 at 21:40
Kamil Maciorowski
23.2k155072
23.2k155072
answered Dec 27 '16 at 17:53
user173724
314313
answered Dec 27 '16 at 17:53
user173724
314313
answered Dec 27 '16 at 17:53
user173724
314313
314313
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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.
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%2fsuperuser.com%2fquestions%2f516808%2fsharing-a-windows-7-wifi-connection-with-a-raspberry-pi%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
Apparently the NIC on the R-Pi is auto-sensing. So plain/cross cables should not be the problem here. Might want to add that to the post before you get people asking you to try it with a cross cable. Also, does the Pi detect link? Does the PC detect it? What happens if you plug either end of the cable in a switch, does the link come up (if not, faulty cable, not faulty type but broken).
– Hennes
Dec 9 '12 at 0:04
hi ive started trying 'sudo /etc/init.d/networking stop|start and its now saying "DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6, it tries this several times and then drops out with No DHCPOFFERS recieved. Unable to obtain a lease on first try. Exiting. Failed to bring up eth0.
– Welsh King
Dec 9 '12 at 0:21
DHCP on Windows 7 is turned on
– Welsh King
Dec 9 '12 at 0:28
What happens if you set up a static route (pi: ifconfig eth0 172.16.1.1 netmask 255.255.255.0, windows same with 172.16.1.2, set up routes (in case those do not get set automatically) and try to ping the other? That should allow ping.
– Hennes
Dec 9 '12 at 0:36
ive just tried something simlar setting both to be the same. The network service starts, but nothing works, when i do a ping it just sits there.
– Welsh King
Dec 9 '12 at 0:41