Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 310
  • Last Modified:

Delayed Printers, Office 2003

Suddenly, and without any newly installed updates or programs, and on only one workstation in my office, it will now take 5 to 10 seconds after pressing the printer icon on the top of the screen in Word or Excel before it send the job the printer queue.

I have found online, even on Microsoft's site, some solutions to delayed printing, but nothing has worked to alleviate this delay.

I have changed settings in Template Manager, I've updated the firmware and drivers for the printer (after completely uninstalling it), nothing helps.

If I send something from command line, or from the Print Test Page, its queued instantly.  This printer is connected via parallel because we have some old Cobol software who's escape codes don't play well with USB, however I don't think that's the issue since command line printing goes quite quickly.

Has anyone run into this issue before, or have any ideas what to do?  I've searched for days for solutions.
0
BMIT
Asked:
BMIT
  • 4
  • 2
2 Solutions
 
Randy DownsOWNERCommented:
try from another User profile on the PC in question
0
 
johnb6767Commented:
Whenever I have had problems like this before, a removal of the printers, AND thier drivers, and a reinstallation of the printer has resolved it....
0
 
BMITAuthor Commented:
I had already tried uninstalling the printer and deleting all drivers associated with it before reinstalling the printer, no change in operation.  I did this again to be sure, again not change in behavior.

The PC will allow me to log on locally, and everything works exactly as it is supposed to when logged in locally (prints immediately when button is pressed, even when printing a file off the server).  However, it will not allow any domain users to logon to that workstation, even my administrator account.  It states that the domain is not available.

How can the domain not be available if the rest of the workstations are working fine, and this user can log in fine on this workstation?

Strange.  Anyone with any ideas?
0
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

 
Randy DownsOWNERCommented:
If you log on locally then the domain doesn't exist. Without connecting through a VPN the domain is unreachable.
0
 
Randy DownsOWNERCommented:
Try logging on as a domain user that doesn't have a profile on the machine (i.e., their 1st visit). If nothing else create a new test user for your domain.
0
 
BMITAuthor Commented:
The domain is local.  The profile that has been logging into this domain from this workstation has been doing so for years.  I can still use the current profile, the one I'm having issues printing from, to log into the domain.

I tried logging into the domain using a profile that had never used that particular workstation before, that profile was a domain administrator profile (mine).  That's when it gave the error that he domain was unreachable.

I realize that the workstation will cache domain credentials and if the domain isn't found, will act as if it has logged in even if it find the domain unreachable.  It must be doing this.

However, when logged in locally to the workstation I have full access to all shares on the domain controller.  There is no VPN involved in this issue.

I've tried deleting the computer profile from the domain controller and let it recreate it when I log in, and it does.  That indicates to me that the profile currently using that computer as a workstation has communication with the domain controller.  Can't understand why other profiles will incite the "unreachable domain" error.
0
 
Randy DownsOWNERCommented:
It appears workstation is not communicating with the login server. Maybe there is another server involved.

I'm not sure how you can connect to shares not logged into the domain unless they reside on this machine. Perhaps you have a connect as using a domain user account.

Maybe try some of the tips here to see which server is authenticating.

http://forums.techguy.org/windows-server/810549-how-determine-current-domain-controller.html

If you are running Win 2003 server this may help - http://www.microsoft.com/downloads/en/details.aspx?FamilyId=6EC50B78-8BE1-4E81-B3BE-4E7AC4F0912D&displaylang=en
0

Featured Post

Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now