Hi Jeffrey
In the attached trace.txt you can see the lines i presume gives the error
The log is created as follows.
start log
Start -> Run -> "\\130.225.51.90" (the samba server)
login to samba server in dialog window.
wait for window with printers to appear. (only 1 printer on this
particular test-server)
stop log.
The test is done twice. once with the AFS-Service running and one time
with AFS-Service stopped.
In the trace.txt:
No_error1_filtered is with the AFS-service stopped
error_filtered is the with the AFS-service running
You can find the complete Process Monitor logs at
//afs/ies.auc.dk/user/ped/AFS-Trace/
I did not do the wireshark logs as i presume i identified the error with
the Process Monitor tool. If you need the wireshark logs let me know and
i will do them
Best Regards
Peter Dissing
Aalborg University
On 2012-02-07 18:20, Jeffrey Altman wrote:
On 2/7/2012 9:20 AM, Bo Nygaard Bai wrote:
We have observed that windows clients running an installation of the
OpenAFS client version 1.7.201 and later will, unknown to the user,
print garbage on all our printers. Every time a user opens/refreshes the
Samba share exporting the printers, each available printer will print 2
pages each containing a single line of output:
,\ ☺☺
How is this data arriving at the printers? You say later that the
Windows Printer Spooler is disabled so there must be a direct connection
from some application to the printers.
Use SysInternals Process Monitor and WireShark to track the source of
the data being written to the process that is doing so.
In 1.7.2 the network provider interface, AFSRDFSProvider.dll, properly
fails a query for printers in the \\AFS name space. It reports that
there are none instead of listing the file shares.
In case the above UTF-8 does not survive the mail system:
<komma><backslash><space><smileyface><smileyface>
Just viewing the share exporting the printers will trigger this.
OpenAFS doesn't browse or otherwise interact with printers so it must be
an application process doing so in response to a network provider browse
request using the WNet API set.
We only see this when the OpenAFS Client Service is running and only
after version 1.7.201. It even happens when the windows Print Spooler
service is stopped but AFS is running.
If OpenAFS is halted the AFSRDFSProvider will report "not connected" to
all queries.
Has anybody else seen this or have an explanation?
I have not.
Should I file a bug report on this?
With whom? That is the question. Since the problem occurs with Samba
shared printers and not Microsoft Windows shared printers or Apple
Bonjour shared printers, perhaps its a bug in Samba.
no_error1_filtered
14:52:12,0818689 svchost.exe 896 CreateFile
\\130.225.51.90\pr-c1-103-bw\ CSC OBJECT PATH NOT FOUND Desired Access:
Read Attributes, Synchronize, Disposition: Open, Options: Synchronous IO
Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize:
n/a, Impersonating: ped-vm\ped
error_filtered
14:33:41,3920696 Explorer.EXE 2544 CreateFile
\\130.225.51.90\pr-c1-103-bw\_._AFS_IOCTL_._ SUCCESS Desired Access: Read
Data/List Directory, Write Data/Add File, Read Attributes, Synchronize,
Disposition: Open, Options: Write Through, Synchronous IO Non-Alert,
Non-Directory File, Attributes: n/a, ShareMode: Read, AllocationSize: n/a,
OpenResult: Opened
14:33:41,3983356 Explorer.EXE 2544 WriteFile
\\130.225.51.90\pr-c1-103-bw\_._AFS_IOCTL_._ SUCCESS Offset: 0, Length: 41,
I/O Flags: Write Through, Priority: Normal
14:33:41,4042403 Explorer.EXE 2544 ReadFile
\\130.225.51.90\pr-c1-103-bw\_._AFS_IOCTL_._ INVALID DEVICE REQUEST Offset:
41, Length: 8.192, Priority: Normal
14:33:41,4043567 Explorer.EXE 2544 CloseFile
\\130.225.51.90\pr-c1-103-bw\_._AFS_IOCTL_._ SUCCESS
14:33:41,4421625 Explorer.EXE 2544 CreateFile
\\130.225.51.90\pr-c1-103-bw\_._AFS_IOCTL_._ SUCCESS Desired Access: Read
Data/List Directory, Write Data/Add File, Read Attributes, Synchronize,
Disposition: Open, Options: Write Through, Synchronous IO Non-Alert,
Non-Directory File, Attributes: n/a, ShareMode: Read, AllocationSize: n/a,
OpenResult: Opened
14:33:41,4461407 Explorer.EXE 2544 WriteFile
\\130.225.51.90\pr-c1-103-bw\_._AFS_IOCTL_._ SUCCESS Offset: 0, Length: 41,
I/O Flags: Write Through, Priority: Normal
14:33:41,4498251 Explorer.EXE 2544 ReadFile
\\130.225.51.90\pr-c1-103-bw\_._AFS_IOCTL_._ INVALID DEVICE REQUEST Offset:
41, Length: 8.192, Priority: Normal
14:33:41,4499010 Explorer.EXE 2544 CloseFile
\\130.225.51.90\pr-c1-103-bw\_._AFS_IOCTL_._ SUCCESS
14:33:41,4699611 svchost.exe 896 CreateFile
\\130.225.51.90\pr-c1-103-bw\ CSC OBJECT PATH NOT FOUND Desired Access:
Read Attributes, Synchronize, Disposition: Open, Options: Synchronous IO
Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize:
n/a, Impersonating: ped-vm\ped
