"Ethernet" Connection Drop

[Generator]

Just wanted to mention that if I leave my Bluetooth 2.0 dongle plugged in all the time, my internet acts the same way. it installs an additional network adapter which seems to conflict so I have to unplug it until I want to send stuff to and from my mobile phone.

This ain't a problem for me but it might be something some ppl overlook. If I didn't mention this and it turned out to be bluetooth I'd be kicking myself for not mentioning it.

I havn't read all 20 pages of this thread but I searched it for Bluetooth which returned no results so if it has already been mentioned I apologise.

EDIT: this was on an old build though, havn't tried on 7127

 

[themouse]

sexytool - are you suggesting installing software for my generic realtek 8139? I didn't know there was any i will look cause if it fixes my problem I will be very happy

 

[themouse]

snuffy - unchecking the power management button is the first thing I do even though I dont think its the problem

yes i am using the win7 drivers it still fails I loose total connectivity there are no packets being sent or received thats nothing to do with my ISP or router. After a reboot its away again.

I have tried every driver I can get my hands on from old xp right up to the latest.

 

[sexytool]

From memory a couple of vendors have released software for 8139's when provided as onboard Networking devices.

However i doubt you'll find one for your specific motherboard and i doubt one for a different motherboard or PCI 8139 NIC will work with yours.

I checked my manufacterors' website for updated NIC drivers and hopefully some management sofware, there isn't any unfortunately.
I'll try installing the drivers off teh CD in XP SP2 compatability mode and see if that helps.

However i'm not going to try it until i get another dropout. I've booted back into my W7 install because honestly, i just love it too much.
Something i share in common with some of these other guys is perhaps teh "Glutton for punishment" aspect haha.

For now i'm going to install my updated Audio Drives for W7 as provided on my manufactorers' website, ill keep checking back here though.

 

[Digger]

/facepalm
/facepalm
/facepalm.

You use a BELKIN wireless and didn't think you NEEDED that software?
MY GOD MAN!

There's a reason i said to install with a pre-vista compatability mode... mainly that those are the only OS's which will install properly, e.g include the software install.

There's dozens of makes and models of network adapters out there, that don't work without their software package. Netgear is infamous for it.

I think it's safe to say that just because you neglected to realise you didn't have the FULL driver package installed, everything you've come accross and everything you've experienced has to come down to "User Error" and be disregarded as trying to find a solution to the problem because realistically; You caused your problem.

It's very probably you'll never see it again and it's not a cause of W7.

On the other hand, you DID make me realise that perhaps this realteck 8186 is the same as the "Nvidia MCP Networking device" or similar generic onboard that requires software to work in W7 100%.
It doesn't require software to work in XP period, but i've installed teh drivers off the motherboards' CD so i can't realistically claim it's running off stock drivers.

whoa tiger. I havent done any different steps on 7127 that i'm taking now, that i didnt do or try multiple times under 7100. Installing under XP SP2 on 7100 did NOTprovide me with the same results i have found while doing the same on 7127. Furthermore, i used the exact same driver package and installed under Vista comp mode on 7000. Recall there was no Vista SP2 mode. Then just the regular Vista comp mode worked FINE, but not under 7100. Look ST, its not a user error, frankly becuase i have tried every possible combination and thoroughly tested up til this point. I didnt install my nvidia ethernet in ANY comp mode, but am using older drivers than the "stock" 7 drivers that have been handed out, and not working ultimately. The nvidia adapter used the website drivers, running under no comp mode at all actually. I did this as a first test, and they are running just fine without the need to make them run under Vista/SP2 being that its a vista driver.

now try and explain this.

 

[sexytool]

It WAS your error. You've installed these drivers on XP and Vista before if i'm not mistaken.

You KNOW there should be software installed along with the driver.
So why didn't you think it was odd that you didn't get the software installed?

 

[Digger]

It WAS your error. You've installed these drivers on XP and Vista before if i'm not mistaken.

You KNOW there should be software installed along with the driver.
So why didn't you think it was odd that you didn't get the software installed?

Correction. Only XP. never poisoined by vista

secondly, the "software" mentioned is only the wireless utility, same utility you have built in. Reason why there is a radio tick on to not use the belkin utility, use the XP wireless zero config. Choosing that, THEN turns that software utility completely off, makling the software null and void, and also by making sure its not running anymore. Gone from systray, no processes of it running at all. Al is working

try again.

You DONT need the software to make it work, just like you wouldnt need Lexmark software to be able to print a webpage, you only just need the printer drivers themselves. It will still funtion just the same.

 

[Digger]

instead of picking apart the software ST. YOu failed to see that i mentioned the difference between all 3 driver dates for each XP, Vista, and 7.... dont you think THIS is and COULD be the issue/problem/resolution ??

