[lilcentric]

So i took out my CMOS battery to reset the bios, but now i dont have internet access for some reason?!? (before that it was fine)

Motherboard is an asus p5n-e sli that has nforce network controller in it. I tried reinstalling the nforce software from nvidia's site but no dice (however i can now see the network connection thats failing...)

- I am running windows 7 64x.
- my mb chipset drivers are not available for win7 64x....the BIOS stuff is though

attached are IPCONFIG and device manager

please advise if you need more info!!

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Josh>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Josh-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet
Physical Address. . . . . . . . . : 00-1E-8C-47-18-01
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::fc2f:e7a3:2c95:f492%11(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.244.146(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 0.0.0.0
DHCPv6 IAID . . . . . . . . . . . : 234888844
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-81-67-4C-00-1E-8C-47-18-01

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{33823F4C-9082-48C9-A17C-DCE60D320BA8}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
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

C:\Users\Josh>ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 169.254.244.146: Destination host unreachable.
Reply from 169.254.244.146: Destination host unreachable.
Reply from 169.254.244.146: Destination host unreachable.
Reply from 169.254.244.146: Destination host unreachable.

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\Josh>ping www.google.com
Ping request could not find host www.google.com. Please check the name and try a
gain.

C:\Users\Josh>

[lilcentric]

forgot to note

- router is D-Link DIR-635
- modem is a little white Dynalink.. lol

currently am on a laptop which is successfully connecting to the network wirelessly

thnx!

[JohnWill]

Did you test this exact cable on the laptop to make sure it's not the router port or the cable? If so, did you try booting this in Safe Mode with Networking?

If none of that works, try this reset.


TCP/IP stack repair options for use with Vista or Windows 7.

Start, All Programs\Accessories and right click on Command Prompt, select "Run as Administrator" to open a command prompt.

In the command prompt window that opens, type type the following commands, each followed by the Enter key:

Reset WINSOCK entries to installation defaults: netsh winsock reset catalog

Reset IPv4 TCP/IP stack to installation defaults. netsh int ipv4 reset reset.log

Reset IPv6 TCP/IP stack to installation defaults. netsh int ipv6 reset reset.log

Reboot the machine.



Post another IPCONFIG /ALL

[lilcentric]

-tried connecting the laptop to the ethernet cable and it worked fine
-tried restarting in safe mode with networking but still nothing

I did the resets specified - however for the ipv6 reset it said
'there are no user settings specified to be reset' (or something along those lines)

Here is the ipconfig after the restart

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Josh>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Josh-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-1E-8C-47-18-01
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::fc2f:e7a3:2c95:f492%11(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.244.146(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 0.0.0.0
DHCPv6 IAID . . . . . . . . . . . : 234888844
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-81-67-4C-00-1E-8C-47-18-01

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{33823F4C-9082-48C9-A17C-DCE60D320BA8}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
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

C:\Users\Josh>

[lilcentric]

bump

[JohnWill]

At this point, I'd reload the network drivers, because something is amiss there.