My Desktop/Storage PC went down during a power outage. After power was restored, I found that I couldn't surf the Internet. I checked the LAN interface in Network Connections and found that it didn't have any TCP/IP values. Usually, they have at least 0.0.0.0 as its IP and Subnet Mask but in this case, it was just blank.
I tried disabling and repairing the LAN network connection but its TCP/IP values were still blank. After I tried repairing the connection, I got this message - "Failed to query TCP/IP settings for the connection." I also tried disabling and enabling the IPX/SPX and TCP/IP protocols and then tried removing them but all that didn't work.
After a bit of research, I uninstalled all my Network adapters in Device Manager and rebooted. My network adapter was immediately detected again after startup. This fixed my LAN network connection and I was able to surf again.
Showing posts with label Networking. Show all posts
Showing posts with label Networking. Show all posts
Linksys WRT54G v7 Piece of Crap Router
I sometimes wonder why, of all the WRT54G router models my family could have gotten as our home broadband router, we ended up with the only version that used an Atheros chipset that is unsupported by any alternative firmware - DD-WRT, OpenWRT, Tomato, etc., instead of the more common Broadcom chipset which is widely supported. Not only does it limit the possibilities we could eventually perform with the router, it also limits its resale value.
This WRT54G version 7 model is a piece of crap which Linksys should never have produced. It seems Linksys has learned its lesson, and has since brought out later models only with the Broadcom chipset.
Problem with WRT54G v7 Router and Broadband Connection
We've been having issues with our router and/or shared broadband connection here at home for the past few days. My first thought was that P2P downloading from two machines on our home network were eating up bandwidth and causing the browsing slowdown or connection failures on other machines. A symptom of this would be the inability to connect to the web admin interface of the router. In the past few days, many of us in my family who depend on web access to do our work, were frustrated and had a very difficult time in completing our jobs.
Since my wife urgently needed unhindered, continuous, and stable web access, I had to block all TCP/UDP ports above the list of well-known ports which are between 0 and 1023. That includes most ephemereal ports. I blocked TCP/UDP ports 1025 to 65535 on our Linksys WRT54G v7 wireless router which still had the default firmware of 7.00.0. This allowed most of us who relied on the web to be able to continue with our work uninterrupted.
The problem was that my brother, who pays for our Internet connection, owned one of the machines that was doing the downloading. I could not block ports 1025 to 65535 permanently. Another reason why I felt that blocking the ports permanently was not a good solution, was that, at some point in the future, I was also going to be doing some P2P downloading.
Since my wife urgently needed unhindered, continuous, and stable web access, I had to block all TCP/UDP ports above the list of well-known ports which are between 0 and 1023. That includes most ephemereal ports. I blocked TCP/UDP ports 1025 to 65535 on our Linksys WRT54G v7 wireless router which still had the default firmware of 7.00.0. This allowed most of us who relied on the web to be able to continue with our work uninterrupted.
The problem was that my brother, who pays for our Internet connection, owned one of the machines that was doing the downloading. I could not block ports 1025 to 65535 permanently. Another reason why I felt that blocking the ports permanently was not a good solution, was that, at some point in the future, I was also going to be doing some P2P downloading.