This post originated from an RSS feed registered with .NET Buzz
by Brad Wilson.
Original Post: 802.11g Solved -- I Think
Feed Title: The .NET Guy
Feed URL: /error.aspx?aspxerrorpath=/dotnetguy/Rss.aspx
Feed Description: A personal blog about technology in general, .NET in specific, and when all else fails, the real world.
Hunting down the solution to my 802.11g problem, I even went so far as to put one set of devices on channel 1 and the other on channel 11. The problem was definitely the bridge that was in the office; the others seemed to cause no interference problems.
So I tried physically moving the bridge farther away. It was far enough away so the ethernet wasn't hooked into it, but I figured that wasn't a problem, since I was testing for interference. (You see where this is going, right?) Well, it worked great, so I found a longer ethernet cord. As soon as I got it onto the LAN, poof, my problems were back.
So it turned out the problem all along was a physical network problem, and not a wireless problem. It became a problem as the result of the firmware upgrade, which tricked me into thinking it was a wireless upgrade issue (since the firmware caused the device to move from 54g draft to 54g final). The bridges are all the same, so I took one from one place and swapped it with the office bridge, and now it seems like everybody is happy again. For the time being, anyway. :) I have no idea what the physical LAN problem might've been, but everything is working, so my curiosity is plummeting. :)
Previous Topic
