 | Can't connect to internet after installing new RAM |
March 17th, 2009, 11:50 PM
|
#1 (permalink)
| | Junior Member
Join Date: Aug 2004 Location: Plano, TX
Posts: 16
| Can't connect to internet after installing new RAM
I upgraded the memory in my kids' Dell 5100 and now I can not get the computer to access the internet or our home network. It connects via Verizon FIOS router. The other 3 computers can connect. The computer seems to run fine other than the internet connection.
When I view my router, it lists that computer on the network, but says it is inactive.
I'm not even sure where to begin.
Thanks,
Marion |
| |
March 18th, 2009, 12:14 AM
|
#2 (permalink)
| | Thaumaturge Member
Join Date: Oct 2001 Location: West Haven, Utah
Posts: 18,162
|
Any chance you unseated your NIC when you installed the RAM? Try taking the network card out then putting it back in to reseat it. |
| |
March 18th, 2009, 03:15 AM
|
#3 (permalink)
| | Ultimate Member
Join Date: Sep 2003 Location: From my house
Posts: 1,265
|
"It connects via Verizon FIOS router"
Can you elaborate? Meaning, are you just talking about the physical connection that it's wired up to that router at current? - Or does it actually say that it's connected (either on the bottom right of your taskbar, or in the properties of the NIC).
My guess is right up there with howste's and that something got dislodged when ya' played around on the inside of the case. Check everything starting from the ground up, including your cabling (plugged in on both sides), the card is seated properly, Windows can see the card in the device manager (and there isn't anything wrong with it), etc.
Then go from there, and check to see if (I'm guessing that you're router is handling addressing) - check to see if it's able to get an IP from the device. If it infact can get an address, then see if you can ping the router (your default gateway from the PC) - and then out to the internet.
Lost network connectivity could be a bazillion and a half reasons, but always start from at the ground, and work your way up.
**Good luck** 
__________________
And thus it was spoken by the mighty Uss. And it was so.
|
| |
March 18th, 2009, 07:35 AM
|
#4 (permalink)
| | Ultimate Member
Join Date: Oct 2001 Location: South Jersey
Posts: 9,879
|
The Actiontec router will show recently connected equipment even if they are no longer there. If the status shows "inactive", then your NIC is dead or not communicating. Bad cable or connection, perhaps? It's got to be something simple like that. |
| |
March 18th, 2009, 02:09 PM
|
#5 (permalink)
| | Junior Member
Join Date: Aug 2004 Location: Plano, TX
Posts: 16
|
More info - not sure what could be indicative of the internet connection problem ...
In Internet Explorer, when get message that can't connect to internet, I click on the link, "Diagnose connection problems". Then look at the log of errors :
"Unexpected error with iphlpapi : Pipe is being closed"
"Could not retreive IP information for specified NIC"
Ran sfc \scannow and got :
"Files that are required for Windows to run properly must be copied to the DLL cache. Insert Windows XP Professional SP 3 now."
I don't have a CD because the computer came with OS installed. Does this seem like a legit problem or could it still be a hardware problem?
I opened the box up again and checked that cards were in place. I don't think I bothered anything because it was pretty easy to remove the old memory and add the new without touching anything else.
I physically have the PC connected to the router. When I go to Network Connections, it shows "Local Area Connection, Connected, Intel (R) Pro/100 VE Network" I'm not seeing the 1394 Connection like I see for the other 2 PCs.
When I go to Device Manager and look at Network Adapters, I have 4 listed.
Intel (R) Pro/100 VE Network Connection
Intel (R) Pro/100 VE Network Connection - Symantec Network Security Miniport
WAN Miniport (IP) - Symantec Network Security Miniport
WAN Miniport (IPX) - Symantec Network Security Miniport
The last 3 have an error indicator. When I view properties, it says, "Windows can not start this hardware device because it's configuration information (in the registry) is incomplete or damaged (code 19)"
When I ping the Dell, it fails.
Thanks for any and all help I can get. I'm not a hardware person. |
| |
March 18th, 2009, 04:03 PM
|
#6 (permalink)
| | Ultimate Member
Join Date: Oct 2004 Location: Blacksburg, VA USA
Posts: 1,231
|
Uninstall the memory and see what happens
__________________
Swan XT10 640K 20M HD Hercules Graphics
|
| |
March 18th, 2009, 06:33 PM
|
#7 (permalink)
| | Ultimate Member
Join Date: Oct 2001 Location: South Jersey
Posts: 9,879
|
Even without the XP disc, you can do an OS restore by following these instructions: Dell - Support
BEFORE YOU DO THIS, make sure to back up your files.
Also, you can order disc from here: Dell - Support
Might be a good idea. |
| |
March 19th, 2009, 01:37 AM
|
#8 (permalink)
| | Ultimate Member
Join Date: Sep 2003 Location: From my house
Posts: 1,265
|
"Intel (R) Pro/100 VE Network Connection - Symantec Network Security Miniport"
I haven't seen this before - but that "Symantec" in the title is leaning my guess towards an inadvertant firewall setting.
Are you using any firewall on that PC with the problem?
I've seen motherboards that have really strict security settings on their onboard NIC, where at the default setting wouldn't allow any ICMP (pings, etc.) message responses, and I basically had to fizzle through the "advanced" properties of the NIC to get my desired security settings, etc.
Big Daddy's got the right idea also, as it could be that those last three listed devices with the expl. point on em' sound like they're conflicting for the same system resources. - And depending on how the memory controller handled the additional memory - something may have been "broken" in that process.
I'd do Big Daddy's suggestion - at this point, and take it back down to the point of last successful usage. Remove the memory - and boot normal. Just to test.
If it does infact come back up, then we can isolate the problem pretty much to what we've been talkin' about.
Do the system restore bit only after you've exhausted all other possible means of troubleshooting. As it may fix the problem, and it may not. But definately use that as one of your "bag of tricks" like Osprey suggested. |
| | | Most Active Discussions | | | | | Recent Discussions  | | | | | | | | Thread Tools | Search this Thread |
| | |
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) |
| |