HP Business Inkjet 2800 Windows 7 multiple copies

A well documented problem. We have a sort of solution.

A client with this printer / OS combination could not get multiple copies to print. Doesn't matter how many copies are selected only 1 copy was printed.

Came across this link which looked hopeful. It provided another link to download some drivers. Just a word of warning - you have to access this second site using IE, other broswers cannot access the page.

I downloaded and tried both the PCL5 and PS drivers but nothing made any difference.

In order to provide for the client I went into printer properties and changed the default page count setting to 2 instead on 1 just to see if that would give us a workaround.

Yipee!! 2 pages printed out. Ok lets see if changing the default 2 to 1 on the normal print window works and Yeeha only one page printed. On a roll now what if I change it to 3 copies. Wow! It worked. I repeated with 6 copies and all seems fine.

This is however bizarre behaviour and with any luck one of the HP printer team will see this post and attempt to correct their code.

Better than that. HP, how about producing the PCL6 drivers for this printer so that we don't need these workarounds.

A related problem which we are also having to sort out is why tray 2 is not recognised. For those interested in that problem click here.

The security database on the server does not have a computer account for this workstation trust relationship.

We recently has this error message appear when trying to log on Windows 7 workstations to our Windows 2003 domain server.
"The security database on the server does not have a computer account for this workstation trust relationship."
We trawled through the Google searches for this message and there are pages of reports of this error.
Let me give you the circumstances.
Our domain server failed. We could not get it to get through POST and BIOS to try to find and operating system. That was the first big 'Ouch'.
So we rebuilt the server on to new hardware and configured it, as we thought, the same. We initially had some issues with DNS and NICs not doing as they should but the upshot was that our 2 Windows 7 workstations could not connect to the domain. Please note this did not affect our remaining XP workstation which logged just fine.
After looking at the Goggle responses we noticed that we had rebuilt the domain but missed off the '.local' on the domain name.
So we rebuilt being more careful next time. Even so we got a capital letter in the wrong place in the domain name. So we rebuilt a third time. This time we are sure we got everything right. It made not a jot of difference.
Other websites had suggested we disconnect from the domain and reconnect to the new domain. Not an iota of difference.
Finally we had to reinstall the operating system on both our Windows 7 machines.
One side effect of this, despite having installed onto completely new hard disks to preserve the data on the old disk, is that on one of the machines we have lost ALL out Outlook pst files. Some emails going back 6 years with important information.
Couple this with the total data loss of all information on the server did not make us very happy.
I will finish with this comment. Why, oh why, Microsoft is it so hard to get your systems to talk to each other. This is hardly a ringing endorsement for the improvements in Windows 7 when XP performs better in what was already a very fraught situation. Please try to do better next time.

AN ATTEMPT TO RESOLVE THE DNS NAME OF A DC IN THE DOMAIN BEING JOINED HAS FAILED!

We had a problem connecting a newly installed Windows 7 system to a Windows 2008 SBS domain.
We got the message "AN ATTEMPT TO RESOLVE THE DNS NAME OF A DC IN THE DOMAIN BEING JOINED HAS FAILED! PLEASE VERIFY THIS CLIENT IS CONFIGURED TO REACH A DNS SERVER THAT CAN RESOLVE DNS NAMES IN THE TARGET DOMAIN."
We checked all the setting and everything was correct.
We checked through Google and we found a lot of posts relating to this problem but not many where the problem was resolved.
We looked on the Microsoft Technet with the same result.
We tried taking a newly installed Windows 7 machine and adding it to our own domain (Windows 2003) and there were no problems. This points to the server being the issue.
We referred to our copy of Stanek Administrator's guide and on Page 218 we found a command line utility called dnscmd.exe. We ran this utility and found that the DNS server was listening on IP address 192.168.0.2. The only local adaptor was on IP address 192.168.0.210 so this was a problem.
We fixed the DNS set up on the server. The following link will tell you how to restrict the DNS listening devices click here so please amend to your needs
Once we had done this the new computer joined the domain without problem
Further information contact us through our website.