AW: Problem with Studio 4.3.0.0 Windows 2003 Terminal Server andPrint Spooler

[Keith Bartlett]

Hi Rudolf

Possibly, a misconfigured DNS can cause delays on many activities.  On our networks we usually set the DNS to the local servers and then let them go to the net if they can't resolve the address

Cheers
Keith


Keith Bartlett - Adnet Ltd
Tel: 01491 642133    www.adnetltd.co.uk
Sent from my BlackBerry® wireless device

-----Original Message-----
From: Rudolf Bargholz <bargholz at onlinetravel.ch>
Date: Sat, 9 Jan 2010 11:42:17 
To: OmnisDev List - English<omnisdev-en at lists.omnis-dev.com>
Subject: AW: Problem with Studio 4.3.0.0 Windows 2003 Terminal Server and
 Print Spooler

Hi Keith,

Would the DNS settings react differently according to user privileges? But this is something I will look into on Monday. Thanks!

Regards

Rudolf

-----Ursprüngliche Nachricht-----
Von: omnisdev-en-bounces at lists.omnis-dev.com [mailto:omnisdev-en-bounces at lists.omnis-dev.com] Im Auftrag von Keith Bartlett
Gesendet: Samstag, 9. Januar 2010 11:03
An: OmnisDev English
Betreff: Re: AW: Problem with Studio 4.3.0.0 Windows 2003 Terminal Server andPrint Spooler

Hi Rudolf

DNS settings?  It's not trolling round the net looking for printers by any chance?

Cheers
Keith

Keith Bartlett - Adnet Ltd
Tel: 01491 642133    www.adnetltd.co.uk
Sent from my BlackBerry® wireless device

-----Original Message-----
From: Rudolf Bargholz <bargholz at onlinetravel.ch>
Date: Sat, 9 Jan 2010 06:50:58
To: OmnisDev List - English<omnisdev-en at lists.omnis-dev.com>
Subject: AW: Problem with Studio 4.3.0.0 Windows 2003 Terminal Server and  Print Spooler

Hi John,

Thanks for this.

  1.  anti virus scanning problem
No antivirus installed

  2.  a backup process locking a file
Clean server without any backup

  3.  server not updated to latest patches Up to date

  4.  print driver updates, or incompatible drivers, 32 bit on 64 bit, or visa Versa Only one printer driver installed on the server, and deactivated client printer mapping. And I made sure the driver left on the server is a 64 bit driver.

  5.  permissions/access rights not set properly.
This is my guess. The strange thing is, if we log in as the original administrator, the problems go away, but if we log in as a domain admin the problem can be reproduced. But where to go from there, that is a bit of a problem.

Regards

Rudolf Bargholz
_____________________________________________________________
Manage your list subscriptions at http://lists.omnis-dev.com
_____________________________________________________________
Manage your list subscriptions at http://lists.omnis-dev.com