I have a weird issue I have never seen before and am trying to get some answers. I setup a laptop for one of our employees who works out in the field. We typically login to the machine while on the network with a domain account. This is so the password gets cached and they can login to the machine once they receive it.
I sent a laptop to this one guy (who is rather tech savvy-so I know it is not user error) and he could not login to the laptop using his network credentials. I was able to get him on his home network using his router, and I RDP’ed into the machine. When I was remotely connected, I was able to login to the PC with no problem. However, after I disconnected, he tried to login also and it kept telling him that the domain was not available? It wasn’t even an “invalid password or login” error.
I ended up creating another local account on the machine so he could work, but I am stumped as to why he could not login locally, but I could using RDP. Any ideas?
I understood the question.
I don’t believe you were using the cached domain account info. Your rdp session was to a local account not a domain account. The user was trying to use a domain account not a local to the workstation account. This is why when you made a local account it worked.
I don’t think you understood my question. He was at home using the laptop I just sent him. He was trying to login to the laptop using the cached domain account. He was not able to login.
When I RDP’ed into the same laptop, I was able to login to that PC using the same cached domain account. I don’t understand the difference. The machine is not on the company network – he was at home using his personal network so I could get connected.
usually you have to do port fowarding to rdp thru a router. interesting you never mentioned doing that.
To address your question, he was trying to logon to a domain. you were logging on locally. One uses the domain account, the other the local account.