I believe that my current Dlink router is causing my internet to drop whenever I am loading multiple tabs in Firefox or doing any kind of heavy browsing or downloading. So I figure I will try and get a new router to see if it is actually the problem.
This one is a 4 port wired router, and I want to stay wired for my PCs and Xbox, but I would also like to have wifi for my phone and stuff. What router would be the best choice? Not looking to spend much on it, if possible.
Thanks!
Its not your router.
This problem seem to have a commen occurence now so I ripped this next part from a site. SO EVERYONE TAKE NOTE> IF YOU HAVE DROP OUTS ON THE WIRELESS NETWORK THIS IS WHAT TO LOOK AT TO SEE IF ITS IN FACT CAUSING THE ISSUE. Here we go
Computer Browser Error Causes Wireless Network Connectivity Problem
Here is what is really happening. You can prove it with your computers own system event logs. (The logs are under Administrative Tools -> Event Viewer -> Windows Logs -> System)
Depending upon how long it has been since your computer dropped its wireless connection and you look in the Event Viewer, these events may be right up at the top, or you may have to scroll down a bit to find them.
The tale tell sign of Browser Elections from NetBIOS breaking wireless network connections is a pattern of 3 system events that all occur with the same time stamp. The easiest way to find them is to look for the Source of BROWSER. That will be the first of the three events. The other two events will be the TCP/IP NetBIOS Helper service was successfully sent a stop control, followed by The TCP/IP NetBIOS Helper service has been stopped.
The next events may vary depending upon how your computer is set up, but will include one indicating that the TCP/IP NetBIOS has successfully started. This is why your Windows 7 system does not know that it has lost wireless connectivity. It THINKS the link is still working and will not change the system tray icon to show a disconnected network because TCP/IP (which is what it is actually using for networking) is working normally.
Unfortunately, another service gets knocked offline during this cascade of system events that does not get restarted. The WinHTTP Proxy Auto-Discovery Service, which should be completely unnecessary for a system using legitimate networking standards, enters the stopped state and does not restart.
This prevents your computer, not from networking and sending packets, but rather it prevents your system of having any idea what to do with that traffic. The stink of this whole thing is that if Windows 7 wireless networking worked well enough without all of these helper services, none of this would be a problem for Internet connections because the DNS Servers would still be running. But, Windows 7 wireless configuration is too dumb to use DNS Servers for Internet traffic, because it worries more about local area network traffic. Without one of the LAN services there to tell Windows to send those packets to the Internet and use the real networking protocols standards, it flails about like a helpless child.
Unfortunately, the next event is the one that gets the WARNING icon and label and it says that there is a DNS problem. Oh, that isnt a Windows issue, is it? I guess youll need to go waste hours of your time seeing if there is a DNS error. Even worse, if you re-enter your DNS settings or otherwise change the configuration of your wireless adapter enough to cause a full network subsystem restart the problem will go away
until the next time, because the problem was not with the DNS configuration in the first place.
All credit must go to this guy
http://besthubris.com/computers-internet/wireless-network-drop-connection-windows-7-error/