Why there can be problems with wrong Usernames and Passwords?

If you are working inside the Microsoft Domain, there are no problems. Every time you try to access a shared resource, the priviledges associated to your User Account are compared, and you are granted/denied access regarding to the result.

But if you are not in the domain, then Windows behaves apparently gloomy.
  1. If you are using a username that doesn't exist in the domain, you are granted the GUEST priviledge. Generally, this is good. Apart from when someone wants to access private shares, not open to GUESTs!
  2. The main problem arise when you are using an account that DO exist in the domain (generally, the Administrator account on any Windows machine).
    • If you try to access a shared resource (a printer, or a shared folder on a disk) and the password of the account on your machine IS EQUAL to the one of the User Account in the domain, then there are no problems: you are granted the access (as you can see, this can happen either for a user that knows what he's doing, or by a lot, but very a lot, of (un)luck).
    • If the username is the same, but not the password, then two things can happen.
      • When accessing a file share: Windows asks you for the correct password. OK, not pretty, but it works.
      • When accessing a shared printer: Windows disconnects that printer, so you cannot use it! This is very bad, isn't it?
That's why you MUST always use the correct UserName (usually, your last name followed by the initial of your first name), and NOT a funny one (like the always present pippo) or Administrator.


Q. What about if I want to access a shared resource as guest but Windows asks me for a password?

A. When Windows asks for it, give the word GUEST as username, and no password. This will work.

Last Updated on Thursday, 14 June 2012 14:34