Networking disconnect

[FONT= "Verdana"]Hi.

Yesterday, I ran into a very strange thing.

I admit that my eMachines PC is limited, at best. I tried to add in two cards. One, a USB 3.0 2-port card, with that strange little card edge connector with a Molex (?) power jack, and the other a USB 2.0 4-port card, with a normal PCI card edge connector.

This strange box had a flimsy metal framework on the inside, where the cards should be added. It also had card inserts which required breaking a small nib, which kept them closed, before I would be able to put a card in. (I know, it's hard to describe, and I am sorry.)

I ended up taking the frame out, before breaking the nibs, to enable openings for the add-on cards. Neither card worked, and I was unable to even boot up the system, until I removed both.

When I got the system back up, I was then unable to connect to the Internet, or my local peer network! I finally got connected to the Internet and my local peer network, using a USB-based WiFi from D-Link.

The RJ-45 connection - on the m-board itself - still will not allow me to connect and System Restore doesn't indicate anything changed since 4/6; this happened yesterday, 4/9, so nothing was different, other than the removal of that flimsy framework. Certainly, no systems settings or new software.

I wonder if this rings any bells for anyone; I'd really like to get back to using the on-board RJ-45 connection to my FiOS router, and even one - or both - of the new USB add-in cards. Before I can use the USB 3.0 card, I must get a Molex extension cable, as the one I have doesn't reach far enough and just maybe, that is why it wouldn't boot with that card installed.

And so it goes.

Cheers!

-a.[/FONT]

 

Enabled, but Not Talking to the World

Thanks, Tony.

That sounds about right, given that the NIC states that it is enabled, in Device Manager, and all other indicators seem to be good.

I did try to be gentle, when I removed those things (similar to your image). They had nibs on two locations on top and again on the bottom, so the frame may be a tad bent.

What I wondered about was the need for that flimsy shiny metal 'frame' on the inside of the area where the add-on cards go. I have it, but haven't yet put it back in, as I cannot think of a reason for it being there. Clearly, a metal object is not used for grounding, so to speak, nor should it be necessary for the proper fit of cards. And, the only card there is the modem, not a NIC.

Even looking at the IRQ lists, the NIC shares IRQ 20 with the modem; the modem is the only expansion card that was originally there and, I am certain, I did push it back firmly into its original position.

While I acknowledge that I have much to learn, I have been modifying PCs for way too many years to not be very careful about what I do, especially on the insides.

I thought about putting a separate NIC in one of those slots, to see whether Win 8 can find it and use it.

I also thought about using Device Manager to "remove" the current on-board NIC and restarting, to have Win 8 "find" it again. But what stopped me on that approach was, again, that it comes up as being "enabled" but not making the connection.

I admit that I am baffled as to how to manually configure that connection, as I was able to do in earlier versions of Windows; putting the IP address, subnet mask, and all the goodies in manually, to ensure that it knows where to look for connectivity.

Again, my thanks for your input. I do appreciate that I may, indeed, have messed it up somehow.

Cheers!

-a.

 

System Revealed

Done.

I also attached a text file - very abbreviated, due to size limitations - of System Information exported from Advanced System Details, in Control Panel.

If there is anything I removed that you might need to see, please let me know.

Thanks, Tony.

Cheers!
-a.

 

Thanks, Arie.
-a.

 

Wow!

[FONT= "Verdana"]Hi Tony.

I repeat: WOW!

I used to write guides like that, when I had time. Too bad I never got this topic so thoroughly. I will definitely do this. But first ...

Win 8 Pro bit me in the tush so badly yesterday - Arie can tell you how much trouble I'd been having - that by last night, it wouldn't even boot to the Start Menu.

And I know I must have compounded things, trying to start it so many times, with that snake of dots that replaced the hourglass, just spinning for hours ... I ended up hitting the big red button often.

By today, I used my wife's PC to look for new desktop systems. She has a better PC than I do; I bought her a good one, and used the older, slower one for myself.

Anyway, at both sites I was researching, to buy a new box, I got web pages that said they were having issues - on their end, not mine. So I decided to put the DVD for 8 Pro in, and see what damage/good I could do.

Long story short - I did a "Windows 8 refresh" and am now reinstalling all the apps and HW I had before.

Win 8 Pro is working smoothly now, so I don't need to run out and get a new box quite yet.

And no, the NIC is not working quite right, even after the refresh, so I'm going to follow your instructions, once I get this stuff reinstalled. But only what I really need, and keeping it as slim as possible.

Again, my thanks for an incredible guideline for me to follow. When I am done, I will let you know how it went.

Cheers!

-a.[/FONT]

 

A little something

Hi.

I'm trying to attach a screen shot of the Ethernet Settings from my Verizon Actiontec, in case these help before I get to trying your suggestions.

Every time I click on upload, after finding the jpg in my folder list, I get an "incorrect posting" error message. If I can get this done, it might help. Then again, maybe not!

Thanks, once more,

-a.

 

Ch-Ch-Changes (Apologies to Bowie and Lennon)

Hi Tony.

Here is some data I got by doing the old "ipconfig" command, at the DOS prompt:

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : home
Link-local IPv6 Address . . . . . : fe80::cd03:cee9:4d8:559a%13
IPv4 Address. . . . . . . . . . . : 192.168.1.6
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::a517:2875:6711:6267%12
Autoconfiguration IPv4 Address. . : 169.254.98.103
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Tunnel adapter isatap.{84CB4063-29DB-4C8C-A06A-236C75DA051A}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter isatap.home:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : home​

Now, I haven't finished with the reinstallation of all the stuff I need - needs analysis stuff, wants later on - so I've not had time to make the changes you recommended. That will come soon but until then, I wondered if any of the above settings might change my situation, without going to the length of disconnecting, removing, etc.

Should I try to plug in the address for IPv6? And the Auto-config IPv4 address is not from the 192.168 range ...

What do you think? Would it help if I did an "ipconfig/all" and posted that info for you?

Again, my undying thanks!

Alex
-a.

 

Gotcha! Thanks,
-a.