A majority of the time a system reboot will address a lot of technical issues.
In this instance, the user will want to make sure he/she has tried to use a domain login and not an inadvertently created local system login. IE – jsmith as opposed to cnpjsmith where the cnp declares the jsmith user a CNP domain user. Then if drive mappings are provisioned properly on the backend, they will get loaded as the system completes the login.
If issue stems from an Exchange based account on a smartphone, the Exchange application on a phone behaves like an Outlook session that is never closed. The application has already authenticated once when it was provisioned. From that point forward, the cached password will continue to work until the phone is rebooted or until the account has been removed and added back.
In most cases, the end user has not been declared a member of a system’s local administrators group. Without this group membership inclusion, an end user will not be able to change many aspects about his/her system. Being left out of this group membership could be by network administrator design but most of the time it is inadvertent. We generally do this for most of our end users unless a business has compliance issues to take into account.
Make sure to check every cable and connector that is involved with or around your station/area. Don’t just eye-ball the cords; make sure they are all firmly connected to the equipment. Many times this will solve your connectivity problem.