[Spinman]

Trying to add a computer to my home wired network.

Gigabyte 8I-EXP motherboard with ethernet connection on motherboard (Intel Pro 100/ve network connection).

I have activated the device in bios and applied the manufacturers device driver. The device show up as functioning properly in device manager.

I have the computer attached to a wired switch - and the display lights are illuminated. (BTW - I use a dial-up modem for internet - don't think that would cause any problems).

The device is show as not connected in the system tray icon and in the LAN network connection screen. The specific message is " Limited or No Connectivity. You might not be able to access the internet or some network resources. This problem occured because the network did not assign a network address to the computer."

I have tried running the repair option, but it did not resolve anything.
I have tried turning off my Norton and Windows Firewall to see if that was a problem - no change.

Wondering if anyone might have some suggestions for my next steps...

Thanks -

[oofki]

Sorry to tell you this but you nic is bad. I have seen it before. If you go into device manager then double click your nic you can change the negotiation to 10 mbit half duplex and some times it will work like that, other wise it is just bad. If it does work like that there is still somethin wrong with it eithway.

Send Her Back.

[ravashaak]

There's a slim chance it's your cable. You could swap that out and give it another try.

When you installed the manufacturer's driver for your NIC, was it their newest driver?

If neither of the above helps, it's most likely that your NIC is bad.

- Ravashaak

[Spinman]

Going into device manager - I accessed the advanced settings panel and changed the link speed from auto detect to 10mbps / half duples, per your suggestion. The yellow exclamation mark is removed and the info bubble informs me that it is trying to acquire a network address. The lights on my switch = Link/Act (on) 100 (off) Full/Col (off). After a while - the yellow exclamation point returns with the same error message.

When I reset it back to auto detect - all 3 lights on the switch are illuminated again.

The Motherboard is several years old - so a return is not in the works. If it is in fact defective - than a PCI network card may be my next step.

Where is it trying to acquire a network address from? I see that there is an option in device manager to assign a locally administered address. Would putting value in that field resolve anything?

[Spinman]

This is a new install of windows - so there should not be any conflicting garbage left over that is causing interference...

I did switch the cable - no change in status. Everything seems to click in solid.

I downloaded the drivers from the web site last night - so they are the latest and greatest.

I removed the driver utility and tried to install using the installation CD that came with the motherboard - it reported that no LAN devices were found. When I clicked on the network adapter in device manager - and pointed to the Cd - it found the OEM drivers and installed them - resulting in the same sequence of messages. Retested the half duplex setting - problem continues.

So it would appear that my NIC feature on the motherboard has failed.

Funny thing - I tried to install a LInksys PCI LAN card in the system last year (to check out the card) - it failed to load and Linksys was unable to offer any suggestions - other than the card was bad.

Wonder if there is something generic in the bios (or elsewhere) that is causing a LAN enable problem.

Thanks!

[aSMiLoN]

If you don't kave a DHCP server running and you have WIN XP with SP2 you could experience this syptom... Try applying static IP to you network adapter in order to correspond with your other LAN settings (like IP 192.168.0.10 sub mask 255.255.255.0)

[oofki]

Yeah its bad dude, I just bought a BRAND NEW motherboard tha thad the same problem, I tried 2 freshloads dif, drivers, nothing. Some times things jsut go. Pci/Isa nic is now your way of life.

[TomcaT]

Do you have MAC address filtering setup on your network?? if so have you added the new MAC address of your NIC??

[Spinman]

Did a little experimenting since my last post...

Disabled the motherboard LAN via bios to remove it from my experiments.

1) Add an PCI LAN card - during installation I was unable to get it to properly load the drivers. Kept getting an error message (that I don't remember at this time). Contacted Linksys support and worked with them for 10 minutes - his conclusion - the PCI card was bad..... (?) In reality - it is probably because of my overall problem... I'll have to try the card again on another machine.

2) I then tried to network using a USB wireless G network device and set up a peer-to-peer connection with another computer at home. I am able to get the signal and recognize the other computer (and it in reverse) - but I am unable to access the workgroup on the problem machine - keep getting a MS message that I need to contact my system administrator.....

3) On the off chance that I might have a registry setting that was the cause of the problem - I did a clean install of XP on a new hard disk and installed the wireless connection immediately after installing my intel chipset drivers. Same problems. Same error messages.

4) Flashed back to the OEM version of the bios to see if that was favorable - no improvement (using a hacked bios).

Looks like it is 0 for 3 - motherboard LAN port; PCI NIC; USB wireless.

Without going into specifics - is there a component on the motherboard that could have failed that would prevent me from establishing network communications via all three methods (including PCI and USB)? Everything else on the system works perfectly.

I have a fully loaded machine - is it possible that a card conflict or IRQ mismatch would be the cause? I might try the USB wireless again after removing all the PCI cards tonight.