edit: also, the software is ONLY installed via XP comp mode, becuase there IS NO wireless utility config for vista like with XP if i'm under the correct understanding. Tis the reason why i didnt get the utility install while under Vista or Vista SP2, only when XP comp.

 

[sexytool]

Err, no. That's how it's supposed to work.
Just like NetComm.
Can you get away without using their wireless utility? Probably not.

You didn't even install it and use it to eliminate the possibility -.-;;
You're now running 7127, you didn't even check to see if 7100 had the problem resolved if you manually installed the wireless utility.

Just because you haven't gotten the issue in 7127 doesn't mean it's "Fixed"
7127 has been out less than a week and I had ZERO problems for the first week of running 7100.

You're probably going to get the same issue.

EDIT:

becuase there IS NO wireless utility config for vista like with XP if i'm under the correct understanding

Yes, there is. It's called the Windows Wireless Zero configuration tool and was integrated into service pack 2 or a windows update along the line, don't remember accurately which.
Either way it's on my XP install.

 

[Digger]

Err, no. That's how it's supposed to work.
Just like NetComm.
Can you get away without using their wireless utility? Probably not.

You didn't even install it and use it to eliminate the possibility -.-;;
You're now running 7127, you didn't even check to see if 7100 had the problem resolved if you manually installed the wireless utility.

Just because you haven't gotten the issue in 7127 doesn't mean it's "Fixed"
7127 has been out less than a week and I had ZERO problems for the first week of running 7100.

You're probably going to get the same issue.

wrong again ST. slow down bro. I DID say that i tried this same driver under XP SP2... got the utility installed also... but it didnt help the drops at all. I'm not doing ANYTHING differently. I am a creature of habit. I'm sure you are too, goes with the nature of the pc mind. I have a systematic process in which i have tested all kinds of drivers in all comp modes, swapped out routers, tested wired and wireless, 2 different wirless nic cards now.

If you would scroll way back in this thread, i DID mention on how it was weird that when troubleshooting the vista driver setup.exe, 7 told me to run it as XP SP2 both under 7100 and 7127. I came in here to report that, just becuase of the wierdness factor there if you recall, probly around 2 weeks ago, give or take a day or two.

I've been pulling hair out, dont you think just with common sense that i would have tried EVERYTHING by now. I got MY ethernet working, so obviously i am doing something right so far. ANd my $2 bet is on the drivers themselves. The XP driver was a 2005 driver, the vista driver was newer than the "stock" 7 driver. so go figure. On 7000, it was the Vista driver that work under vista comp mode. Yes, i even installed under XP SP2, by shear curiosity to see how it would behave with the OS... was the first or second time trying out the comp modes back then. I got my answer, regular Vista comp mode was the winner, not SP2, not XP/SP2. If its all about the software utility, why not recommend installing under XP SP3? my guess is that the SP3 wasnt out till after the driver release date, therefore wouldnt support it in some fashion.

 

[Digger]

if anything here ST, i have found that using multiple utility configs confuse the adapter. Atleast this is and WAS my experience with it and multiple adapters and their software under XP, my dlink which is now dead, did the same thing the same way. I always used zero config. If i'm allowing windows to "configure" and NOT the utility itself, then why am i not seeing problems, if its JUST the software thats the holy grail. Why do i not have problems with my ethernet after installing an OLD chipset driver from GA's website, instead of the 7 driver, or for that matter the nvidia driver, too which there is no more support for the nforce4 boards now. Atleast they took them out of the dropdown box just this week. One has to resort back to the old 15.23's. which i didnt use on this install, but did on 7100, as well as the OLD chipset driver. None which worked properly.

 

[Digger]

another thing... about your netcomm example. If that was the case, it not working without its utility software, dont you think MS or just a customer would go about making a federal case about it all? not having the choice of what software to run for your bought hardware? That be like lexmark telling me that i couldnt use photoshop to edit pictures or lexmark wouldnt print them out unless i used their editor. Woldnt make sense, or be practical in any way just the same. Havent used any netcomm, so dont have that headache... i would be ringing their phone lines and trying to find the closest tort lawyer around me to handle the case. All it should need to funtion is a CORRECT DRIVER, not some piece of software. Same thing if sony pictures only allowed you to watch their dvd movie on their dvd hardware player.

 

[sexytool]

Sadly the N4 and 700 series are the buggiest out of the lot.
I really liked the NF2 series, that was great.. had no problems.

Perhaps that's why they've stopped supporting them - they had too many bugs and just gave up.

I've just found my NIC is actually incorrectly installed.
It's got a combo 8168 / 8111 driver installed.

The official realtek driver is only an 8111 it's not a combo driver.
IF i get a network dropout again ill try it.

So far... i've encountered it 3 times, all 3 of those times my router actually crashed along with the NIC.

Now i've got a 10/100 switching hub installed between myself and the router, so i still shouldn't have lost ALL connectivity, which is where the odd part comes in.

