"Ethernet" Connection Drop

[sexytool]

your 7000 reg compared to 7100 reg pre Tweak7 tweaks, with Tweak 7 tweaks, and after tweak7 reset default.

Making a SINGLE image of the registry can take 1/2 an hour.
You want me to make 5?
These files are 30-50megabytes each digger.
Plus i don't have my beta 7000 instal anymore, i deleted it's partition and re-created it for 7100 RC1.

7100 reg pre-tweak 7 is impossible now unless i were to format and re-install W7 - something i'm not inclined to do just to grab a couple of lines from the registry.

I can however link YOU to the program and YOU can make an image of your own registry. That will give you a great starting point.
From there you can tweak 7, make another image
then "un" tweak 7.
However, then it'll probably take quite litterally, months for you to pour through the 30,000 odd lines of text that make up the windows registry.

An Alternative option is to export your whole registry in regedit before making any changes.
Then set Kaspersky to monitor registry changes.
Then Tweak 7, check kasperskys' logs and view the changed registry locations.
Then "Un" Tweak 7 and again, check kasperskys' logs and view the changed registry locations.

 

[Digger]

Making a SINGLE image of the registry can take 1/2 an hour.
You want me to make 5?
These files are 30-50megabytes each digger.
Plus i don't have my beta 7000 instal anymore, i deleted it's partition and re-created it for 7100 RC1.

7100 reg pre-tweak 7 is impossible now unless i were to format and re-install W7 - something i'm not inclined to do just to grab a couple of lines from the registry.

I can however link YOU to the program and YOU can make an image of your own registry. That will give you a great starting point.
From there you can tweak 7, make another image
then "un" tweak 7.
However, then it'll probably take quite litterally, months for you to pour through the 30,000 odd lines of text that make up the windows registry.

An Alternative option is to export your whole registry in regedit before making any changes.
Then set Kaspersky to monitor registry changes.
Then Tweak 7, check kasperskys' logs and view the changed registry locations.
Then "Un" Tweak 7 and again, check kasperskys' logs and view the changed registry locations.

dude, seriously... get up, walk around some... have a smoke or something....lol. i said all that in my last post in gest. Yes, thats what i would need, but i wouldnt have expected you to think about doing so unless you were very highly enthused about what it is and what and how to solve. I didnt expect that at all. I just dont like not knowing why something is the way it is.... i rarely take things at face value.

fyi, shouldnt take a 1/2 hour, it would just be a reg backup, couple minutes tops... you arent saving it to a floppy drive, lol...unless that registry has overgrown itself from XP.. but anyways, i am calling it a day, a full day... later on.

You wouldnt have to pour thru the registry if you know what to look for, and all you would do is to compare the reg files, searching for any differences. programs out there to do this. also programs that monitor the registry for the hyper-paranoid type. I'm no guru, but i've been around the reg block a time or two.

Oh, yea, and your kas i just seen you mention, may be one of the causes of your problems as this is a bear of a program. Just search around on the security forum for kas and the problems found. Even I had issues with it, tho i admit, this WAS an install on 7000. I have turned my back to them since, and not installed on the RC. Maybe thats your problem, get rid of that thing and install Avast!

 

[sexytool]

Nah i'm right thx
I've been administrating networks since before i could drive.
Before i finished year 10 i knew the ins and outs of DoS and Win95 + 98 networking lol.

I've got a fair bit of experience up my sleeve by now, so usually any problem i run into, i can fix.

If it ever gets to that stage, i'm not affraid to just go "Ah f**k it!" and format it.

Sometimes a full format is a faster resolution XD

 

[tongteh]

guys.. getting too technical ow.. is there any way i could boot up into windows vista now? i just need a stable connection!!

 

[Digger]

well, there is really no need to do much testing anymore. Guys this is all driver based. Non compatible drivers. You may find one thats maybe 80% compatible, but not 100%

Case in point: The Red X

Now i came into this thread becuase of this, and also just to see if and what similarities there were between the two, keeping in the back of my mind the overall driver concern. Now, I have found that both the wireless AND wired act the exact same way in appearance.

For example, with my wireless connection and the rex X, I found that unticking "connect automatically" and connecting manually each time "made the asterix and the X disappear". I just ran some initial driver testing on the ethernet, having the wireless situation in mind, and what do you know.... I have found that they all act in a similar fashion.

