Hi Shayne,
On 28/02/17 11:23, Shayne Ghere wrote:
> Last count, we have 51 Apple TV's, but they aren't on the same network we're
> having problems with. The TV's are either hard-wired or registered on a
> Wireless network that's not secure and doesn't require any
> authentication...just
You name it, we have it.
Last count, we have 51 Apple TV's, but they aren't on the same network we're
having problems with. The TV's are either hard-wired or registered on a
Wireless network that's not secure and doesn't require any
authentication...just registration.
I'm not a MAC guys at all,
Hi Shayne,
On 28/02/17 11:10, Shayne Ghere wrote:
> I’m reaching out since we just started having problems with users
> complaining about getting messages on their Mac’s about a duplicate IP
> address on the network.
>
> When looking in the ARP table of the Cisco Nexus switches, the mac
>
I’m reaching out since we just started having problems with users
complaining about getting messages on their Mac’s about a duplicate IP
address on the network.
When looking in the ARP table of the Cisco Nexus switches, the mac address
of their computer isn’t in there, however the IP address
Wireless is pretty much treated like most other services. We don't have any
specific teams or structure for wireless support.
Users (staff/students/visitors) can all get help by ringing our service desk
(who will go through some steps and if no go send the job to our onsite team or
refer them
I'm curious if people can share their delineation of duties between
the support organization (help desk) and the network administration
(engineering, etc) teams, especially as it surrounds the triaging and
troubleshooting of wireless connectivity issues.
What is expected from the support
Hi Brian,
What we have generally done is migrated out classes of access points over a
period of time. We budget to replace approximately 1/3 of our APs every couple
years and our controllers during an 'off-year' every 6-ish. We try and keep the
latest tech in our classrooms which does mean a
Mmm, that module you refer to is only carrier agnostic on paper. It means that
Cisco configures the frequencies for the carrier that wants to use it. I tried
to use the module for unlicensed spectrum in the 1800 Mhz band but Cisco did
not support that ;-(
FYI: many regulators in EU allow to use
