XP machine on a domain. Have given remote access to two users, so they logoff of their sessions when complete. When they do, the machine is not pingable and will not respond to anything but a console logon. A physical restart never makes it available without a console logon first.
What have I missed in the setup for this? It is new behavior and used to not be an issue.
This is behaving exactly like the network isn't turned on unless the user is logged in. I've seen this happen with some Wireless configs, as the agent that handles Wifi login is a userspace systray app which doesn't run as a service. This kind of thing is starting to show up on wired configs in networks that do Network Access Control. Client-side AV may put the machine into firewall deny-all mode when a user isn't logged in, which is another area to look into.