The printer is hooked up to 2003 ms small business server its shared and it publishes to the list of available printers. the status shows ready the network speed has been slowed to 10mbs Auto but every time the test job errors out I down loaded drivers from cannon but i am not sure they are the correct ones. or if they are installed properly ?
a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need. goodluck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
HP LaserJet, Color LaserJet and LaserJet MFP Products - Print driver Client / Server Connections in a mixed 32-bit and 64-bit environment
ISSUE: 32-bit clients are not able to connect to shared Universal Print drivers or discrete drivers on a 64-bit print server or vice-versa. These scenarios may involve Server 2003/Server 2008 64-bit print servers with Windows XP, Vista, 7 32-bit clients. It is also possible that the server editions could be 32-bit versions with 64-bit clients.
The administrator will need to download the 64-bit AND 32-bt version of the print driver from www.hp.com . If the server involved is a 64-bit version, the 64-bit version of the print driver will need to be installed and mapped to the printer via TCP/IP. Ensure that the print driver has been shared on the network by going to the print driver properties and enabling Share this printer within the Sharing tab.
Ensure that communication has been established and that a driver test page can be printed from the 64-bit server. Once functionality has been confirmed from the 64-bit server, proceed to the next step.
Currently, 64-bit clients will be able to connect to the shared 64-bit print driver that has been installed on the 64-bit server as the architecture currently matches. However, if 32-bit clients wish to map to the shared 64-bit print driver on the 64-bit server, the 32-bit version of the same driver will need to be installed within the current 64-bit driver.
This process can be done by navigating to the printer properties of the 64-bit driver on the 64-bit server, clicking the Sharing tab and clicking the Additional Drivers button.
Once the administrator clicks on the Additional Drivers button, the next screen will allow the administrator to load the 32-bit drivers by placing a checkmark in the x86 button and clicking the OK button.
Once the administrator clicks the OK button, a print driver window will pop-up asking for the 32-bit driver components. Again, the administrator will need to download, and extract the 32-bit version of the print driver on the 64-bit server. Once the window below comes up, the administrator will need to navigate to the 32-bit driver components and select the appropriate driver .inf file.
For example, the UPD .inf file would be the first file in the list and be named hpcuXXXc.inf.
Once the appropriate .inf file is selected, the 32-bit driver components will be installed within the 64-bit driver on the 64-bit server. This can be verified as both x86 (32-Bit) and x64 (64-Bit) boxes will now be checked and show the status as installed by clicking the Additional Drivers button compared to the screenshot in Step 3 above.
Now that 64-Bit and 32-Bit drivers have been loaded onto the 64-Bit server, 32-Bit and 64-Bit clients can now navigate to the shared print driver on the 64-Bit server, by manually navigating to the shared print driver on the 64-Bit server from the client machine. Typically the path is \\servername\sharedprintername.
Once the client maps to the shared print driver, printing should work successfully.
For problems or errors that continue to occur after completing the aforementioned process, ensure that the latest version of the print drivers are being used www.hp.com . If there are problems with older discrete drivers, it is recommended to use the latest version of the Universal Print Driver which can be found at www.hp.com/go/upd .
Windows sharing based printers are dependent on the computer where the printer is attached. This means that if the computer is turned off, or is in the sleep/hibernate mode, then all the computers that can print through that server will not be able to print. To solve this issue you can use external print servers to share printers in the home/office. External print servers are connected to the router which allows it to be available on the network without being dependent on any other computer system. External print servers are available in both wireless and wired versions, and the choice between those options is based on the needs of the home or office.get more information and help for Network Printer Configuration .Hope this helps you.
Yes is possible. Use Routing and Remote Access facility from Windows 2003 server to create a VPN Server. Create a VPN connection to Windows server, and thus you get an IP address from windows 2003 server and you can use printer.
Ok, first off, system specs:
- Windows XP Home SP2
- HP PSC 1*** (not sure) Inkjet Printer
In MS Office 2003, when you print a document, the printer spits out a
blank page. When I did a test page in the printer settings, the test
page printed perfectly fine. And pretty much any other non MS based
program prints (tested: AOL EMails/webpages [IE6]).
I reinstalled the drivers and checked for updates...all good. Restarted the PC with printer unplugged and vice-versa.
I have had a similar issue with both laserjet 3005N and 1320N machines setup as network printers on a windows 2003 print server. Both machines install correctly and print test pages but once you push to much of a print job to it (in my case it was a 12mb pdf file) the printer stops printing and never prints again for some reason. After a quick reboot a test page will print but what gives?? Buffer issues? Not enough ram? None of this makes sense since the printer displays nothing and just stops printNo test pages or anything. I tried re-installing it and rebooting it. Nothing.
You can physically connect the printers to the server and share it from there
leave the printers connected to your computer and have the server connect to them via a Local Port which routes to your computer!!
To do the Create the local ports you'll need to 1.) share the printers on your pc
2.) Go to the server and go to printers in control panel
3.)Click on Add a new printer then next
4.)Select Local Printer connected to this computer; De-select Automatically Detect Printer
5.)Select Create new port and select Local Port
6.)In the enter a port name, enter the full network path to the printer i.e. \\your-pc-name\printer-share-name
7.) Select the drivers for that specific printer(if its not there click on have disk then browse to the drivers to install them)
8.) Continue through the installation until finish)
9.) Repeat steps for additional printers
Keep in mind that your computer still needs to be on!
You can check to see if your printer support a network card to make them fully network printer you can add them to the server this way and only the server would need to be on!
you can also get a print server(Device that makes regular printers into network printers).
Now when it comes to the scanning, i don't know of any way to share a scanner with just windows alone, but there are third party software that allows you to do that Check out http://www.remote-scan.com/
There are also printers that sorta do the scanners sharing by automatically scanning and putting files in a designated area on the network!
Hope this was helpful