EricP
November 17th 06, 03:28 PM
Hello,
I've recently switched a server in my company's domain from Windows
2000 (professional) to Windows XP (professional). There was only
reported issue, which seems to be related to either network or Win XP
security.
This workstation / server has a number of scheduled tasks, at various
regular intervals on workdays. This is handled by a 3rd party software
(named Trading Partner), bundled with its own scheduler. Tasks include
batch and executable command files, as well as software tasks. The
problem occurs when the station is locked.
Jobs are scheduled every hour (4pm, 5pm, 6pm, etc.). They run even if
the station is locked, and we never experienced any issue under Windows
2000. They still run in XP once we lock the station, but most tasks
that involve ftp transfer, network transfers or anything else that
require connections (network and external) do not seem to complete
properly if it's locked. I'm seeing "connection failed" messages for
ftp transfers and network access tasks. A MS Office Communicator
session active at the time of locking is also eventually terminated.
If these same tasks are ran when someone is using the station, we don't
experience these issues. The exact same transfers work fine, using the
same data files. At first, I thought this might have to do with Win
XP's firewall, and so I had the settings changed to allow mostly
everything through. The tasks completed properly on the following
evening / night. However, yesterday's failed again, and no settings
were changed. The firewall options match those from 2 days back. It
doesn't seem to be at a fixed time either...the 1st time we saw tasks
starting to fail from 5pm onward, whereas yesterday's failed only after
8pm.
What I'm wondering is: does Win XP include any kind of built-in
security settings for when users lock a domain workstation, that
weren't featured in Win 2000 ? I doubt this issue would be related to
firewall settings, it looks more of a network or session timeout
problem. Our domain uses Active Directory.
Any help would be greatly appreciated. If at all possible, we want to
avoid having to switch to Window's scheduler as many tasks inherently
depend on the TP software's features.
Thank you,
Eric P
I've recently switched a server in my company's domain from Windows
2000 (professional) to Windows XP (professional). There was only
reported issue, which seems to be related to either network or Win XP
security.
This workstation / server has a number of scheduled tasks, at various
regular intervals on workdays. This is handled by a 3rd party software
(named Trading Partner), bundled with its own scheduler. Tasks include
batch and executable command files, as well as software tasks. The
problem occurs when the station is locked.
Jobs are scheduled every hour (4pm, 5pm, 6pm, etc.). They run even if
the station is locked, and we never experienced any issue under Windows
2000. They still run in XP once we lock the station, but most tasks
that involve ftp transfer, network transfers or anything else that
require connections (network and external) do not seem to complete
properly if it's locked. I'm seeing "connection failed" messages for
ftp transfers and network access tasks. A MS Office Communicator
session active at the time of locking is also eventually terminated.
If these same tasks are ran when someone is using the station, we don't
experience these issues. The exact same transfers work fine, using the
same data files. At first, I thought this might have to do with Win
XP's firewall, and so I had the settings changed to allow mostly
everything through. The tasks completed properly on the following
evening / night. However, yesterday's failed again, and no settings
were changed. The firewall options match those from 2 days back. It
doesn't seem to be at a fixed time either...the 1st time we saw tasks
starting to fail from 5pm onward, whereas yesterday's failed only after
8pm.
What I'm wondering is: does Win XP include any kind of built-in
security settings for when users lock a domain workstation, that
weren't featured in Win 2000 ? I doubt this issue would be related to
firewall settings, it looks more of a network or session timeout
problem. Our domain uses Active Directory.
Any help would be greatly appreciated. If at all possible, we want to
avoid having to switch to Window's scheduler as many tasks inherently
depend on the TP software's features.
Thank you,
Eric P