Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.
I'm trying to deploy Direct Access with Server 2012 to replace my finicky 2008R2/TMG direct access install. I've got a new 2012 VM spun up. It's sitting on the edge and I'm logged in as the domain admin. The role is installed, but the getting started wizard/remote access management console...
This is a network file server - are Z:\ and Y:\ the local paths on the server? Or the drive letters used by clients when mapping to these shares? If the former, I don't understand why they're relevant - just recreate the share Scans in the shared folder and you'll have the same relative...
No, a $ hides it from everyone. Just give users links to their shared folders and set the shared folder permissions so only the assigned user has access. This way, even if Tom guesses Mary's folder name, he won't see get into it.
No, there's no feasible way to crack WPA2-PSK, certainly not for a 9 year old.
If you have physical access to the router, it's trivial to reset it / log in and turn off wireless security.
Why don't you ask your uncle (or nephew if you aren't exactly on speaking terms with your uncle) exactly...
Not sure, but don't get confused with the /console part. If you're using a client 6.1 or higher, /console is ignored - it's the same as mstsc by itself.
http://blogs.msdn.com/b/rds/archive/2007/12/17/changes-to-remote-administration-in-windows-server-2008.aspx
It's definitely great. As has been said, IT is mostly hands on experience with systems and real world issues. A CS/CSE background is solid for IT - understanding the theory and fundamentals is of great, albeit indirect, utility. Plus, with a CS degree and practical IT knowledge you can do...
Same thing at my new place. I just punched em down to a double gang keystone plate and used short patch cables to the switch. Oddly enough, in my 10 years as a sysadmin, I've never had to punch down cable. It's dead simple with solid core wiring (which your builder should have used).
The Honewell 6280 z-wave controller seems pretty cool. http://www.youtube.com/watch?v=S0Ljk1brlek
That's what I'm planning to get, then expand out with keyless/NFC door locks, cameras, water sensors, etc.
DHCP clients never 'see' the server.
Use netmon to pin down where the problem is. The client is making the discovery; you need to see what offers are made in response, whether the client makes a request and whether the server acknowledges...
lol @ Ye Olde being call an antagonist. Really lol'd at 'come at me bro'.
Seriously though, if you're spending more time updating/repairing/securing your PC than you do using it, you're doing something wrong.
No, they won't see the username or the URL. That's all part of the HTTP header, which is encrypted. If the whole session is over SSL it shouldn't leak visits to other pages/etc, but depending on the implementation on the site's end, they might only secure authentication/cookie exchange, not...