By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,121 Members | 1,723 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,121 IT Pros & Developers. It's quick & easy.

Service

P: n/a

I have created a service that create a process.
The service is running in local system account & it also create the
new process in system account.

In process i have to access network resource .
In Windows 2000 new process is working fine but in Windows XP it does't
do anything .
The problem is that newly created problem could not access network path
thats y creating problem .
What may b the reason ?
Any Help ?

FAISAL NAWAZ

Jul 21 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
<ma***********@gmail.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...
In process i have to access network resource .
In Windows 2000 new process is working fine but in Windows XP it does't
do anything .
The problem is that newly created problem could not access network path
thats y creating problem .
What may b the reason ?


Make sure you have your service dependencies set as needed. You may need
Remote Procedure Call (RPC) for networking. You can set these dependencies
in VS.NET by setting the ServicesDependedOn property of the ServiceInstaller
component in your project. Use "RPCSS" for RPC. If you change this
setting, you will have to uninstall and reinstall the service for the
setting to take affect. You may have other dependencies as well, such as
message queueing, etc. It is important to set the service dependencies
correctly, because otherwise the ordering of the various service startups at
boot time may be wrong for your service.

Secondly, you may need to set the logon user for the service to a domain
user that has rights to the network resources that you are trying to access,
rather than your system account. If necessary, you may have to assign the
"Log on as a service" right to the login in the Local Security Policy's
SecuritySettings/LocalPolicies/UserRightsAssignment option.

-- Alan

Jul 21 '05 #2

P: n/a

Thanks 4 feedback.

There is nothing wrong with the service as it works on Windows 2000.

Actually whole things r working fine in windows 2k SP 4.but
on Windows XP SP 2 the process is unable to access the network path.
People say that if ur process is running in local system account then u
can't
access network resources.

Its OK on Xp i.e when we try to access network it could't but why it is
working in windows 2000 when the process is running in system account.

Why there is difference in service activity on WindowsXP & Windows 2K.

Hope u will guide me...
Thanks in advance





Alan Pretre wrote:
<ma***********@gmail.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...
In process i have to access network resource .
In Windows 2000 new process is working fine but in Windows XP it does't do anything .
The problem is that newly created problem could not access network path thats y creating problem .
What may b the reason ?
Make sure you have your service dependencies set as needed. You may

need Remote Procedure Call (RPC) for networking. You can set these dependencies in VS.NET by setting the ServicesDependedOn property of the ServiceInstaller component in your project. Use "RPCSS" for RPC. If you change this
setting, you will have to uninstall and reinstall the service for the setting to take affect. You may have other dependencies as well, such as message queueing, etc. It is important to set the service dependencies correctly, because otherwise the ordering of the various service startups at boot time may be wrong for your service.

Secondly, you may need to set the logon user for the service to a domain user that has rights to the network resources that you are trying to access, rather than your system account. If necessary, you may have to assign the "Log on as a service" right to the login in the Local Security Policy's SecuritySettings/LocalPolicies/UserRightsAssignment option.

-- Alan


Jul 21 '05 #3

P: n/a
Windows 2000 and Windows XP have very different security models. To add to
the flavor, Windows XP SP2 has a different security model than Windows XP
SP1. Just because your app works on W2K does not at all mean it will work
with the security model of XP especially when we are talking about network
access.

As Alan stated below, for your service to work correctly across the network
you should probably have the service start under a Domain user account that
has the privileges you require of your service. Microsoft has reduced the
authority of LocalSystem, LocalService, and NetworkService accounts to
increase network security.

Hope that helps,
PJ

<ma***********@gmail.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...

Thanks 4 feedback.

There is nothing wrong with the service as it works on Windows 2000.

Actually whole things r working fine in windows 2k SP 4.but
on Windows XP SP 2 the process is unable to access the network path.
People say that if ur process is running in local system account then u
can't
access network resources.

Its OK on Xp i.e when we try to access network it could't but why it is
working in windows 2000 when the process is running in system account.

Why there is difference in service activity on WindowsXP & Windows 2K.

Hope u will guide me...
Thanks in advance





Alan Pretre wrote:
<ma***********@gmail.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...
> In process i have to access network resource .
> In Windows 2000 new process is working fine but in Windows XP it does't > do anything .
> The problem is that newly created problem could not access network path > thats y creating problem .
> What may b the reason ?


Make sure you have your service dependencies set as needed. You may

need
Remote Procedure Call (RPC) for networking. You can set these

dependencies
in VS.NET by setting the ServicesDependedOn property of the

ServiceInstaller
component in your project. Use "RPCSS" for RPC. If you change this
setting, you will have to uninstall and reinstall the service for the

setting to take affect. You may have other dependencies as well,

such as
message queueing, etc. It is important to set the service

dependencies
correctly, because otherwise the ordering of the various service

startups at
boot time may be wrong for your service.

Secondly, you may need to set the logon user for the service to a

domain
user that has rights to the network resources that you are trying to

access,
rather than your system account. If necessary, you may have to

assign the
"Log on as a service" right to the login in the Local Security

Policy's
SecuritySettings/LocalPolicies/UserRightsAssignment option.

-- Alan

Jul 21 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.