Cannot connect to server from remote - followed #1050, still doesnt work... :(

[kosmonooit]

Greetings,

I am really keen to get Print Watch working so I can use it in our Internet Cafe. I have set up a 'new' Windows 2003 Server, so it hasnt got much else on, and its got the latest updates etc and seem stable. I am using Active Directory. The PC I am trying from is XP Pro SP2.

On the server, Pritn Watch works great. But no matter what I do, I can not get the  remote Print Watch control program to connect "Acces Denied"

I have followed the instructions in the ID #1050. I made a group of for the print admins, and added this with full rights in "Edit Limits" and Edit Default" in the Servers COM Security, as well as all the sections in PW4Srv Security, tabs, restarted the service, the same. Even logged in as Administrator, same. Nothing I do or tweak seems to make any difference.

Please help me out here, this app is all I need to do the task of controlling and recording printing, thanks so much in advance.

[Oleg Kovalenko]

You can try to enable failure logon audit on the remote server.
Run O&K Print Watch Control Program and connect to this server.
Check EventLog for failure logons event and find account name which is used to connect.

[kosmonooit]

thanks for the reply, I tried that. I enabled all the options for the logins (success &  failure)  in the Audit Policy / Local Policy/  Security Settings / Default Domain Controller Settings

I can see all the other login events, and I used Administrator to help sort this out. When I try connect from the workstation, an Successful Login event is listed from the w/s IP, source ports 1154, 1155, 1156 but still "Access Denied" from the PC.

Anything else I can try do to nail down the problem? still really keen to get this sorted please.

[kosmonooit]

I try again a  user that has all the rights - and no events are logged when I try connect with the control program....

[Oleg Kovalenko]

Try to add all rights to PW4SRv.exe DCOM Server on the client PC the same like you have done it on the server.

[kosmonooit]

thanks - got it working eventually, think it was the firewall on the XP

But still not certain on the following, can you please clarify exactly what should be set:

> Edit Access Permissions + Launch and Activation Permissions. You should change the both settings "Edit Limits..." and "Edit Default...".

and

> Edit "Launch and Activation Permissions", "Access Permissions", "Configuration Permissions".

Thanks.