If i disable the network adapter ( causing it to not be enabled therefore not trying to connect and identify itself on the network at startup/boot like i had the wireless set to not connect auto) before i rebooted, then reboot, then come back to the desktop ( you will see the network icon trying to identify with the circle/busy icon) and then enable the ethernet adapter in question, and voila, dinner is served, no red X, everything atleast LOOKS good to go. Tho in actuality, this doesnt solve the whole issue of having a correct driver.

No matter what driver i have tried to installed, be it W7, chipset manufacturer, MB manufacturer. No matter what comp mode. I always get the same results, and find that it only enables/shows the controller as 10/100 instead of 10/100/1000. So just right there i know i driving down the road with two flat tires. Like i keep stating and repeating, this is a driver issue first and foremost, and until that is addressed, any other problems can then be fixed. But if you take a look around, not everyone is having these issues, its about 50/50 i'd say. Ones whom have a correct working driver for their ethernet/wireless will not see these effects/problems and results.

really no need to do any kind of network testing at all, be it lan or wan, when its going to be a hit and miss issue of connectivity. Like i also keep repeating, my drops/connectivity were never part of some pattern, it was all very random, as i have found that to be the case here for most ppl in this thread, especially the actual creator of this thread tongteh.

 

[Digger]

now to satisfy and rectify someone's urging me of this reset to default setting of the program tweak7... ahem.... did nothing....no good at all. Why maybe others ask? Thats because i never used it in the first place to change any variables/settings that would have and did ultimately cause problems for someone by doing so, and the FIX FOR THAT was to reset back to windows 7 defaults.

This may affect the browser and a few other settings if tweaked and played around with, who knows, you would have to closely watch the registry. Maybe an install of tea timer, but i had a bugger or two with that on 7000 so i tossed it. But by overall, this program, atleast with those specific page tweaks7 you are referring to,( as there may be others that affect different properties of hardware, like cpu tweak, gpu tweaks and so on) is not tweaking the chipset to work with the given driver thats not a true working driver in the first place.

If you thought this was the fix all, how come the entire sevenforum.com community hasnt came in here to back up your claim? One reason being is that like i said, 50% guesstimation doesnt have this issue as they have a correct working driver. And the other 50% in this thread didnt all use Tweak7 to change any settings, atleast they arent speaking up. Changes may have been done, like myself, thru the driver advanced properties tab. And maybe 1% made some manual registry changes. Cant you clue in here a little? I think you are a little arrogant and presumtious yourself that your answer could be and is the holy grail, when common sense tells a different story.

My overall explantion is this, 90% of ppl with ethernet cards 1.5 years or newer have a correct working driver. Its the older and freakish chipsets that have been coming into this thread (with maybe a 10% exception) and reporting problems, the same problems.

 

[sexytool]

Buddy, you've never even told us what your NIC *IS*, so how are we supposed to use our good judgement to determine wether it's an NIC problem or a registry problem, if you don't give us the information required for us to diagnose your problem?

You said your NIC has Vista support + drivers so the automatic assumption is it's less than 1.5 years old and should work fine under W7.

You put yourself in this position by not handing out the correct information to begin with =/

EDIT: And the information you HAVE given us, is very errornous. Your K8N-SLI deluxe does NOT use a Marvell 88E8111 Gigabit LAN PHY chip, it uses a CICADA8201 Gigabit LAN PHY chip.
Tried installing the nForce system utility and driver package?

EDIT #2: Now at least, we can say for certain and have verified it's not a W7 issue.
You're using a driver that's not designed for W7 and your hardware probably never WILL HAVE a W7 driver.
That's not through any fault of microsoft, it's not a compatability issue, it's simply because the NIC is probably too old for the manufactorer to BOTHER writing a W7 driver.

 

[sexytool]

Sorry for the double post; Thought it prudent to mention;
I just got my ethernet connection drop out on me =/

Jynx me much Digger? hehe, just kidding.

In all seriousness though, i didn't get it at all for a week. Then twice in 1/2 an hour. Now 3 days later i get it again.

Today i fixed it by disabling and then re-enabling my NIC in the device manager.
No need to restart thankfully.

 

[Digger]

see... you missed my post before about how i was going to run "your test" after i ran mine... Dont be sho gung ho and trigger happy trying to find something wrong with what i have posted just because your theory and fix was debunked.

You are correct, its not a marvell... on a google search last nite being up 23 hours str8 i didnt see the misguided link to the GA-8N sli pro... instead of GA-K8N sli pro... never stated deluxe tho. And yes, i have tried everything as far as drivers go, unless now i find some obtuse driver for this chipset... or get this XP driver for the board to work, which seems doubtful, but a hunting i shall go. the nvidia 4 forceware didnt fix btw.

 

[sexytool]

There's been a few scenarios where i've had to use a win2k or 98SE driver for XP.

If you have the option to install a 2k or 98 driver, please give it a shot.
Unfortunately for me, i think i'd have to actually visit the M$ site and get the newer driver manually.

Windows update failed to install my "updated" driver stating a reboot may be required.

Well, i've rebooted about 3 or 5 times since then and it's still not installed =/

 

[Digger]

for everyone here... i wouldnt normally do this at all.... but after my findings today.... get your hands on a 7127 build....... this fixes just about everything i've thrown at it so far.... i'm still working on my own wireless problem project, that could be still on my end, like i said before with the drops. Tho it does accurately report ethernet after many reboots, with the adapter still enabled before and after reboot.

As far as connection drops. When running same tests i did for wireless against Ether, i still seen some of the same unusual spike drops, especially outbound. Very close to an incrimental pattern i seen, as not so much with the wireless, more random there. But that was just one test, and i didnt have my eyeball glued onto the connection graph for the whole time. This could have meant that the connection dropped and picked right back up, moving traffic right along. If that was the case, then i am more apt to blame my router. More to still be determined as far as that goes.

i shall run more tests on the 7100 Ether and glue an eyeball for a longer period, and also implement some software and options that once connection is lost, it wont try and reconnect. Also tested the lan, which i've yet to see any noticeable problems, be it streaming to extender or just exploring around on the lan transferring files, viewing, using, etc.

This just flames anger that MS couldnt have waited and tested the PUB RC to find all these problems. Besides this problem, the IE update (crashing) 2 of them, and then the x86 root security flaw, i cant BELIEVE this was allowed to happen. Two days later, the 7th, in the afternoon, they compile the 27. FFS.

 

[themouse]

I have given up trying to figure out a way of fixing this issue. Yes my hardware is 3 years old but come on MS my realtek 8139 is such a generic chip this should not be happening. I have found that disabling the device and enabling it dosent work for me only a reboot. I have plugged in a usb/ethernet for now but it only runs at 10mbs its really annoying but with such a flakey connection with the onboard I have no choice or I dump win7 till its fixed. I have tried everything different drivers etc. For me build 7048 was great after that it was broken, I dont think its a driver issue I think its deeper than that.

 

[Digger]

I have given up trying to figure out a way of fixing this issue. Yes my hardware is 3 years old but come on MS my realtek 8139 is such a generic chip this should not be happening. I have found that disabling the device and enabling it dosent work for me only a reboot. I have plugged in a usb/ethernet for now but it only runs at 10mbs its really annoying but with such a flakey connection with the onboard I have no choice or I dump win7 till its fixed. I have tried everything different drivers etc. For me build 7048 was great after that it was broken, I dont think its a driver issue I think its deeper than that.

try disabling adapter before reboot, then enable it after you login. Does that do anything?

Even if, try atleast installing 27 on a new partition, keeping the 7100 part, and tell me if you still have the same issue.

 

[jesseftw]

LAN wired connection drops randomly, constantly

Here are my system specs:

Motherboard: ASUS P5N32-E SLI BIOS v1205
Processor: Intel Core 2 Extreme Q6850 @ 3.00 GHz
Memory: 8 GB DDR2
Video Card1: ASUS NVidia GeForce 8800 Ultra 768mb
Video Card2: ASUS NVidia GeForce 8800 Ultra 768mb

I formerly had Windows XP x64 running on a small SSD. I yanked that and installed Vista x64 Ultimate on a clean HDD. Then upgraded that to Windows 7 RC Ultimate.

Ever since ?grading to Windows 7 my internet connection has been dropping frequently, when in use. I'm on a wired direct connection to my router. It's to the point where it's pretty much unusable. Fortunately, it's one of five computers in the house.

I've got 4 other computers: 1 wired, 3 wireless; one running Vista x32, and the other 3 running XP x32. I've got 2 broadband lines from 2 different ISPs, 2 routers from different manufacturers (Netgear, Belkin), and loads of spare, good ethernet cable. As you can imagine, I did plenty of mixing it up with the hardware to make sure that wasn't the problem.

This is either an issue with windows 7 or possibly a problem with my motherboard firmware or lan drivers? As a side note, I have been having some trouble with the display drivers too. Once in a while the screens (2x 1920x1600 Planar PX2611w) will flicker off and back on. As a side note, my USB speakers cut out once in a while and I must restart the system to get them back. They're still recognized by the device manager but no sound comes out.

