Understanding Print Notifications in Windows Vista

re: Understanding Print Notifications in Windows Vista

molotov.molotov — Tue, 20 Jan 2009 21:38:58 GMT

Thanks for clarifying, CC - it appears somewhere along the way I missed an edit - "What this is telling us is that the Vista client cannot access the communications pipe for the spooler for some file activity" changed to "What this is telling us is that the print server cannot access the communications pipe for the spooler on the client for some file activity", which makes more sense in the given scenario.

re: Understanding Print Notifications in Windows Vista

CC Hameed — Tue, 20 Jan 2009 18:39:55 GMT

Molotov -

The Procmon which was taken on the print server shows that it can't perform an activity on the Windows Vista spooler (\\Vista\pipe\spoolss) - that is why the change has to be made on the client side - to allow the print server to send the notification back to the client's spooler.

- CC

re: Understanding Print Notifications in Windows Vista

Ondrej Sevecek — Tue, 20 Jan 2009 01:30:54 GMT

hello,

I would like to add myself to the procmon entry question.

Why should I change the null-session settings on the Vista client? Is the connection done locally?

re: Understanding Print Notifications in Windows Vista

molotov.molotov — Sat, 17 Jan 2009 01:41:01 GMT

Thanks, CC.

However, I'm still a bit confused about the interpretation of the Procmon log entry, as noted in my initial comment... Any clarification would be welcome.

re: Understanding Print Notifications in Windows Vista

CC Hameed — Fri, 16 Jan 2009 22:21:23 GMT

Molotov -

The edit error is my fault. I missed one spot when I edited the article. I've corrected the oversight.

Thanks for pointing it out!

- CC

re: Understanding Print Notifications in Windows Vista

molotov.molotov — Fri, 16 Jan 2009 21:30:09 GMT

Interesting post, Mick, but... I'm a bit confused - perhaps you can clarify?

>> What this is telling us is that the Vista client cannot access the communications pipe for the spooler for some file activity <<

If Process Monitor was running on the server, I would interpret the log entry to mean that the spooler running on the server was not able to open the communications pipe \\vista\pipe\spoolss, on the Vista client. This makes sense, since the registry modification to allow the access apparently took place on the Vista client.

There also appears to be some discrepancy WRT the system the NullSessionPipes registry change was made on - first, the statement is made that "On the print server, we needed to modify the following Multi-string registry value", then another statement is made indicating the modification was made on the Vista client - "Once we performed this step on the Windows Vista machine, print notifications worked fine."

CC Hameed's EDIT attempts to clarify this ("The changes were made on the CLIENT (Vista) and not the Print Server."), but I think it would be desirable to edit the article to reflect the actual scenario...