So, issue that has just recently cropped up, and we have made no changes that would cause this.
We now have several users who, although able to initially log in off the WAN, cannot unlock the screen off the WAN. They receive a "No logon servers available" error.
This has never been an issue with XP. One user reports the issue didn't start until some time towards the end of last week. One of desktop support folks just received a report from a user today.
Now, I've tried duplicating the issue with my machines but simply cannot.
We have 2 other users with desktops who can duplicate the issue, though.
What would cause this?
The issue is not that they cannot log on; they can log on fine, initially. It's only the screen lock that appears borked. Therefore I wouldn't think the "Always wait for network at logon" GPO would be relevant, since the issue isn't at initial logon.
Ideas? I've tried searching the Goog, but haven't had much success in finding info on this particular issue.
Edit: This is in a domain environment. No GPO modifications have been made since June, and this issue just recently started cropping up.
We now have several users who, although able to initially log in off the WAN, cannot unlock the screen off the WAN. They receive a "No logon servers available" error.
This has never been an issue with XP. One user reports the issue didn't start until some time towards the end of last week. One of desktop support folks just received a report from a user today.
Now, I've tried duplicating the issue with my machines but simply cannot.
We have 2 other users with desktops who can duplicate the issue, though.
What would cause this?
The issue is not that they cannot log on; they can log on fine, initially. It's only the screen lock that appears borked. Therefore I wouldn't think the "Always wait for network at logon" GPO would be relevant, since the issue isn't at initial logon.
Ideas? I've tried searching the Goog, but haven't had much success in finding info on this particular issue.
Edit: This is in a domain environment. No GPO modifications have been made since June, and this issue just recently started cropping up.
Last edited: