"Ethernet" Connection Drop

ha! after further review of my belkin G. I know this cant be a good driver. the install via XP SP2. I just went to driver/advanced... and it came to my attention that while i have some freak values to be set that i havent seen normally, there ISNT a value to change channels of all things.

On 7100, i recall when installing under Vista SP2, the driver was a athrusb.sys . Now when i installed the same setup.exe under XP SP2 the driver is named BLKWGU.sys. Two totally different drivers there. Not as if it installs the SAME driver for each comp mode, then does a few tricks on it to get it to be compatible with 7. All it does is just use the driver from previous OS, it just doesnt load it all completely is what i think. With the athrusb.sys i could change the channel. Even when firing up the belkin utility, there is no option to change channels there either. So... a hunting i shall go... again.

So, actually ST, you are kinda right. It wasnt me as a user error on this, as more it was like an OS error back on 7100, atleast as far as installing drivers goes in comp mode. I'm 100% sure that i DID install actually under XP SP2 comp mode, only thing is that during those installs, i'm not quite sure THO if i did a manual delete of the old whatever comp mode install of, and then do a "fresh" install of it under XP SP2 mode. Therefore, it wouldnt change the driver, which i never seen it do, always displaying the athrusb.sys. But i ALWAYS got the belkin utility with it everytime nevertheless.

whoa, that was a lot of reading . I take it Digger you are having issues with your Belkin as well? We all seem to be gluttons for punishment the thing is I have got so used to win7 and i like the way it works so much i cant stand to go back to XP! so the fight continues. for some unusual reason last night i was able to watch an HD movie over my network with out incident. it must be a clam before the storm........

I do keep wondering though, we keep trying all sorts of driver combination's and still end up with the same problem. Surely it can not be a driver issue hence why i feel its deeper than that.

k i lied problem still happens. it seems to occur more when im torrenting AND downloading through FF and browsing at the same time. seems that the downloading through FF is what really sets it off while torrenting since browsing and torrenting was working just fine. the only things is have not toyed with is some settings to the tcp/ip stack like the auto tuning feature may be at fault otherwise i will either wait for a new driver or try out the newer build.

Solace said:

k i lied problem still happens. it seems to occur more when im torrenting AND downloading through FF and browsing at the same time. seems that the downloading through FF is what really sets it off while torrenting since browsing and torrenting was working just fine. the only things is have not toyed with is some settings to the tcp/ip stack like the auto tuning feature may be at fault otherwise i will either wait for a new driver or try out the newer build.

hehe... no problem. Another one's input is good anyhow. Tho i wouldnt go blaming FF, as i dont use it at all. This is mostly drivers, again. find all the possible drivers for your adapter, new and old, XP, Vista or 7. Tho i found that 7's havent been to reliable for me personally.

While searching around, and having a migraine headache with these two wireless adapters. I noticed one of the error reports i viewed after a drop, metioned the MSM helper class as a problem. I did a little research on this, and there was a BIG problem back with Vista, and it not being able to keep or get a connection to some routers. Released June 2008.

source: Windows Vista cannot obtain an IP address from certain routers or from certain non-Microsoft DHCP servers



I also ran into an idea of trying to solve by disabling the IP Helper service. Tho mixed reviews/results were with this.

Just throwing out a bone.

upgrade to 7137 today, and I experienced my first - internet connection lost. checked my setting as to NO AUTO shut off to conserve power.
2 internet connection lost. still checking what changed. all set to NOT CONSERVE POWER. 3rd IC lost. Finally I reset TCP/IP from 10 (default) to 39. (why 39 - no reason). no more IC lost.

Digger said:

hehe... no problem. Another one's input is good anyhow. Tho i wouldnt go blaming FF, as i dont use it at all. This is mostly drivers, again. find all the possible drivers for your adapter, new and old, XP, Vista or 7. Tho i found that 7's havent been to reliable for me personally.

While searching around, and having a migraine headache with these two wireless adapters. I noticed one of the error reports i viewed after a drop, metioned the MSM helper class as a problem. I did a little research on this, and there was a BIG problem back with Vista, and it not being able to keep or get a connection to some routers. Released June 2008.

source: Windows Vista cannot obtain an IP address from certain routers or from certain non-Microsoft DHCP servers



I also ran into an idea of trying to solve by disabling the IP Helper service. Tho mixed reviews/results were with this.

Just throwing out a bone.

i have multiple services disabled and a static ip so no it cannot be that. those are things i do at first install and the issue happens on fresh install and tweaked.

Solace said:

i have multiple services disabled and a static ip so no it cannot be that. those are things i do at first install and the issue happens on fresh install and tweaked.

right, as neither do i, for the most part. I just thought if THIS was a problem, as small as it seems, no telling what other problems leading up to, or down the river this may have caused in 7.

Same as the IP Helper service. dont think this is the answer either honestly.

sexytool said:

That's the page i had open when i was writing my last post :P
Re-read my post. I never called those 'tweaks' those are features.

Tweak 7 modifies registry values for better optimised speeds.
Drivers modify registry valules for better optimised speeds.

See the similarity?

Tweak 7 offers you the option to reset your values back to default.
Your drivers, don't.
Un-installing your drivers, will not reset your settings back to default.

So the ONLY way to get windows 7 back to DEFAULT settings, is tweak 7.

I'm not telling you to "Not add tweak 7" i'm telling you Tweak 7 will fix the issue your drivers caused in the first place.

The problem originates in SVCHost coding.

wrong on so many levels.
tweak7 is horribly incompatible "well i shouldn't say this but for the networking tweaks it is" i was monitoring the changes in regedit except for the fact it was asking for permissions to change certain values in registry except when i allowed changes to be made no values were even changed... if you want a windows tweaker for vista/7 Ultimate Windows Tweaker 1.2. google it free/useful

being that said just for the hell of it i hit the default button and rebooted and all loaded up utorrent with the newer builds of win 7 torrenting away on 2k+ peers and what do you know it drops after a few minutes.

i have also screwed with the advanced options more under the drivers nothing in there seems to help/affect the issue.

also for those who read this far this is not a router problem nor is there anything you can do about it at the current time, this is a driver/win7 issue that is only resolvable by a future build/driver update.

there is only two other things possible left to try which possibly could fix this which is to enable the registry setting to seek max tcp/halfopen value in the file it sits into then patch the file to a set limit/no limit "this is the only change i know Microsoft has done that relates to half open limits...." http://support.microsoft.com/kb/969710

option two is somehow snag the drivers from 7068 or prior and see if they are compatible with the current builds which i believe there should not be a issue.

also have not tried uninstalling the 7127 drivers prior to installing the nforce chipset to see if previous drivers are at hand... one of the most common issues to cause problems except i dont believe that to be the solution since the drivers work perfectly fine tbh i could go a motnh without DC up until i torrent.