I used to use a wireless network adapter, but I bought an ethernet cable. I attached it to the router, and plugged the other end into my pc, but nothing happens. I looked and my motherboard info says "Modem/LAN: No/Yes", so I went on my mobo disk to the LAN folder, and installed the driver. I don't see the driver in Device Manager, so I don't know if it installed or it doesn't show, but again, no wired connection. How do I set up the connection?
0
can't connect using ethernet cable
Started by beatlebryce, Apr 02 2009 06:18 AM
4 replies to this topic
#1 OFFLINE
-
- Members
-
- 126 posts
Advanced Member
- Gender:Male
- Location:CA
Posted 02 April 2009 - 06:18 AM
#2 OFFLINE
-
- Members
-
- 1,626 posts
Lets Get Dangerous
- Gender:Male
- Location:QLD,Australia
- Interests:PC, LOTRO
Posted 02 April 2009 - 08:27 AM
beatlebryce, on Apr 2 2009, 04:18 PM, said:
I used to use a wireless network adapter, but I bought an ethernet cable. I attached it to the router, and plugged the other end into my pc, but nothing happens. I looked and my motherboard info says "Modem/LAN: No/Yes", so I went on my mobo disk to the LAN folder, and installed the driver. I don't see the driver in Device Manager, so I don't know if it installed or it doesn't show, but again, no wired connection. How do I set up the connection?
Check your manual for setting the BIOS to enable on board LAN.
fireryone
There are 10 types of people in this world.
Those who understand binary, and those who don't.
There are 10 types of people in this world.
Those who understand binary, and those who don't.
#3 OFFLINE
-
- Members
-
- 431 posts
Advanced Member
- Gender:Male
- Location:South Carolina
Posted 02 April 2009 - 12:38 PM
You could also try right clicking on "Network Connections" on the desktop and selecting properties. Your LAN adapter should show up there if the drivers are installed for it. If you are logged in under an administrative account, you can right click the LAN adapter and select enable.
There's always an exception to the rule. I'm that exception.
Desktop ----- AMD Athlon 3700+ (2.64Ghz), 2GB DDR 400, ASUS A8N-SLI Premium, 500GB HD, Windows XP Pro SP3, Avira Antivir Personal
At work ----- Intel C2D T1700 (1.6Ghz), 2GB DDR2 667, Dell OUY141, 80GB HD, Windows XP Pro SP2, Symantec 10
Laptop ----- Intel C2D P8400 (2.4 Ghz), 4GB DDR3 1066, Mainboard, 160GB HD, Dualboot: Windows 7/openSUSE 11.1, Avira Antivir Personal
Desktop ----- AMD Athlon 3700+ (2.64Ghz), 2GB DDR 400, ASUS A8N-SLI Premium, 500GB HD, Windows XP Pro SP3, Avira Antivir Personal
At work ----- Intel C2D T1700 (1.6Ghz), 2GB DDR2 667, Dell OUY141, 80GB HD, Windows XP Pro SP2, Symantec 10
Laptop ----- Intel C2D P8400 (2.4 Ghz), 4GB DDR3 1066, Mainboard, 160GB HD, Dualboot: Windows 7/openSUSE 11.1, Avira Antivir Personal
#4 OFFLINE
-
- Members
-
- 126 posts
Advanced Member
- Gender:Male
- Location:CA
Posted 04 April 2009 - 02:09 AM
Ah it turns out I had it turned off in my BIOS, so I turned it back on, and then I was good to go. How embarrassing haha...
Thanks for all the help!
Thanks for all the help!
#5 OFFLINE
-
- Members
-
- 431 posts
Advanced Member
- Gender:Male
- Location:South Carolina
Posted 04 April 2009 - 02:56 AM
No problem, glad you got it fixed!
There's always an exception to the rule. I'm that exception.
Desktop ----- AMD Athlon 3700+ (2.64Ghz), 2GB DDR 400, ASUS A8N-SLI Premium, 500GB HD, Windows XP Pro SP3, Avira Antivir Personal
At work ----- Intel C2D T1700 (1.6Ghz), 2GB DDR2 667, Dell OUY141, 80GB HD, Windows XP Pro SP2, Symantec 10
Laptop ----- Intel C2D P8400 (2.4 Ghz), 4GB DDR3 1066, Mainboard, 160GB HD, Dualboot: Windows 7/openSUSE 11.1, Avira Antivir Personal
Desktop ----- AMD Athlon 3700+ (2.64Ghz), 2GB DDR 400, ASUS A8N-SLI Premium, 500GB HD, Windows XP Pro SP3, Avira Antivir Personal
At work ----- Intel C2D T1700 (1.6Ghz), 2GB DDR2 667, Dell OUY141, 80GB HD, Windows XP Pro SP2, Symantec 10
Laptop ----- Intel C2D P8400 (2.4 Ghz), 4GB DDR3 1066, Mainboard, 160GB HD, Dualboot: Windows 7/openSUSE 11.1, Avira Antivir Personal
