Laptop For A Mobile User
-
I've tried picking the brain of other IT pros with no luck.
I've got a single user who uses a laptop as his main machine (Dell with a Dell docking station) and he has encountered some strange issues the past 24 hours. If he locks his machine and then comes back to it, the it will not take his password to the domain. If you SWITCH USER and then log in locally, it is fine. Going back to the logged in account OR another domain account, it says it doesn't know the password.
If we unplug the docking station from the USB port and then back in, wait a few seconds and try the password, it works.
He does NOT want to turn off hibernation as he likes to sleep/hibernate and then resume his open programs.
Also, if you simply lock and unlock we get "Trust Relationshitp between Workstation and Primary Domain failed." He has to unplug the USB docking station port and then log back in.
Any clue as to what has suddenly caused this? He is on Windows 7 Professional.
Second question, management may be OK with getting him a better solution. I see Lenovo offers "true" docking stations, if this perhaps the root of the problem. Any suggestions there?
-
Could it be the VPN dying on sleep / hibernate?
-
@scottalanmiller said:
Could it be the VPN dying on sleep / hibernate?
That is a good option I would think. I've never like the sleep / hibernate as some programs just don't recover well from it - I've seen a time or two were memory use doubled on wake up.
Another thing could be how he is connected to the network. Is he wired or wireless? If he is wired - is it via the port replicator or direct to the laptop. Dell still ships systems that will use the E-Dock, and while I"m not sure if that is compatible with his system, it's a option.
-
VPNs are notoriously bad on sleep. That's one thing we love about Pertino.
-
@scottalanmiller said:
Could it be the VPN dying on sleep / hibernate?
Well, really, he doesn't VPN much if at all. He does a lot of local work. And the great mystery is when, at work and on the "docking station", just locking the PC and unlocking causes the "Trust Relationship between Workstation and Primary Domain failed" message when trying to log back in. You can just lock it for 1 second and try again and you get this error. Only unplugging the docking station and plugging it back in helps and in his case, it causes his external monitors to lose what they were displaying and just shows on his laptop screen.
Oh, and didn't mention that...he uses his laptop screen as a third monitor.
-
@g.jacobse said:
@scottalanmiller said:
Could it be the VPN dying on sleep / hibernate?
That is a good option I would think. I've never like the sleep / hibernate as some programs just don't recover well from it - I've seen a time or two were memory use doubled on wake up.
Another thing could be how he is connected to the network. Is he wired or wireless? If he is wired - is it via the port replicator or direct to the laptop. Dell still ships systems that will use the E-Dock, and while I"m not sure if that is compatible with his system, it's a option.
He is wired via the port replicator, so in a sense, it is not a true, direct wired connection.
-
I actually had some time to spend in his PC since his group had an audit this week. He takes his PC home so never had time to play with it.
Fingers crossed, I may have resolved some (maybe all) of the issues. His work/domain network was set to public. Switched it back to WORK, removed and re-added it to the domain and it now shows domain network and no longer do we get the "Trust Relationship between Workstation and Primary Domain failed" error when unlocking or when rebooting.
-
I'm a bit late, but the trust error message made me think the machine account had gone out of sync - you've already fixed that by removing and readding it to the domain.
Good luck.
-
Ah that makes sense. One network connection set as public and another set as domain.
-
It's odd that the two different connections would cause a problem - unless networking changed that much in Windows 8 vs Windows 7. Windows 7 sorta disabled the wireless connection when it detected you were on a wired connection. The docking station should be considered a wired connection.
-
It's the types. It will change security profiles based on public vs domain.
