hey i know it's not the cable or modem as it works fine on laptop. In device manager it shows good as well. Do i have a bad card or pci port or should I try to reset tcp/ip via cmd?
2007-05-11 10:28:37 · 6 answers · asked by KWA 2 in Computers & Internet ➔ Computer Networking
Yes it is a hardwire connection
and yes the router is dhcp
it is set to obtian ip automatic
2007-05-11 11:23:52 · update #1
169 meant your PC cant see the modem/router, from your previous action, I suspect a faulty driver or faulty card
2007-05-11 10:32:31 · answer #1 · answered by Cupcake 7 · 1⤊ 0⤋
The 169 number is a MS dummy number used to prevent the card causing problems when an IP is not given. You don't say if this is wired or wireless. In the tcp/ip properties try setting it to one or two numbers away from the laptop, then from cmd try ping 192.....
In other words if the laptop has 192.168.1.4, use 192.168.1.5
Then ping 192.168.1.4
If this returns 4 correct replies the problem is the dhcp. Check that the router is set to give dhcp addresses. If not turn it on, set the tcp/ip to automatic and try again. It would then be safer to check the laptop and set it to auto as well.
2007-05-11 11:15:35 · answer #2 · answered by Anonymous · 0⤊ 0⤋
Hard to tell what the problem is right away, but try these:
1) Try using a static IP address, instead of DHCP
2) Try replacing the card. They're cheap. If it works, it was the card. If it doesn't, return the card
3) Your router may not be giving your PC an IP for some reason. Log into your router and check for DHCP clients.
4) Again, I know you said it wasn't your router, but try rebooting it anyway. And your PC
5) Something simple, but at a command prompt, type "ipconfig /renew" You've probably already tried it, but it's worth a shot.
2007-05-11 10:37:16 · answer #3 · answered by Marty H 2 · 1⤊ 0⤋
Yes, first thing to do is cmd > ipconfig /all to ensure you see the device labeled Local Area Connection (or similar)
Then an ipconfig /release followed by ipconfig /renew
If you're still getting the windows 169... address, update the driver for your NIC, use the NIC manufacturer driver not a generic or Windows driver.
Repeat commands above.
If you still have a 169 address, then it's time for a new NIC.
2007-05-11 10:36:32 · answer #4 · answered by spl 4 · 0⤊ 0⤋
I would check layer 1 first that 169 address is a appipa address and is not routable
2007-05-11 18:55:41 · answer #5 · answered by Figure O 1 · 0⤊ 0⤋
Did you run the set up program ( it assigns the port addresses) You could assign them manually.......
2007-05-11 10:38:21 · answer #6 · answered by Daniel H 5 · 0⤊ 0⤋