Top 10 Things a WiFi Installer Does Not Want To Hear...

-

Here are the top 10 things (IMO) you don't want to hear from a customer when you arrive on site to install a new WiFi network (I compiled this rather quickly in a flippant moment - please don't take it too seriously...):
  1. Our networking guy, who was going to be helping you today, isn't available, I'm afraid he's... (choose from the following):
    • On a late shift
    • Off sick
    • On leave
    • Over-slept
    • Double-booked
    • Left the company
    • Had a baby
    • Buying a radiation suit
  2. Oh, you wanted POE ports for those APs?
  3. Our goods-in department has definitely received the kit, they're just not sure which part of the hospital it went to...
  4. Oh, we thought you were bringing the kit with you. No, we haven't received anything.
  5. You know that 500-person call-center where you said we might have issue with personal hot-spots? The good news is, we've introduced a policy of 'no personal hot-spots' in that area! As a sweetener, we gave all of the operatives a bluetooth headset, mouse and keyboard each. We also threw in 5 new microwave ovens for their rest area, together with 10 new security cameras to monitor all that new gear.
  6. We've changed out minds. We'd really like to be able to run video and voice across the network as well. Can you squeeze that in whilst you're here?
  7. Our CEO has a new iPad and he'd really like to be able to use it on the wireless network. I know it wasn't in scope, but it's really important...
  8. Well, the salesman said it would support <insert unsupported feature here>.
  9. We've decided we would like a bit of coverage outside of the building after all (the CEO is a smoker). Can you move a couple of APs a bit closer to the windows near the smokers area?
  10. The cabling guy has assured us that you'll have no issues with 120 metre cable runs...
I'm sure there are plenty of others... :)

Nigel.

Popular posts from this blog

The 5GHz “Problem” For Wi-Fi Networks: DFS

-
Image
Wi-Fi networking provides us with 2 bands for the operation of wireless LAN networks: the 2.4Ghz band and the 5GHz band. The 2.4GHz band has a reputation of being something of a “sewer” of a band, due to its limited number of usable channels, the number of Wi-Fi devices already using the band, and the high levels of non-Wi-Fi interference that it experiences. Many wireless LAN professionals will generally advise that you put your “important stuff” on the 5GHz band whenever possible. 5GHz has far more channels available, a corresponding lower number of devices per channel, and generally suffers much lower non-Wi-Fi interference. However, beneath the headline of “2.4Ghz = bad, 5Ghz = good”, there lurks a shadowy figure that can be troublesome if you’re not aware of its potential impact: DFS. Background Wi-Fi networks operate in areas of RF spectrum that require no licence to operate. This is in contrast to many other areas of the radio spectrum that generally require some form of (p
Read more

What Are Sticky Clients?

-
Image
One term you'll often hear banded about when talking with Wi-Fi professionals is "sticky clients". I thought it might be worth spending a few moments exploring what is meant by "sticky clients", why they are generally considered to be a bad thing in Wi-Fi networks and some approaches to mitigate them. Background Many folks dealing with Wi-Fi networks often talk about the "sticky" characteristics of wireless clients when discussing client roaming within a W-iFi network. In an ideal world, we'd like to have access points providing ubiquitous coverage across our desired area providing high-quality, consistent client coverage where-ever we go. In this wonderful land of rainbows and unicorns, our clients would gracefully roam from AP to AP, detecting and associating with their closest AP throughout the coverage area to ensure their best connection speed at all times. Unfortunately, the real world doesn’t quite reflect this roaming-client
Read more

Microsoft NPS as a RADIUS Server for WiFi Networks: SSID Filtering

-
Image
The Microsoft Network Policy Server (NPS) is often used as a  RADIUS server for WiFi networks. It can provide authentication and authorization services for devices and users on a wireless network in a Windows Active Directory environment. In this article we look at how we can use NPS to provide authentication for WiFi users across a number of SSIDs. We have previously discussed how to authenticate groups of users using the same SSID and then assign them to a VLAN that is appropriate to their security authorization. However, there may still be instances where two or more SSIDs are in-use on a wireless network and we would like to base policy decisions on the SSID that the authentication request is being generated from. As an example, if we consider a school, perhaps we would like students to only be able to authenticate if they connected to the SSID: "Student_Net". Similarly,  staff should only be able to connect using the SSID: "Staff_Net". This would
Read more