speckytecky Posted October 20, 2006 Posted October 20, 2006 We have a new Dell OptiPlex 745 PC prints to default USB connected printer. Also prints to Networked Brother Laser and Toshiba machines no problem when first or reinstalled. However, reboot and only USB printer is active. Remainder fail to connect. Delete Brother and Toshiba machines from Printers and Faxes and reinstall and all OK again until reboot then fail to pick up brother and Toshiba. Checked Computer Management no obvious problem Printer Spooler service status = started and automatic. All other Dell machines in this Workgroup keep the connection apart from this new Optiplex 745. Dell support scratching their heads and not offering workable solutions so far! Any suggestions please?
djm968 Posted October 20, 2006 Posted October 20, 2006 What make model is the default USB connected printer?
speckytecky Posted October 20, 2006 Author Posted October 20, 2006 What make model is the default USB connected printer? Epson 950 Photo. Previous Dell PC of HT was connected to it and had no problems with accessing Network printers. Verry strange!
indiegirl Posted October 20, 2006 Posted October 20, 2006 Now I have no idea if this is related in any way, but we had something similar with a direct-linked printer and the machine wouldn't pick up any of our networked HPs... you could try if nothing else: In gpedit.msc on the local machine: Computer Configuration --> Administrative Templates --> Printers I set the top one "Allow Printers To Be Published" to 'enabled'. I know that theoretically it shouldn't have anything to do with it, because that setting *should* publish any direct printers that are shared, but strangely enough after a reboot ours picked them all up. Don't ask...!!!
u8dmtm Posted November 11, 2006 Posted November 11, 2006 If the networked printers are installed on a server, when you reboot your machine are your authenticating with that server (i.e. if your running a standalone / workgroup workstation then).
speckytecky Posted November 13, 2006 Author Posted November 13, 2006 Mapping the network drive from the offending machine seems to have solved the problem. thanks all for the very useful input.
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