(My 2nd machine was a clean install 2 days ago - wireless installed w/o any problems and shows the shared folders from that machine on the network workgroup - obvisouly nothing from the 1st machine despite having a connected wireless link). I don't understand why the problem machine will not display the shared folders under its network workgroup in explorer...

Is there anysort of utility (MS or 3rd party) I could run to check for conflicts or defective hardware on the motherboard?

I'll try aSmilon's suggestion tonight when I get home as well.

YUK! - (this puts a crimp into my home media center network)

[Spinman]

Finally got everything to work - but don't know why I had to do it the way I did.


I booted into safe mode - at which point an unspecified device loaded.

Rebooted and returned to normal mode - no improvement.

Rebooted and returned to safe mode.

Reconfigured entire network settings in safe mode.

Renamed PC and Workgroup

Rebooted back into safe mode

Renamed PC and Workgroup

Rebooted back into normal mode.

System partially correct.

Rebooted back into normal mode.

System stable and works perfectly (for at least the last hour).

Very strange....

[sven]

i only get that problem when i connect my card to my modem. its because it cannot get any information about you ip and subnet. even when you conenct, it will continue to say it because those settings are in the internet connection icon. the main way too stop it is just unselect notify me if this connection has limited or no connectivity. if your connected to a network or something, its possible your not getting any info from the dchp server. this happens with sp2

if it works perfectly but says that still, just unselect the option to tell you about it

[TomcaT]

Spinman, on Jan 26 2005, 09:09 PM, said:

Finally got everything to work - but don't know why I had to do it the way I did.


I booted into safe mode - at which point an unspecified device loaded.

Rebooted and returned to normal mode - no improvement.

Rebooted and returned to safe mode.

Reconfigured entire network settings in safe mode.

Renamed PC and Workgroup

Rebooted back into safe mode

Renamed PC and Workgroup

Rebooted back into normal mode.

System partially correct.

Rebooted back into normal mode.

System stable and works perfectly (for at least the last hour).

Very strange....

!!!!!!!!!!!!!!!!!!!!!!!!!!

Well done! As you say Very Strange!

[epic]

I have seen this with my machine as well as others. It happens without warning. It seems it is a problem with SP2 but have not figured it out. The only solution I have found is to physically remove the drivers and the card and reinstall.

[davidhutchinson]

I had almost exactly the same symptoms crop up a couple of weeks ago. - This is what fixed it for me (and a couple of other people I know):

Update for Windows XP Service Pack 2 (KB884020)
http://www.microsoft.com/downloads/details...&displaylang=en

I apply this patch as a matter of course during my unattended installs ... no problems ever after that.

Dave

War Eagle!

From Microsoft:

Overview
This update helps resolve an issue on computers running Windows XP Service Pack 2. Programs that connect to IP addresses in the loopback address range may not work as expected and you may receive an error message indicating you cannot establish a connection. After you install this item, you may have to restart your computer.

SYMPTOMS
On a computer that is running Microsoft Windows XP with Service Pack 2 (SP2), programs that connect to IP addresses that are in the loopback address range may not work as you expect. For example, you may receive an error message that says that you cannot establish a connection.

CAUSE
This problem occurs if the program connects to a loopback address other than 127.0.0.1. Windows XP Service Pack 2 (SP2) prevents connections to all IP addresses that are in the loopback address range except for 127.0.0.1.

[matrix0978]

Spinman if it happens again for me all i had to do was disconnect my modem and router (unplugg the power cord) for about 10 seconds them restart your computer..

[jeffshen]

sorry if i seem to be starting up an ancient topic but it seems relevant in this thread rather than to start a new one but yea...

have a dell computer with a intel pro/100 ve card
installed winxp sp2 then internet connection dies
uninstall sp2 - internet connection remains dead
so reinstall
come across this thread
uninstall driver+reinstall - nothing new - ie. net connection still dead
installed the microsoft update stated in this forum - nothing new again
reboot into safe mode - net connection working!!
reboot back into normal mode - dead again
reboot back into safe mode then change network identification then reboot - still dead
tried pulling the plug for >1 min - still dead
tried using ping and tracert on urls - works

this is so weird...
i connect to the internet using a router and all the other computers are working fine

o and even MS networking aint working on the machine with the bugged card.

can someone please help me?! ive spent more than a week trying to figure this out!?!

Thanks,

Jeff

[softec]

Though I would add my 2 cents worth.
I have a clients Dell. It had viruses and spyware all over it. They called me because the internet went down. I removed the spware and viruses. The machine feels really good, quick, stable. But the on board Intel connections does not work. Tried rebuilding the TCP stack, no luck. Added a Dlink DFE 538 PCI card, got an IP address and updated windows. Life was good. Then I rempved the Dlink card. Back to no connection. The intel utility say the card is working. It also tells me that I am connected at 100MB, but my switch says 10MB. I really don't believe it is a hardware issue. I have seen this before, and it was software left over from the Malware. I just can't seem to rip this stuff out this time. Any suggestions?

