networked printers: logon failure

[Guest]

Hi everybody,

we had our new delivery of computers yesterday. We have switched the new
ones with the old ones and they have been RISed with the same configuration
as before. We have a script which runs when our users connect to the network
which attaches them to the relevant printers.

We can connect to the network printers fine, however the locally shared
printers wont allow our users in the group "staff" to connect to them. This
was all working with the old computers. When we logon as the network
administrators we can connect to them from any computer.

The permissions have not been changed by anybody, the only thing that has
changed is the computer names (due to a change in room names.) the only
script that runs before it connects the network drives, which works fine.

the error we receive is

Logon failer: the user has not been granted the requested logon type.

can anybody help?

 

[Ron Lowe]

Hi everybody,

we had our new delivery of computers yesterday. We have switched the new
ones with the old ones and they have been RISed with the same
configuration
as before. We have a script which runs when our users connect to the
network
which attaches them to the relevant printers.

We can connect to the network printers fine, however the locally shared
printers wont allow our users in the group "staff" to connect to them.
This
was all working with the old computers. When we logon as the network
administrators we can connect to them from any computer.

The permissions have not been changed by anybody, the only thing that has
changed is the computer names (due to a change in room names.) the only
script that runs before it connects the network drives, which works fine.

the error we receive is

Logon failer: the user has not been granted the requested logon type.

can anybody help?

Assuming XP Pro, and that you are not using Simple File Sharing.
Is that correct?
Otherwise, post back.

Also, are you in a domain or workgroup?

On the machine(s) with the printers attached,
which you are trying to connect to, go to:

Start | Run | Secpol.msc

Go to Local Policies | User Rights Assignment

Double-click the policy "Access this computer from the network".
Ensure that the users you want are included in at least one of the groups
which have access.
For example, 'Users' or 'Everyone' might be listed.
That would cover them.

Then, double-click the policy 'Deny access to this computer from the
network'.
Ensure the connecting users are NOT included here.
I'd normally expect SUPPORT_###### and Guest in here.
( unless you are using Simple File Sharing, in which case, Guest must not be
listed here. )

 

[Chuck]

Hi everybody,

we had our new delivery of computers yesterday. We have switched the new
ones with the old ones and they have been RISed with the same configuration
as before. We have a script which runs when our users connect to the network
which attaches them to the relevant printers.

We can connect to the network printers fine, however the locally shared
printers wont allow our users in the group "staff" to connect to them. This
was all working with the old computers. When we logon as the network
administrators we can connect to them from any computer.

The permissions have not been changed by anybody, the only thing that has
changed is the computer names (due to a change in room names.) the only
script that runs before it connects the network drives, which works fine.

the error we receive is

Logon failer: the user has not been granted the requested logon type.

can anybody help?

Is the server (the computer that you want to connect to) running XP Home or Pro?
Read this article, and check Local Security Policy settings:
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Help>

 

[Guest]

Ron, Chuck,

i cant get to the room at the moment and the caretakers are locking up,
thanks for the replys though, ill give you an update tomorrow.

 

[Guest]

Thanks for the fast response, we did need to use Secpol.msc to configure the
network access on the local computer policy, the way our network is setup
though, all these policies are controlled by the Group Policies on the server
and in Active Directory. As there was already a group setup with the policy
to allow the right people to connect to the computer, all we had to do was
move the computer into this group in AD and it all worked fine.

 

[Chuck]

Thanks for the fast response, we did need to use Secpol.msc to configure the
network access on the local computer policy, the way our network is setup
though, all these policies are controlled by the Group Policies on the server
and in Active Directory. As there was already a group setup with the policy
to allow the right people to connect to the computer, all we had to do was
move the computer into this group in AD and it all worked fine.

Andy,

Thanks for the update.