alloo
New member
Have you all tried disabling the windows firewalls, and I mean all of them? Have you tried disabling the security software firewalls?
My Computer
- OS
- windows 7
I tried disabling the windows firewall once, not sure what you mean by 'all firewalls' but i only use the windows one.
Ok more information.
The issue is most likely a TCP handshake issue. When the network connection 'fails', I am still able to perform ping and nslookup commands. This is consistent with the symptom of open connections remaining open, since you've already established the TCP connection. Ping just sends ICMP and nslookup by default uses UDP so neither of those require a TCP connection to be established.
Motherboard type and/or NIC chipset(s) having the problem
CPU Architecture (x86 or x64)
- Gigaybyte i45, Realtek 8111 LAN (also have second Biostar i45 system w/Realtek 8111 LAN with same exact problem)
Upgrade or clean install?
- Intel QX9650 (X64) (both systems)
Driver details (i.e. manufacturer and version of driver experiencing connectivity issues)
- Clean installs. Tried both W7 32 and 64
Problem description (LAN? Internet? Frequency?)
- Tried native MS drivers, tried latest Realtek W7 8111 drivers from their website, also tried Realtek Vista driver in W7's Vista compatability mode.
- I also bought a D-Link DFE-530TX PCI add in ethernet card with the onboard LAN disabled. (same problem)
Solutions or Suggestions
- Internet browsing (Firefox and Explorer) starts out very responsive. After a few minutes I see an increase in server timeouts and dropped connection issues. It continues to degrade until I restart the system. (disabling ipv6, power management and uninstalling anti virus and firewall SW has no effect)
- Reverting back to Vista solves the problem
Motherboard type and/or NIC chipset(s) having the problem
CPU Architecture (x86 or x64)
- Gigaybyte i45, Realtek 8111 LAN (also have second Biostar i45 system w/Realtek 8111 LAN with same exact problem)
Upgrade or clean install?
- Intel QX9650 (X64) (both systems)
Driver details (i.e. manufacturer and version of driver experiencing connectivity issues)
- Clean installs. Tried both W7 32 and 64
Problem description (LAN? Internet? Frequency?)
- Tried native MS drivers, tried latest Realtek W7 8111 drivers from their website, also tried Realtek Vista driver in W7's Vista compatability mode.
- I also bought a D-Link DFE-530TX PCI add in ethernet card with the onboard LAN disabled. (same problem)
Solutions or Suggestions
- Internet browsing (Firefox and Explorer) starts out very responsive. After a few minutes I see an increase in server timeouts and dropped connection issues. It continues to degrade until I restart the system. (disabling ipv6, power management and uninstalling anti virus and firewall SW has no effect)
- Reverting back to Vista solves the problem
I finally eliminated all my ethernet/internet dropped connection issues. (After struggling for several weeks swapping NICs, drivers, clean W7 reinstalls and implementing various configuration suggestions)
As a last ditch resort I decided to swap out my wireless Linksys WRT54G router and replace it with a spare Belkin wireless router I had. All the connectivity problems instantly went away. I put the router back in the data path and all the problems came back. (Even after I flashed in new Linksys firmware).
I had previously totally eliminate the router and went straight from NIC to broadband ethernet and the problem stayed the same without the router in the data path???
This Linksys router still works great with Linux, XP and Vista but does not like W7. However shouldn't a router should be O.S. agnostic? (not knowing or caring anything about the O.S.!!)
Summary:
In summary I need a router between my PC and my broadband source for reliable connectivity but it can't be a Linksys.
I believe that there's some strange conflict between W7, NIC drivers, Linksys and internet/ethernet communication protocol.
If you have a similar issue try a different router.
Actually now i have been getting more problems of instability. After a few hours after teh changes sugested by guitardog it's been worse....