New
#11
I tried to update the drivers, but the NVidia site was acting weird as well, I'll keep on trying. My Ethernet port is on my motherboard.
When I switched my case I switched one of the fans powered from the motherboard from a small one to a large one, would it be drawing power out and making other components (like my ethernet port) act differently? Just a thought.
And here's my properties.
Was that tcp/ipv4 from your wireless or LAN? in your ipconfig, there is no ipv4 or the LAN. Is there any issue that you can see in your Device Manager?
That was from the LAN, and in my Device Manager, it all seems fine.
Windows IP Configuration
Host Name . . . . . . . . . . . . : Harblkips-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : phub.net.cable.rogers.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce 10/100 Mbps Ethernet
Physical Address. . . . . . . . . : 00-21-97-1C-18-B9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IPv4 Address. . : 169.254.197.246(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : phub.net.cable.rogers.com
Description . . . . . . . . . . . : D-Link DWA-130 Wireless N USB Adapter(rev
.C)
Physical Address. . . . . . . . . : 00-22-B0-74-01-73
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b8cf:2727:cd4a:411c%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.12(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : December-27-09 9:36:39 PM
Lease Expires . . . . . . . . . . : December-30-09 9:36:38 PM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 369107632
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-8D-04-6D-00-21-97-1C-18-B9
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection* 9:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:1882:1b3a:9c05:7a02(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::1882:1b3a:9c05:7a02%11(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.{342225C1-84F4-4A2E-81CF-399F3278202C}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.phub.net.cable.rogers.com:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : phub.net.cable.rogers.com
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
From the looks of thing you might not have gotten the correct driver for your nforce LAN adapter.
Retry download the correct driver and install.
Drivers - Download NVIDIA Drivers
If issue, what error did u get?
After a gruelling search, I finally found a driver! But alas, it gave me false hope and failed me.
I tried out a Linux Live Cd (a little out dated version, but i'd imagine it would still work) and I STILL couldn't connect through LAN. So I assume this is a hardware issue, or some software paradox. I'm going to buy a Network card and see if that works. I'll let you know how it goes.
Something weird that happened as well: I couldn't connect to my OWN wireless network during this whole endeavour. It would just not accept the connection. Quite odd, thank god for my neighbours.
I would also like to thank you both for all your help, especially aem, your efforts to help this aspiring computer expert are very appreciated.