8 Jul
2004
8 Jul
'04
12:40 a.m.
In our experience, wireless is fine for casual internet connections,
thin clients (terminal services, citrix, rdp) but much too slow for
anything that involves any level of data transfer. We sell and support
medical software that transfers very large databases. I have lost count
of how many offices have implimented wireless networks without checking
with us first. They usually scream bloody murder when we inform them
they will have to revert back to wired networks. It seems mostly the
doctors brother-in-law reccomended wireless.
I use wireless 802.11g at home for my kids and wifes internet
connections. All of my Unix boxes are wired. Since I'm again an
apartment dweller, the mgt company frowns on racks and patch panel
installations.
Christopher McNabb wrote:
Interesting, because we have LOTS of wireless here at Virginia Tech
and oh yeah, it works fine. I'm on a wireless connenction right now.
The house I live in is 175 years old and is on the Federal Register of
Historic Places. The walls are 16" thick brick - even the interior
walls. Because the building is protected, I couldn't run a wired
network, so we went with wireless. It works fine, even through the
very thick walls and floors.
I think that wireless installations that are slow and/or unreliable
probably have configuration issues or interference from other sources.