Prev: How to access data buffers in a completion routine for a KMDF driv
Next: updated driver in OOBE(audit mode) no longer selected in norma
From: Michael Steiger on 20 Jan 2010 15:54
Hello!

I have developed a Port Monitor which is running fine for the last few
years.

Now I had to add some functionality which includes information about
the client machine where the printjob was originally submitted.

After calling GetJob with JOB_INFO_2 I use the pMachineName field.
But now I have the problem that most of the time this field includes
the IP address of the client (like "\\192.168.1.170") which is exactly
what I need. But sometimes I get the machinename (like "\\NAME").

In my test environment
Server: Windows Server 2008 x64 which is running the Port Monitor
all tests with XP or Vista clients (had no chance to test Win7 yet)
result in IP address in pMachineName.

In the production environment
Server: Windows Server 2008 x64 which is running the Port Monitor
tests with XP client result in the machinename
tests with Vista clients result in the IP address

The problem is that this is happening in a WLAN environment where I
have to use the IP address to lookup in a Radius database.
I thought about doing a DNS lookup but the machinename which gets sent
in the XP case is the locally defined machinename of the XP laptop
which is not defined in the DNS because these are travelling users.

Has anyone an idea what to configure so that every time the IP address
get set in pMachineName?

Best regards
Michael
From: Michael Steiger on 25 Jan 2010 15:08
Is there really no one out there who can help me with this issue?
 | 
Pages: 1
Prev: How to access data buffers in a completion routine for a KMDF driv
Next: updated driver in OOBE(audit mode) no longer selected in norma