Access denied adding network printers fronm trusted domain.

Hi,

We have two trsuted domain. Domain A and domain B trust fully each other.
We've just installed a server A belonging to domain A. Workstations belong to
domain B and I've created a Computer startup script to add network printers
from server A from the other domain.

When workstation are applying their configuration all of them get an access
denied error 800A0046. The line is in this way:

Set WshNetwork = CreateObject("WScript.Network")
WshNetwork.AddWindowsPrinterConnection "\\serverA\PrinterQueue"

It's likely there are a permission problem, but it's just some users trying
to install a netowrk printer from a truted domain.

I've already granted rights to Domain Users and Computer Machines from the
other domain, no way.

Thanks in advance.

What is the operating system of your clients and servers? What type of trust
relationship is established between both domains (external or forest)?
In any case, I believe that this approach will, at best, create a printer
mapping in the .Default profile on your client computers (with not much of a
benefit to your users).
You might want to consider alternatives - such as, for example, mapping
printers based on the client computer OU
(http://www.microsoft.com/technet/scr...7/hey0727.mspx),
its IP address
(http://www.microsoft.com/technet/scr...6/hey0719.mspx),
taking advantage of Windows Server 2003 R2 printer management features
(assuming you have those available), or similar functionality available via
GP Preferences...

hth
Marcin

"fedaynjorge" <> wrote in message
news:38E78A02-0147-471D-B10D-...
> Hi,
>
> We have two trsuted domain. Domain A and domain B trust fully each other.
> We've just installed a server A belonging to domain A. Workstations belong
> to
> domain B and I've created a Computer startup script to add network
> printers
> from server A from the other domain.
>
> When workstation are applying their configuration all of them get an
> access
> denied error 800A0046. The line is in this way:
>
> Set WshNetwork = CreateObject("WScript.Network")
> WshNetwork.AddWindowsPrinterConnection "\\serverA\PrinterQueue"
>
> It's likely there are a permission problem, but it's just some users
> trying
> to install a netowrk printer from a truted domain.
>
> I've already granted rights to Domain Users and Computer Machines from the
> other domain, no way.
>
> Thanks in advance.

Hi
Can you do it manually?

--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

Of course,

Once the user has loged to the network there's no problem.

What's more, I tried with user logon scripts and everything goes well.

The problem is that by using computer startup scripts, the script runs with
SYSTEM account credentials and this one netowork doesn't recognize this
account, so it's impossible to do anything.

Thanks to Marcin, I'll try filtering with ip addresses.

Thanks both.


"Jorge Silva" wrote:

> Hi
> Can you do it manually?
>
> --
> I hope that the information above helps you.
> Have a Nice day.
>
> Jorge Silva
> MCSE, MVP Directory Services
>
> Please no e-mails, any questions should be posted in the NewsGroup
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Great.

--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi fedaynjorg
Did you solved your problem descripted above?
I have same problem, external trusting domain and SYSTEM account.


> On Tuesday, September 30, 2008 4:42 AM fedaynjorg wrote:

> Hi,
>
> We have two trsuted domain. Domain A and domain B trust fully each other.
> We've just installed a server A belonging to domain A. Workstations belong to
> domain B and I've created a Computer startup script to add network printers
> from server A from the other domain.
>
> When workstation are applying their configuration all of them get an access
> denied error 800A0046. The line is in this way:
>
> Set WshNetwork = CreateObject("WScript.Network")
> WshNetwork.AddWindowsPrinterConnection "\\serverA\PrinterQueue"
>
> It's likely there are a permission problem, but it's just some users trying
> to install a netowrk printer from a truted domain.
>
> I've already granted rights to Domain Users and Computer Machines from the
> other domain, no way.
>
> Thanks in advance.


>> On Tuesday, September 30, 2008 9:30 AM Marcin wrote:

>> What is the operating system of your clients and servers? What type of trust
>> relationship is established between both domains (external or forest)?
>> In any case, I believe that this approach will, at best, create a printer
>> mapping in the .Default profile on your client computers (with not much of a
>> benefit to your users).
>> You might want to consider alternatives - such as, for example, mapping
>> printers based on the client computer OU
>> (http://www.microsoft.com/technet/scr...7/hey0727.mspx),
>> its IP address
>> (http://www.microsoft.com/technet/scr...6/hey0719.mspx),
>> taking advantage of Windows Server 2003 R2 printer management features
>> (assuming you have those available), or similar functionality available via
>> GP Preferences...
>>
>> hth
>> Marcin
>>
>> "fedaynjorge" <> wrote in message
>> news:38E78A02-0147-471D-B10D-...


>>> On Tuesday, September 30, 2008 1:20 PM Jorge Silva wrote:

>>> Hi
>>> Can you do it manually?
>>>
>>> --
>>> I hope that the information above helps you.
>>> Have a Nice day.
>>>
>>> Jorge Silva
>>> MCSE, MVP Directory Services
>>>
>>> Please no e-mails, any questions should be posted in the NewsGroup
>>> This posting is provided "AS IS" with no warranties, and confers no rights.


>>>> On Wednesday, October 01, 2008 6:51 AM fedaynjorg wrote:

>>>> Of course,
>>>>
>>>> Once the user has loged to the network there's no problem.
>>>>
>>>> What's more, I tried with user logon scripts and everything goes well.
>>>>
>>>> The problem is that by using computer startup scripts, the script runs with
>>>> SYSTEM account credentials and this one netowork doesn't recognize this
>>>> account, so it's impossible to do anything.
>>>>
>>>> Thanks to Marcin, I'll try filtering with ip addresses.
>>>>
>>>> Thanks both.
>>>>
>>>>
>>>> "Jorge Silva" wrote:


>>>>> On Wednesday, October 01, 2008 7:07 AM Jorge Silva wrote:

>>>>> Great.
>>>>>
>>>>> --
>>>>> I hope that the information above helps you.
>>>>> Have a Nice day.
>>>>>
>>>>> Jorge Silva
>>>>> MCSE, MVP Directory Services
>>>>>
>>>>> Please no e-mails, any questions should be posted in the NewsGroup
>>>>> This posting is provided "AS IS" with no warranties, and confers no rights.