When the internet connection problem occurs, I get the small yellow exclamation triangle on the network icon in the taskbar. Hovering on it reveals: "Network: No network access." To recover from this, I right click the icon and select Troubleshoot problems. So far, doing this has always been able to repair the connection and then I'm good to go... for another 5 minutes.

I've read all 18 pages of this thread so far and countless other threads with no real solution so far. I have unchecked "Allow the computer to turn off this device tos ave power" in the Power Management tab of the Network adapter properties in the Device Manager. That hasn't helped. I'm current with all the Windows updates.

If anyone has any other ideas or would like more info from me, please let me know. Thanks in advace for your help!

 

[Gene]

My connection was stable for over a week. I decided just for grins to install build 7127 which I did yesterday. I have since had two lost connections. 7127 is not a fix, at least for me.

 

[Digger]

My connection was stable for over a week. I decided just for grins to install build 7127 which I did yesterday. I have since had two lost connections. 7127 is not a fix, at least for me.

Hmm... well to be accurate here gene, I havent "noticed" any drops ethernet wise. But i havent had time to test my same problem via wireless as you have with wired. 7127 did however resolve the "reporting of" correctly the status of the connection. To as where it wouldnt in 7100, even while using the exact same drivers for both builds. I no longer have to fiddle around with it to get it reporting accurately.

I didnt scroll back, and go over what info you provided gene, sorry bout that, but i dont recall if you ever swapped out your router. I think i recall you saying that you did buy another nic, with same results. I would check if it could be your router or wires for that matter. Tho my hunch is that you havent gotten a proper driver installed still and THAT could be your only problem, how did that work with the 7127? Have you done any problem reporting to MS concerning that setup.exe. What did the program troubleshooter tell you to run as? In my case, mine is working, but how well I'm still up in the air about. As it still doesnt report it as a gigabit card. And no option to change to 1000/100/10. Tho while currently NOT on my gigabit router (sitting on the sideline not usable atm), this could be the reason why.

I plan on putting the wireless pre-existing drop problem to the test this week since it does atleast report, and reconnect correctly without errors or issues. I'm interested to see if i still have the drops still, using the same drivers. If you recall, on 7000, none of these were a problem for me atleast, be it wired or wireless.

 

[Gene]

It is different. Almost certainly a driver. It works without peoblem for simple browsing or Email. Load it with P2P and it drops - showing limited connectivity. All I have to do to fix is to disconnect followed with connect - much different than before. The router is a new Linksys wireless N - never a problem with my laptop which is running Windows 7 Beta.
I just reloaded the driver. It that is still a problem I will give ethernet a try. That was also a problem in the past as it was with so many others.

 

[Digger]

It is different. Almost certainly a driver. It works without peoblem for simple browsing or Email. Load it with P2P and it drops - showing limited connectivity. All I have to do to fix is to disconnect followed with connect - much different than before. The router is a new Linksys wireless N - never a problem with my laptop which is running Windows 7 Beta.
I just reloaded the driver. It that is still a problem I will give ethernet a try. That was also a problem in the past as it was with so many others.

ok, instead of stressing the network with P2P... try testing the DL with downloading the RC from MS... and see if it drops JUST while doing that... if you get past 50%, by then you can cancel, you should be fine. For the upload, you can try using skydrive or any service that will allow you to upload somekind of zip file with a decent file size... atleast 25mb or higher. Skydrive allows 90mb file size or smaller. You could also use an ftp program to test both up and down with a buddy. This wont push you to the limits, but will provide yet another constant variable as far as just the connection drop, while it may not stress test it, still good to know. Or if you're lucky enough to find a test server or something that can stress both your up and down. What % of your upload do you allocate to the p2p app? If you end up testing your connection in all these other ways and dont experience a drop, well, then you have your own answer, most likely.

 

[themouse]

I have just installed build 7127 I really am hoping this helps my issue. When my adapter fails disabling and re enabling the device cant fix it only a reboot I have tried all sorts of drivers, I can not believe this is a driver issue as I have tried 6 different ones it seems to be deeper than that.

I will let you know if the new build helps

 

[Digger]

I have just installed build 7127 I really am hoping this helps my issue. When my adapter fails disabling and re enabling the device cant fix it only a reboot I have tried all sorts of drivers, I can not believe this is a driver issue as I have tried 6 different ones it seems to be deeper than that.

I will let you know if the new build helps

I will have my ears to the wind