BartM Posted January 29, 2013 Posted January 29, 2013 We have a problem with our Print Manager Plus setup. We have cloned Windows 7 machines in several student rooms. Because they are cloned they have the same computername but they get a unique IP address from a DHCP server. They are in a workgroup, called WORKGROUP. They print to several student printers on a Windows Server 2008R2 print server. The server is in a domain and it is running Print Manager Plus from Software Shelf, version 8.0.137.193. Previously we ran a setup where the printer server was Windows Server 2003 and Print Manager Plus was version 7.0.131.61 and this worked well but now, with Server 2008R2 it is not working. The Print Manager Plus logs show that Print Manager Plus is not resolving the computername, therefore it does not prompt the student for verification and it just prints the job. Previously Print manager plus would log the incoming job by IP address and so was able to communicate with the client, now it logs it by Netbios name, which is not unique. Software Shelf say that we need to give each computer a unique name, which makes sense from a networking point of view but is difficult in an environment where the computers are frequently re-imaged. It also does not address why the setup worked previously, with the Sever 2003 print server. Does anyone have a similar setup or any insight into why Print Manager Plus is now attempting to use Netbios when it previously used IP addresses? I am quite open to suggestions that our Server 2008R2 setup is not right, but I can't see where the problem lies. ====Example of a log on the new server - Server 2008R2 and Print Manager Plus 8.0.137.193.================== 12:23:43: CPMPPipeServer::SendToClientThread - sending to: STUDENT-LAB 12:23:43: CPMPPipeServer::SendToClientThread - return server: SERVER1 12:23:43: CPMPPipeServer::SendToClientThread - id: 264503799 12:23:43: CPMPPipeServer::SendToClientThread - Using Citrix Support: No 12:23:46: CPMPPipeServer::SendToClientTCP - Error: -1 - Unknown Error 12:23:51: CPMPPipeServer::SendToClientThread - Pipe opening pipe \\STUDENT-LAB\pipe\PMPClientComPeer_Student failed with error code 53 12:23:54: CPMPPipeServer::SendToClientThread - Pipe opening pipe \\STUDENT-LAB\pipe\PMPClientComPeer failed with error code 53 12:23:54: CPMPPipeServer::ProcessResponse - msg: action=UserConfirmationNoClient|uid=264503799|ok=1|billable=0| 12:23:54: JTH::JobFilter_User - KM-Bizhub Student-Lab(167): Deducting Balance - UserName: Student, Total Current Balance: £424.00, New Balance: £423.00 ====Example of a log on the old server - Server 2003 and Print Manager Plus 7.0.131.61 ================== 13:08:25: CPMPPipeServer::SendToClientThread - sending to: 10.10.93.102 13:08:25: CPMPPipeServer::SendToClientThread - return server: SERVER1 13:08:25: CPMPPipeServer::SendToClientThread - id: 113789 13:08:25: CPMPPipeServer::SendToClientThread - Using Citrix Support: No 13:08:25: CPMPPipeServer::SendToClientTCP - success 13:08:36: CPMPPipeServer::ProcessResponse - msg: action=UserPswConfirmation|uid=113789|ok=1|user=?#S6r!*15C74F9B13530C6C4E245E924F176688|userpsw=?786kr!*15B84FF7134E27|project=|projectpsw=|comment=| 13:08:51: JTH::JobFilter_User - KM-Bizhub Student-Lab(3): Deducting Balance - UserName: STU0001, Total Current Balance: £488.00, New Balance: £487.00
R0B0_Ape Posted August 15, 2013 Posted August 15, 2013 Hey Bart, Not sure if you ever found a solution. It was happening to random imaged computers for me as well. I was able to trace it down to bad DNS/DHCP records. I deleted the records (which were assigned to other computers, btw), performed an ipconfig /release-/renew and I was able to get the pop up for authenticaion. You can also try changing the computernames. Unfortunately that was not an option we wanted to pursue. Good luck.
adrian_costea Posted August 16, 2013 Posted August 16, 2013 Every workstation needs to have a unique name, if not you will have conflicts on your network. Rename your PC's then try again and it should work. If you are re-imaging the PC's so often, you could use a WDS server and configure it to give a unique name to every PC.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now