PDA

View Full Version : Little or No Connectivity on NIC


macellarius
03-20-2006, 10:06 AM
:confused:

MSI K7N2Delta-L
Win XP Home SP2 AutoUpdates
AMD 2400
1Gig Crucial PC2100
1 120Gig/1 18Gig
Linksys Wireless LAN card, RealtekNIC, Firewire


For years I've had my cable modem connected to a desktop PC using that NIC (URL=http://www.realtek.com.tw/products/products1-2.aspx?modelid=7) on my PCI port with no trouble.

(I also have an onboard NIC that's never worked for me, and still has a !confilct in device mgr)

Realtek NIC worked fine with Comcast cable modem and Internet sharing worked fine off my Linsys Wireless B router to a laptop, etc.

Recently I decided to connect WIRELESSLY using the wireless lan card FROM MY DESKTOP to the Router. This has worked fine too.

last night I was trying to connect to a new device (http://www.buffalotech.com/products/product-detail.php?productid=72&categoryid=16) via that Realtek NIC and I'm getting "Little or No Connectivity" warnings from XP!

The Buffalo LS software searches for the device on the network as part of the setup process. SOMETIMES it sees it, sometimes it doesn't, but when I get to the part where the software is setting up DHCP for the drive, it fails to obtain an IP address.

I try to run IPCONFIG and get no details...just "Windows IP Configuration", or something like that.

I try to ping the default IP for the Link Station with no response, can't http to it either...

* I've tried multiple PCI ports
* Tried updating the driver
* Tried uninstalling and reinstalling the NIC
tried that onboard NIC

I need to connect directly (not through my wireless setup) for this situation, so want to get this to work.

Could the problem be that NIC is set to DHCP from when I was using it with the cable modem and it can't GIVE AN IP to the Link Station?

Could I have a TCP IP stack issue?

I know it's not the drive because I also was not able to connect to a Savin printer that I have that I WAS ALWAYS able to connect to before I started connecting wirelessly through the Linksys NIC.

Thanks in advance, you guys have come through for me serveral times over the years!

macellarius
03-20-2006, 05:05 PM
No response...getting worried now. Anyone?

classicsoftware
03-20-2006, 11:30 PM
You need to resolve the conflicts with the NIC. Get a hold of the drivers. Get a copy on:

A floppy
A CD
The hard drive


Go into device manager and remove the NIC there. Re-boot and the system will attempt to re-install. Have the drivers ready and you should be good to go.

Whyzman
03-21-2006, 12:27 AM
What does the Device Status box say in Device Manager regarding the NIC? Does it spell out what the conflict might be?

macellarius
03-21-2006, 10:57 AM
1) I tried to uninstall the on board NIC, but Windows doesn't let me...
Says: Failed to Uninstall, this device may be required to boot the computer :rolleyes:

2) I've already updated the driver for the PIC NIC, but I can't honestly remember if I uninstalled it and reinstalled it WITH the new driver. Let me try that. I don't have the driver on CD or floppy, I just have it in a directory on my D drive because I had to download it from the web.

3) Device mgr does not elaborate on the conflict as far a I can see...

http://www.ehomeparade.com/images/temp/Clipboard01.jpg

Whyzman
03-21-2006, 12:44 PM
Did you try right-clicking and PROPERTIES? That should get you the Device Status dialogue box...

Also, at this point you might want to try what ever you are doing in SAFEMODE...I've a suspicion that there might be some "ghost" drivers that have appeard from your trials and errors to install...

"Ghost drivers" are multiple software installs that confuse the OS from knowing which one to actually use...you would need to remove all instances and let Windows find and reinstall...

Also, if you cannot remove...you might be clicking on the "category" rather than the individual component...however, you best attempt to remove in SAFEMODE for the reason cited above.