Fried LAN Port?

[DarkneSS]

Hey guys an gals I am just wondering if any of you could give me some input on whether on not you think my LAN port could be fried. Heres the scenario:

It was a normal day for me, relaxing because I have the day off and I put a DVD-R in my comp and start to burn something, I then go away to have a shower and what not and come out of the shower only to realise that the power had gone out in my area (Out time 4:00ish to 7:45). I then proceed downstairs to turn my computer on and check things out, when I boot it up I get the annoying message of "Limited or No Connectivity". So I figure that the router and modem just may need a reset after the power outage, I proceed to do so and power down my computer. I leave them off for about 5 minutes to clear them and plug them back in, I boot the computer up again and recieve the same message. I then tried different ports on the router and a direct connection from the modem straight to the PC and got the same error. I then proceed to check the other devices that are hooked up to the router. My old HP computer (Which I am posting this on) has full connectivity as does my sisters computer and my Xbox Live. My computer is the only computer to recieve a connectivity issue.

The port still flashes when I plug the ethernet cable into it it just cannot obtain an IP Address when I try the Repair option in "Network Connections" or when I run Command and try to renew it through Ipconfig. I also cannot access my router via that computer because it doesnt obtain a correct Ip Address. Any input on the situation would be appreciated seeing as I am highly frustrated with the situation of not having internet on my PC!

[David]

Good morning, Here are some suggestions (not in any certain order) to try:

it is possible that something hardward related happened..
load up your computer system, and click on your start button, and then run.
Type the following ( when you see <cr> this means press enter/return)

command <cr>
ipconfig /all <cr>

** what do you see? Is it giving you an address? or does it say it can not find anything (dhcp)??

Continue to type :

ipconfig /release <cr> (If on 98, it would be: ipconfig /release_all <cr>)
ipconifg /renew <cr> (If on 98, it would be: ipconfig /renew_all <cr>)

This should give you a new ip assignment to your computer.
It wouldn't be your router, not because you see the light (which is an indication the port is not dead / fried or you wouldn't see any light) but because it does not work when it is plugged directly into the modem..

It could be your network cable that you are using.. Try switching that one with another.
I imagine by the sound of your posting, that you have a separate router then that of the computer you wrote this on..
Your router could also be failing picking up the IP address (DHCP), however since it didn't work with a direct connection (as stated above) it probably won't make a difference, but you might as well try anyway...
Open up your browser (IE for example).
Type in the local ip address to it (If you have not changed it, it will be set to : 192.168.1.1).
Do not enter a username in the box that appears, but put in your password (if you have not changed it before, it will be defaulted to : admin ).
Go to the SERVICE tab, and click on the DHCP Release button.
Wait about a minute, then click on the DHCP renew button.
See if you get an ip address..

You should also check your network protocols by going to your network properties (located in the control panel).
Ensure you have a Service (Client for Microsoft Networks)
Ensure you have a Internet Protocol (TCP/IP).
If not then add these.. if you do, then don't worry about it or you can remove them from the list, reboot your computer, and re-add them.
If all else fails, go to : Start / settings / control panel.

Double click on the SYSTEM icon, and go to the device manager.
Find your network card connection, select it, and delete it (uninstall)..
Click okay, etc...
Reboot your computer system.
When it comes back up (XP should find it, and install it automatically for you, and 98 may do the same if it has the drivers pre-installed).
If not then just reinstall the network card manually by going back in the SYSTEM icon, and FIND NEW DEVICES.. FOllow the online instructions..
When this is done, you should be surfing away.

[DarkneSS]

I've tried a lot of those things already. When I release and renew I cannot get a renewed IP and I get the Limited or No Connectivity Error. In the command prompt it tells me "An Error occured while renewing interface Local Area Connection 2: unable to contact your DHCP server. Request has timed out"
I have tried to switch network cables, I've tried about 3 or 4 that I have around the house. I have also tried to access my router via that computer as well by typing in the ip adress that it is default (192.168.1.1) and could not connect with the router.
I do have the Services and Network protocol and have tried uninstalling and reinstalling them with no luck obtaining an ip address.
I uninstalled and reinstalled the device as well, thus indicating "Local Area Connection 2"
When I type in ipconfig /all I get the following:
Windows IP Configuration

host name: .......... Mikes-Comp
Primary DNS Suffix ....... :
Node Type ......... : unknown
IP routing enabled ..........: no
WINS Proxy Enabled.........: no

Ethernet Adapter Local Area Connection 2:

Connection specific DNS suffix:
Description .........................:VIA VT6102 Rhine II Fast Ethernet Adapter
Physical Address...................: 00-40-62-C3-C8-4D
Dhcp Enabled ......................: yes
Autoconfiguration Enabled.......: yes
Autoconfiguration Ip Address ...: 169.254..231.114
Subnet Mask .........................: 255.255.0.0
Default Gateway .....................:

Normally it should read the same as the computer that I am now which is:
Connection Specific DNS Suffix ........: pr.phub.net.cable.rogers.com
IP Address ...................................: 192.168.1.101
Subnet Mask ................................: 255.255.255.0
Default Gateway ...........................: 192.168.1.1

[Deb]

Ip starting with 169 usually indicates a failed card or bad driver.

[DarkneSS]

Well I am not running a network card, it is onboard. I tried to roll back the driver, and that didnt do anything. I uninstalled the network adapter and reinstalled it and used the drivers CD that came with my mainboard and I still didnt get anything.

[Mischief007]

Next thing to do is to try putting in a network card. My brother's onboard LAN died as well and there's nothing you can do.

[Drthorne]

My onboard LAN died also, I tried everything. I ended up buying a $10 d-link e-net pci card