He's a guy who likes to help out apologize drink beer, named Luke, from Canada.
His comments are supposed to be constructive, or thankful, as seen above. His comments do not infect protected computers that have adequate antivirus and antimalware programs. He recommends Common Sense 2.0 (Windows)...
Someone downvoted my answer :( I'll never get that Gold badge now
Aaaaand, it's done
@Zoredache Thanks for VTCing that question, and fulfilling your duties!
@allquixotic hey allquixotic, you always help me, so how about this one: I'm trying to install Windows 7 on a blank HDD and it doesn't work. HALP canadian-luke
Yeah, that would be great; you can clean up all my terrible n00bish inaccuracies and such, and de-Canadianify the mannerisms and sayings so the audience isn't taken aback
@allquixotic I know, but I live pretty close to a military airstrip. Not a good idea to mess around with signaling mirrors here :-) Last year a farmer, about half a mile from here, got into trouble because he used strips of aluminum foil to enhance a scare-crow. The fine was bigger than the bird-damage to his crops. — Tonny1 min ago
Our SBS 2011 recently had some hardware trouble, so we decided to migrate everything to a new server which we also installed with SBS 2011.
Since the migration, I've been having trouble to get our VPN to work. The connection fails with the following error dialog:
So I checked out the Security...
Hmm. I haven't experienced that particular problem before, sorry. Although, @allquixotic could probably answer it off the top of his head. He's so smart.
http://www.talk-about-it.ca/?p=99&utm_source=rss&utm_medium=rss&utm_campaign=canadian-luke-a-quick-faq Talk about IT! Canadian Luke – A quick FAQ LukeB 1399667146
I never really messed with these policies. Couldn't I just create a new policy above all, granting access to anyone in the basic Users group? Just to see if that works
If so, the proxy is probably refusing your HTTP requests because it doesn't like Windows Update's user agent (it could be doing user agent whitelisting, which is stupid, but a lot of proxies do it)
Oh, also, are you using a WSUS server? Looks like you're running Server 2008
You could of course run Wireshark and see what the actual requests/responses are (and where they're being directed to) to debug it further
perhaps an interesting topic, is to what extent as an IT enthusiast and Admin, you seek to generalise, and to specialise.. The pace of change is very great. And there are many OSs and areas.
@CanadianLuke as an admin, do you ever get tired of change and having to keep up with developments, or does it continue to inspire you? (is that a terrible question re your site?)
@AlPacino Just run it and look at the requests and responses when you check for updates, and see which server it's hitting and look for anything unusual... see if you can isolate the "403 Forbidden" responses from the windows update server and make sure it's either a real Windows Update server, or your local WSUS server.
You never said whether you're running under a proxy, either..
Did you add what you think is the server for updates to the trusted list in "IE"? (that was one of the solutions mentioned on googling you error message).
I notice you didn't bother to say in your question which solutions you tried. Just that you tried them all, which is unlikely to say the least.
Those were mentioned on this page when I googled about adding windows update to trusted sites support.microsoft.com/KB/836961
adding windows updates to trusted sites was one of many solutions mentioned for your problem. You said you tried all of them. But you haven't. So yeah you should say what you tried.
if you do wireshark youll get a ton - a ton- of packets.. there may be a display filter that shows just 403 or whatever the error is. Otherwise you should just look at packets that come up at the time of the error
Our SBS 2011 recently had some hardware trouble, so we decided to migrate everything to a new server which we also installed with SBS 2011.
Since the migration, I've been having trouble to get our VPN to work. The connection fails with the following error dialog:
So I checked out the Security...
