192.168.0.1 unreachable ?!

[dazedincanada]

Hi, I have a big problem. I have 2 computers sharing a router, 1 can access the internet fine, the other cannot.

On the machine that is having problems I cant ping the router. i just get destination host unreachable. in researching this i also discovered that the machine that cannot access the router also doesnt have any address resolution protocols (as shown when you type 'arp' in a command prompt).


does anyone know how to fix this ? im trying to avoid a reinstall. is there anyway to rebuild the network information that somehow has gotten corrupt/deleted ??


heres the ipconfig

Windows IP Configuration

Host Name . . . . . . . . . . . . : Dazed
Primary Dns Suffix . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . : No
WINS Proxy Enabled. . . . . .. : No

Ethernet adapter Local Area Connection:

Description . . . . . . . . . . . .: NVIDIA nForce Networking Controller
Physical Address. . . . . . . . .: 00-01-28-FB-90-23
Dhcp Enabled. . . . . . . . . . .: Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.107.39
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :



Thanks

 

[mad0maxx]

Post ipconfig /all

Also what connections are you using in the local area network? TCP/IP and what else?

Do you have DHCP or Static enabled?

 

[RebateMonger]

The PC isn't finding a DHCP Server. There's either a problem with the NIC, with the cabling, or with the router. There have been problems with the built-in nForce NICs, apparently both with hardware and with drivers.

Check the NIC properties to be sure it's "healthy".
Try a newer NIC driver.
Try an older NIC driver.
Add a second, PCI card, NIC.
Replace the network patch cable.
Verify that DHCP is turned on inside the router.
Try a Static IP address on the NIC, in the same Subnet as the router.
Try a different PC connected to the SAME cable and port on the router as the "bad" PC.

If those don't solve the problem, you could have a Windows TCP/IP stack problem. Those can be tough to fix. Try the above list first.

 

[JeffreyLebowski]

have you tried a release / renew?

 

[jlbenedict]

When you install the Nforce networking drivers.. don't install the whole application..
just extract the files.. then go into Device Manager and manually install the NIC driver..
Ensure you have the latest & greatest version

Can you ping "localhost" ?

 

[RebateMonger]

Yeah. Doesn't NVidia have a "problematic" firewall application that installs with their NIC drivers? Also, if we didn't mention it, turn off ALL firewalls on that NIC, just to make sure that's not the problem.

 

[JackMDS]

IP of 169.254.107.39 usually indicate that the Network basic are OK but that the NIC can not obtain a valid IP from the DHCP

Make sure that cable is OK.

Temporarly disable the Firewall.

Log to the Router with the good computer and make sure thta the DHCP has more than one IP to "Dish" out. Dazedincanada, welcome to AT Network Forum.

IP of 169.254.107.39 usually indicate that the Network basic are OK but that the NIC can not obtain a valid IP from the DHCP

Make sure that cable is OK.

Temporarily disable the Firewall.

Log to the Router with the good computer and make sure that the DHCP has more than one IP to "Dish" out.

Try a Static IP that is of the same subnet but out of the DHCP range (like 192.168.0.200)

http://www.ezlan.net/debug.html

Try a Static IP that is of the same subnet but out of the DHCP range (like 192.168.0.200)