Unable to connect via direct connect.
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
Jeff.
Unable to connect via direct connect.
ok, so i have 1 windows 7 laptop that is able to connect to Wifi and i have a fresh Mint 14 laptop that is all i need to do i plug into a direct connection for like 1 minute to download/activate the wireless drivers. I have set the Win7 laptop to share its connection, but when i plug into it via ethernet it is never able to get a connection, What am i doing wrong here? Im open for any suggestions or windows programs if anyone knows of any to make this easy... I would really love to get my Mint up and going. i appreciate any input
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
-
billmc
Re: Unable to connect via direct connect.
Do you have access to your network's router? Does it have ethernet ports you can plug into? I assume you're doing this at home and you can access your router/modem. There should be at least one ethernet connection on it you can plug into. Plug your Mint laptop directly into the router. Normally, your router is configured to be a dhcp server and your eth0 port in Mint should be configured to get an address via dhcp.
After you plug in your cable, open a terminal window and issue the following command -> sudo ifconfig -a
This is what my output looks like:
sudo ifconfig -a
[sudo] password for bill:
eth0 Link encap:Ethernet HWaddr 50:e5:49:3c:cb:3d
inet addr:192.168.1.7 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::52e5:49ff:fe3c:cb3d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:747056 errors:0 dropped:0 overruns:0 frame:0
TX packets:516514 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:597519452 (597.5 MB) TX bytes:39683744 (39.6 MB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:11652 errors:0 dropped:0 overruns:0 frame:0
TX packets:11652 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1426356 (1.4 MB) TX bytes:1426356 (1.4 MB)
wlan0 Link encap:Ethernet HWaddr 00:18:e7
b5:93
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Look to see if eth0 has an address asigned. If it does, you should be good to go, if it doesn't issue the following command -> sudo dhclient eth0
This will cause the dhclient program to request an address from the dhcp server. You can double check its received an address by running the ifconfig command again.
Going through your windows box, I suspect you are using a "straight through" rather than a "crossover" ethernet cable. You either need to use a crossover cable for a direct connection, or connect both the windows box ethernet and the mint box eithernet to a switch/router to perform the crossover for you.
After you plug in your cable, open a terminal window and issue the following command -> sudo ifconfig -a
This is what my output looks like:
sudo ifconfig -a
[sudo] password for bill:
eth0 Link encap:Ethernet HWaddr 50:e5:49:3c:cb:3d
inet addr:192.168.1.7 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::52e5:49ff:fe3c:cb3d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:747056 errors:0 dropped:0 overruns:0 frame:0
TX packets:516514 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:597519452 (597.5 MB) TX bytes:39683744 (39.6 MB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:11652 errors:0 dropped:0 overruns:0 frame:0
TX packets:11652 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1426356 (1.4 MB) TX bytes:1426356 (1.4 MB)
wlan0 Link encap:Ethernet HWaddr 00:18:e7
b5:93 UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Look to see if eth0 has an address asigned. If it does, you should be good to go, if it doesn't issue the following command -> sudo dhclient eth0
This will cause the dhclient program to request an address from the dhcp server. You can double check its received an address by running the ifconfig command again.
Going through your windows box, I suspect you are using a "straight through" rather than a "crossover" ethernet cable. You either need to use a crossover cable for a direct connection, or connect both the windows box ethernet and the mint box eithernet to a switch/router to perform the crossover for you.