Yet when i restarted W7 it wouldn't reconnect to LAN even, until i had restarted the router.

Good 'ole netcom POS...

 

[Digger]

see ST. I know ya got a big brain there, so i know its useful to this thread. You just have to take things a little slower. No one is going to get a big cookie here. I myself like the discussion all the while some of it gives me new ideas as well. Either for this problem or another in a different area. Keeps you on your toes type thing.

Personally I hadnt seen the drops, thank gawd, from ethernet. Not a tick of trouble. But the explanation you just gave there, reminded me of my problem with the belkin and its driver, any driver at the time, crashing out the wlan when it dopped. Causing the ever rock solid lappy, so far, to lose connection as well. Tis why to ultimately prove that its NOT my router or your router thats the problem, i plan on putting them in client-client/mode and bridge the wifi from router to router, lan to lan. If it doesnt have drops and act like it did previously, well then i have MY answer most likely... the driver. This i may do today or tomorrow. but will definitely do, since this is the one loophole i have left to fill in my scenario.

 

[sexytool]

I know it's not my router...
It doesn't crash when i'm running XP.
I've had the same router for ~6 months before i decided to install W7.
The router was already a couple years old by the time it came with the internet plan.

 

[Digger]

I also have a similar setup... wireless/switch on one side of main router, and a switch on the other side... may add another just cuz, lol... but yea, same things here man. When i loaded the 7 driver for belkin, i had lan ax, but no inet. TS turned up nothing, tried and tried all different tricks to try and get that 7 driver to work right. Atleast it DID report correctly with the triangle and while hovering. When in 7100, it would give me the asterix or the Red X... sometimes i was connected, other times not, just didnt report it... and also the continuous drops. I had to do that trick of not connecting auto to have it actually report and connect correctly. This was the SAME story for the nvidia wired adapter. These problems of reporting atleast, i do NOT have anymore, which just that alone to me, means that work is in progress. Or that something in something was screwed up in 7100.


Edit: actually i AM adding another one, i just forgot about it. have to run a wire to the other side of house, kids rooms... not gonna depend on wifi streaming

 

[Digger]

I know it's not my router...
It doesn't crash when i'm running XP.
I've had the same router for ~6 months before i decided to install W7.
The router was already a couple years old by the time it came with the internet plan.

EXACTLY.... tis why i entered the "ethernet" thread when my original problem was wireless, i just KNEW that they had to be related. Too many similarities.

 

[Digger]

One other BIG thing to mention about the difference in 7100 and 27. This was about the non-deletion of a previously installed driver for the adapter. THis was another reason why i advise ppl to be on. If you still have 7100 installed, do this simple task.

go to device manager, also open explorer to C:\windows\system32\drivers (location of your driver). Now in DM, find your adapter, and right click uninstall, check box "delete driver.." All the while side by side you have your eye on the specified driver in explorer window. Hit ok on the uninstall box. Now did you see the driver disappear? Nope. now try and reboot. Logically, it shouldnt find any driver, especially if you have MS download driver turned off. But it does, the driver never gets removed. Reboot does nothing i found. So now, under build 27, that checkmark box is not available anymore and the uninstall ACTUALLY DELETES the driver now in 27 when you go to uninstall.

 

[sexytool]

Now that should be useful.
The "Update Driver" utility should be quite useful either way.
I think it goes by file creation date so if you zip or rar the driver you WANT to use, it should be given todays creation date.

Then update driver should pick that driver regardless.
Might be a quick fix for some who can't seem to manually switch drivers.

W7 Driver management in itself is just retarded.
Just to test, i had a 2009 driver installed off W-Update.
I "Updated driver" in the device manager and now i'm using a driver from 2007 =/

WONDERUUUUL.

 

[Digger]

Now that should be useful.
The "Update Driver" utility should be quite useful either way.
I think it goes by file creation date so if you zip or rar the driver you WANT to use, it should be given todays creation date.

Then update driver should pick that driver regardless.
Might be a quick fix for some who can't seem to manually switch drivers.

W7 Driver management in itself is just retarded.
Just to test, i had a 2009 driver installed off W-Update.
I "Updated driver" in the device manager and now i'm using a driver from 2007 =/

WONDERUUUUL.

Actually imho... it doesnt matter by the dates at all to what driver it updates to. Thing is, if you already have a "working driver" windows will say it was unable since you have it correctly working or whatever blah blah it says. I dont think it looks to it being the dates. Its not like in XP, where it says a newer driver has been found... or a file that you are attempting to overwrite is older/newer than the previous version, do you wish to continue. something to that affect. been awhile since i jumped on XP and played around, 7 confuses my brain with the msg's between them.


edit:
also it will always look to install that 7 stock driver first and foremost, you can tick this option off in windows updates. dont allow MS to download and install drivers... you have a few optinos to choose from there.

edit #2: this is the big problem and combination of problems with the non-deletion of drivers on 7100