Good link jefro although I don't see any restrictions placed by Net User Command or through the Active Directory directory service Users and Computers snap-in. The puzzle continues

0

Have you checked, whether the screensaver is active on the client PCs? In the screensaver you can configure to ask for password after reactivation. Paul

0

Iturned all screensavers and power saving options off on all clients and server while I trace this issue. The clients are all logged off at 10:26pm (both Ethernet & wirelessly connected clients) but it's not done for the normal 2003 scheduler. The client also retain access to the internet so it's not done by the router either. It's almost certainly a configuration setting on the server--maybe it's some 3rd party app that was installed. Just haven't found it yet. I'll check the running PID's on the server and see what's running that I don't recognize.

0

You'll pardon me for pointing out the obvious but........not logging out should be a firing offense for any employee in any company anywhere. One shouldn't ever leave themselves logged in on any unsupervised workstation. If you're getting up to go to the bathroom, lock it. If you're going to the coffee machine to grab a cup, lock it. At the end of the day before you leave work to go home....lock it or log off. It's VERY unsecure to leave yourself logged in. How do you know someone on the cleaning crew isn't a hacker just itching to get on an unsecured workstation and mess up your network so bad you can't do business for a few days....or weeks? Point in fact, you don't. And the problem with not logging off is, you can't even find out who's responsible because logfiles will point at the idiot who didn't log off/lock their workstation.

0

Good advice curt for a large enterprise. We aren't that kind of environment. We have 4 workstations in 4 private offices We the cleaning crew! No-one has access to our space after hours. No-one but we have access to these workstations during business hours. I need to be able to remotely access licensed apps via my workstation when I'm at home. Can't do it if the workstation has been logged off and even though I can remotely connect to and control the server--can't run all the server based applications I need directly from the server: they aren't' licence to operate that way and doing so would defeat the database locking mechanism anyway.

0

Good advice curt for a large enterprise. We aren't that kind of environment. We have 4 workstations in 4 private offices Size doesn't matter where security is concerned. I lock all my PC's (or in the case of the UNIX/Linux boxes, log off) at home as well as at work. I sincerely hope, for your sake, the day never comes when you find yourself saying, "Darn, that guy was right, it makes no sense not to take such a simple, easy security measure." I need to be able to remotely access licensed apps via my workstation when I'm at home. Can't do it if the workstation has been logged off You can if you lock the worstation(s) (ie: hit the Windows key and "L" or ctrl-alt-del and click on 'Lock'). I know, I do it all the time with my home PC and connect to it from work.

0

"You can if you lock the worstation(s) (ie: hit the Windows key and "L" or ctrl-alt-del and click on 'Lock'). I know, I do it all the time with my home PC and connect to it from work." What app are you using to access remotely that allows you to log a locked workstation back on ?

0

I'm just using RDC (Remote Desktop Connection) from within Windows. It's located in: Start >> Programs >> Accessories >> Communication >> RDC You're not logging the workstation itself back on. If you have your system set to allow RDC connections, it's a separate connection from the console. The desktop itself remains locked while connected remotely like that. Sort of like an ssh connection on a UNIX/Linux box. In fact, with a UNIX box, you could have multiple users logged on remotely via ssh and then login from the console without an hassles. But then, UNIX/Linux has always been more flexible than Windows.........

0

Yeah actually curt I built my first PC in 1977 and can remember when UNIX was kind of a new kid on the block. I use putty for UNIX connections. I haven't set RCD up on this server. Like I said, I didn't build the damn thing I'm just trying to figure out what they guys who did build and configure it did. Still trying to trace what's logging off workstations every night. But definately appreciate all the help here. The last MS server I set up was NT---so 2003 has a new learning curve for me. I transitioned from 2000 to XP under protest O(and still make XP look like 2000 to the greatest extent possible) but 2003 is another whole kettle of fish (neither NT nor 2000)

0

and still make XP look like 2000 to the greatest extent possible I hear that!!! The first 10 or 15 minutes I spend on any new XP install (for myself of course) I spend changing to the windows 2000 style interface. I've always found the XP interface too "cartoony" for my taste.....LOL My career is taking me away from domain admin and computer/server/printer repair as the last few years have been spent as a network technician so my Windows skills are rusting. It seems to me though, that in the users property sheet there is a setting (somewhere) for time's of day that they're allowed to logon to the network. If that's set to say, 8 am to 5 pm, then it would log the user off at 5 pm automatically.

0