What you find, and it's even documented, is that the first times that you try to connect to the wireless network, you encounter security certificate errors.
From the QCC brochure (PDF file) that describes how to connect to their network:
Depending on your browser and operating system, the message or dialog box might look different, but it's something such as this:
or this
The trick is that you are supposed to ignore the security error and click through until you get to a login screen. I got through and on the air. There was joy in RB's heart.
As I sat in the computing center, another student came to the help desk with a question regarding connecting to the network while running Linux on his laptop.
"Is your Java all updated?" asked the help desk person, a question that was interesting but not really relevant.
The student explained that he had the right configuration but kept running into these errors.
"You may have to go down to talk with the guys downstairs? What room is that?"
"320," said another employee.
"You can actually just go in the door. The door is closed, but you can go in."
I said that I might be able to help. I walked around the table and looked at the student's screen, saw the error, and said that he needed just to bull his way through the errors until he got to the login screen. Several clicks later, he was able to log in and was on the air.
So, they're clever enough to block
ssh
, but can't configure the network not to require users to ignore security messages. Grumble, grumble.Oh, by the way, the Harrington Computing Center is not in the Harrington Center, but on the third floor of the Administration building.
1 comment:
I constantly face helpless desks tell users that they should disable anti Virus, anti Spyware, and firewalls.... Brings to mind a quote, "Social Engineering, because there is no patch for human stupidity" Don't know where it came from, but I do think it's right.
Post a Comment