The card almost looks as though some form of firewall software is blocking the card and windows from working together.

[MDVill]

I have tried almost everything on these **** computers!

I am an IT Administrator at a company and we have about 5 Intel computers and about 10 others. The intels all have the same exact motherboards and programs. But just 2 of them do not want to work! Before, everything was ok, they worked perfectly with the servers and everything was just fine and dandy...but just recently, one day they decided to have "limited or no connectivity". I have tried everything that you people have said to do and it still does not work

I got the original CD and uninstalled the driver for the card and then re-installed it and rebooted...no dice. I have used that patch that you have given me earlier...no cigar.

All of the Intel Motherboards have an Intel[R] PRO/100 VE Network Connection built into the motherborad itself...so it cannot be a problem with the card itself...because there is no card to worry about, but this gets really frustrating...especially when my co-workers come to me asking "when will you fix this problem?"

Someone help me!

If anyone has ANY advice...please E-Mail me!

This post has been edited by MDVill: 19 July 2005 - 07:30 AM

[MDVill]

New Update!

I changed my IP Address on each computer that was having the problem to 192.168.1.* and the Default Gateway to 192.168.1.* ... It works perfectly for getting onto the server and accessing files, which was the most important thing, but there is still one more problem. The internet cannot be accessed.

A hint to this problem might be that right when I changed the IP address and exited out (changing the settings) I noticed that a new icon appeard in the Network Connections...

Sorry, but my co-workers are using their computers at the moment (go figure) and I cannot access their computers at this moment. But I do remember that it was some kind of Internet Connections Icon. And when I viewed the detailes...it said that it was disabled, so I try to Enable it, naturally. But to my greatest surprise, it would not enable! WOW! I never saw that one coming!

So if anyone has any more information on this non-enabeling Icon, please contact me. Or Post your answer to my great dillemma below this, thank you.

[-eMc2H-]

These steps are for windows XP


Here are a fiew steps to resolve the route issue ip address: 0.0.0.0, and in some cases also resolves the 169.254.x.x issue and in a fiew cases resolves the LIMITED OR NO CONNECTIVITY message in windows xp Service Pack 2



Here is a little background in the 169.254.x.x ip address, ususly we cannot release a 169 because we will get a fresh 169.254.x.x…. and this same ip address it translates to LIMITED OR NO CONNECTIVITY in sp2, because if we go to the prompt (start, run, cmd) and do a ipconfig /all we will notice an ip address 169



********************************************************************

IMPORTANT:
1.-Before trying this, make sure that the nxtt test shows test code:0000 or 0002 any other test code refer to CLONE to see what it means because it’s possible with other test codes, the steps wont work

2-also make sure that these two options are selected in the TCP/IP properties:



********************************************************************

HERE ARE THE STEPS:



Step 1, we must disconnect the modem from all 3 cables so that the modem can be completely off (the power cord, the ethernet cable and the phone line), if we have a router, it is recommended to connect the modem directly to the pc



Step 2, we are going to network connections and here is a short cut, click on start, run, And then we are going to type nca.cpl, then hit enter or click ok

...then:
we are going to right-click on the local area connection and we are going to select Disable, (it is necessary to disable the connection because it will reset the registry values in the winsock keys in the registry)



Step 3, then we are going to close the local area connections windows and we are going to enter the services local, so we can reset (restart) the DCHP client



Here is the short cut to the services, we are going to click on start, run, services.msc and click ok or hit enter




then we will do one click (highlight) the DHCP client and on the left side we will see the options “stop” and “restart”, we are going to click on restart and we will see for a split secord the following window:



***Note: as we can see the dhcp client sess: Manages network configurations by registering and updating IP addresses and DNS names. That is why it is necessary to restart the dhcp client so that the ip address can be reset



Step 4.in order to have a new ip address it is necessary to SHUT DOWN the pc, NOT RESTAR, but to completely shut down the pc



Step 5, we will proceed on connecting the modem until we get a solid green light (ready or dsl light), then we will turn on the pc again (Note:in these steps we do powercycle on all cpe)



Step 6, we will go back to network connections like in step 2, and by double clicking the Local Area Connection, it will be enabled and over 90% of the times it will resolve the issue IP address: 0.0.0.0 and like it was mentioned on top in some cases it will resolve 169.254.x.x and limited or no connectivity , if the avove steps do not resolve the situation then it is recommended to uninstall the NIC and that can only be done with a local TECH!!….. good luck!!

i work for the Verizon DSL tech support....and this help me a lot...and also to my coustumers...have FuN...hope it worked for you

-eMc2H-