Printer very slow to select

Hi guys,

I'm really hoping someone can help me here;
We have a client running a Windows Server 2003 R2 SP2 Terminal server, and
remote printer selection runs terribly slow.

One of the people connecting to this works from home, over a hardware VPN
(their edge firewall/router establishes this to the office firewall/router).
When they try to print a document (from anywhere - Excel, Word, Moneyworks
etc - the app doesn't seem to matter) the printer selection freezes when they
pick their printer.

They can pick any printer in the head office (where the TS box is), but when
they select their own printer it freezes. This happens when they connect from
home, but also when they bring their laptop into the office and try to pick
their home printer.

Their printer is a Brother HL-5350DN network printer, directly attached to
the network. From the TS server I can ping their printer, and get around
10-15ms response times.

Works fine for the admin login.

So far I have tried deleting their profile, elevating their rights to domain
admin and re-loading the printer.
This issue isn't confined to just their login - I tried another TS user, and
got the same problem. Again, logging in as admin the problem isn't there.

Specs:
Server - dual Xeon E5405 CPU's, 4GB RAM, SAS RAID1 array, Server 2003 R2
SP2, Microsoft Office 2007 SP2.
Printer in question: Brother HL-5350DN

Thanks in Advance,

Joe

 

Hi Joe,

Which driver are you using for the 5350DN on your TS?

I recommend you use either the WHQL certified BR-Script
driver or the WHQL certified Printer Driver, or if those
are not suitable you could substitute a PCL driver that
shipped with 2003. The "Full Driver & Software Package"
appears to be too bloated at 125.94MB for a TS.

Brother HL-5350DN 2003 driver downloads



If you want to continue with the current driver you could
use Process Monitor to narrow down any permission
issues.

Process Monitor



Another thing to consider is to use TS printer autocreation
instead of connecting to the user's printer through the VPN.
My statements about driver versions still apply in this scenario.

Thanks.

-TP

Joe from NZ wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi guys,
>
> I'm really hoping someone can help me here;
> We have a client running a Windows Server 2003 R2 SP2 Terminal
> server, and remote printer selection runs terribly slow.
>
> One of the people connecting to this works from home, over a hardware
> VPN (their edge firewall/router establishes this to the office
> firewall/router). When they try to print a document (from anywhere -
> Excel, Word, Moneyworks etc - the app doesn't seem to matter) the
> printer selection freezes when they pick their printer.
>
> They can pick any printer in the head office (where the TS box is),
> but when they select their own printer it freezes. This happens when
> they connect from home, but also when they bring their laptop into
> the office and try to pick their home printer.
>
> Their printer is a Brother HL-5350DN network printer, directly
> attached to the network. From the TS server I can ping their printer,
> and get around 10-15ms response times.
>
> Works fine for the admin login.
>
> So far I have tried deleting their profile, elevating their rights to
> domain admin and re-loading the printer.
> This issue isn't confined to just their login - I tried another TS
> user, and got the same problem. Again, logging in as admin the
> problem isn't there.
>
> Specs:
> Server - dual Xeon E5405 CPU's, 4GB RAM, SAS RAID1 array, Server 2003
> R2 SP2, Microsoft Office 2007 SP2.
> Printer in question: Brother HL-5350DN
>
> Thanks in Advance,
>
> Joe <!--colorc--><!--/colorc-->

 

Hi,
Thanks for your reply.
We are already using the WHQL driver. I downloaded and installed this last
week.
(I'm not a fan of installing "full driver packages" on servers if I can
avoid it!)

The client affected by this tells me this issue only started maybe a month
ago - before this everything was fine. Unfortunately nobody seems to be able
to pinpoint the exact day, or what has changed.

It has to be some sort of permission issue (registry even) because it is
fine when I log in as admin, although even elevating the user to domain admin
(gone as far as setting the default group to this and removing domain users
in case it is a deny issue instead of an allow issue) does not get the user
working correctly.

I'm heading out on-site later today to do some more testing. Any further
thoughts would be greatly appreciated!

Cheers,

Joe


"TP" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi Joe,
>
> Which driver are you using for the 5350DN on your TS?
>
> I recommend you use either the WHQL certified BR-Script
> driver or the WHQL certified Printer Driver, or if those
> are not suitable you could substitute a PCL driver that
> shipped with 2003. The "Full Driver & Software Package"
> appears to be too bloated at 125.94MB for a TS.
>
> Brother HL-5350DN 2003 driver downloads
>
>
>
> If you want to continue with the current driver you could
> use Process Monitor to narrow down any permission
> issues.
>
> Process Monitor
>
>
>
> Another thing to consider is to use TS printer autocreation
> instead of connecting to the user's printer through the VPN.
> My statements about driver versions still apply in this scenario.
>
> Thanks.
>
> -TP
>
> Joe from NZ wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
> > Hi guys,
> >
> > I'm really hoping someone can help me here;
> > We have a client running a Windows Server 2003 R2 SP2 Terminal
> > server, and remote printer selection runs terribly slow.
> >
> > One of the people connecting to this works from home, over a hardware
> > VPN (their edge firewall/router establishes this to the office
> > firewall/router). When they try to print a document (from anywhere -
> > Excel, Word, Moneyworks etc - the app doesn't seem to matter) the
> > printer selection freezes when they pick their printer.
> >
> > They can pick any printer in the head office (where the TS box is),
> > but when they select their own printer it freezes. This happens when
> > they connect from home, but also when they bring their laptop into
> > the office and try to pick their home printer.
> >
> > Their printer is a Brother HL-5350DN network printer, directly
> > attached to the network. From the TS server I can ping their printer,
> > and get around 10-15ms response times.
> >
> > Works fine for the admin login.
> >
> > So far I have tried deleting their profile, elevating their rights to
> > domain admin and re-loading the printer.
> > This issue isn't confined to just their login - I tried another TS
> > user, and got the same problem. Again, logging in as admin the
> > problem isn't there.
> >
> > Specs:
> > Server - dual Xeon E5405 CPU's, 4GB RAM, SAS RAID1 array, Server 2003
> > R2 SP2, Microsoft Office 2007 SP2.
> > Printer in question: Brother HL-5350DN
> >
> > Thanks in Advance,
> >
> > Joe <!--colorc--><!--/colorc-->
>
> <!--colorc--><!--/colorc-->

 

Did you find any solution? I am also having this problem.

"Joe from NZ" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi,
> Thanks for your reply.
> We are already using the WHQL driver. I downloaded and installed this last
> week.
> (I'm not a fan of installing "full driver packages" on servers if I can
> avoid it!)
>
> The client affected by this tells me this issue only started maybe a month
> ago - before this everything was fine. Unfortunately nobody seems to be able
> to pinpoint the exact day, or what has changed.
>
> It has to be some sort of permission issue (registry even) because it is
> fine when I log in as admin, although even elevating the user to domain admin
> (gone as far as setting the default group to this and removing domain users
> in case it is a deny issue instead of an allow issue) does not get the user
> working correctly.
>
> I'm heading out on-site later today to do some more testing. Any further
> thoughts would be greatly appreciated!
>
> Cheers,
>
> Joe
>
>
> "TP" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > Hi Joe,
> >
> > Which driver are you using for the 5350DN on your TS?
> >
> > I recommend you use either the WHQL certified BR-Script
> > driver or the WHQL certified Printer Driver, or if those
> > are not suitable you could substitute a PCL driver that
> > shipped with 2003. The "Full Driver & Software Package"
> > appears to be too bloated at 125.94MB for a TS.
> >
> > Brother HL-5350DN 2003 driver downloads
> >
> >
> >
> > If you want to continue with the current driver you could
> > use Process Monitor to narrow down any permission
> > issues.
> >
> > Process Monitor
> >
> >
> >
> > Another thing to consider is to use TS printer autocreation
> > instead of connecting to the user's printer through the VPN.
> > My statements about driver versions still apply in this scenario.
> >
> > Thanks.
> >
> > -TP
> >
> > Joe from NZ wrote:<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > Hi guys,
> > >
> > > I'm really hoping someone can help me here;
> > > We have a client running a Windows Server 2003 R2 SP2 Terminal
> > > server, and remote printer selection runs terribly slow.
> > >
> > > One of the people connecting to this works from home, over a hardware
> > > VPN (their edge firewall/router establishes this to the office
> > > firewall/router). When they try to print a document (from anywhere -
> > > Excel, Word, Moneyworks etc - the app doesn't seem to matter) the
> > > printer selection freezes when they pick their printer.
> > >
> > > They can pick any printer in the head office (where the TS box is),
> > > but when they select their own printer it freezes. This happens when
> > > they connect from home, but also when they bring their laptop into
> > > the office and try to pick their home printer.
> > >
> > > Their printer is a Brother HL-5350DN network printer, directly
> > > attached to the network. From the TS server I can ping their printer,
> > > and get around 10-15ms response times.
> > >
> > > Works fine for the admin login.
> > >
> > > So far I have tried deleting their profile, elevating their rights to
> > > domain admin and re-loading the printer.
> > > This issue isn't confined to just their login - I tried another TS
> > > user, and got the same problem. Again, logging in as admin the
> > > problem isn't there.
> > >
> > > Specs:
> > > Server - dual Xeon E5405 CPU's, 4GB RAM, SAS RAID1 array, Server 2003
> > > R2 SP2, Microsoft Office 2007 SP2.
> > > Printer in question: Brother HL-5350DN
> > >
> > > Thanks in Advance,
> > >
> > > Joe <!--colorc--><!--/colorc-->
> >
> > <!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

Hi Edwin,

I managed to get around this issue by making the printer the default for the
user affected by this.
It isn't so much a solution but rather a patch, and this user hasn't had any
issues. They can easily change the default to a 'local' office printer when
they are in the office, but when they are home they can just click print, and
it works perfectly.

Hope this helps you.

"Edwin" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Did you find any solution? I am also having this problem.
>
> "Joe from NZ" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > Hi,
> > Thanks for your reply.
> > We are already using the WHQL driver. I downloaded and installed this last
> > week.
> > (I'm not a fan of installing "full driver packages" on servers if I can
> > avoid it!)
> >
> > The client affected by this tells me this issue only started maybe a month
> > ago - before this everything was fine. Unfortunately nobody seems to be able
> > to pinpoint the exact day, or what has changed.
> >
> > It has to be some sort of permission issue (registry even) because it is
> > fine when I log in as admin, although even elevating the user to domain admin
> > (gone as far as setting the default group to this and removing domain users
> > in case it is a deny issue instead of an allow issue) does not get the user
> > working correctly.
> >
> > I'm heading out on-site later today to do some more testing. Any further
> > thoughts would be greatly appreciated!
> >
> > Cheers,
> >
> > Joe
> >
> >
> > "TP" wrote:
> > <!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > Hi Joe,
> > >
> > > Which driver are you using for the 5350DN on your TS?
> > >
> > > I recommend you use either the WHQL certified BR-Script
> > > driver or the WHQL certified Printer Driver, or if those
> > > are not suitable you could substitute a PCL driver that
> > > shipped with 2003. The "Full Driver & Software Package"
> > > appears to be too bloated at 125.94MB for a TS.
> > >
> > > Brother HL-5350DN 2003 driver downloads
> > >
> > >
> > >
> > > If you want to continue with the current driver you could
> > > use Process Monitor to narrow down any permission
> > > issues.
> > >
> > > Process Monitor
> > >
> > >
> > >
> > > Another thing to consider is to use TS printer autocreation
> > > instead of connecting to the user's printer through the VPN.
> > > My statements about driver versions still apply in this scenario.
> > >
> > > Thanks.
> > >
> > > -TP
> > >
> > > Joe from NZ wrote:
> > > > Hi guys,
> > > >
> > > > I'm really hoping someone can help me here;
> > > > We have a client running a Windows Server 2003 R2 SP2 Terminal
> > > > server, and remote printer selection runs terribly slow.
> > > >
> > > > One of the people connecting to this works from home, over a hardware
> > > > VPN (their edge firewall/router establishes this to the office
> > > > firewall/router). When they try to print a document (from anywhere -
> > > > Excel, Word, Moneyworks etc - the app doesn't seem to matter) the
> > > > printer selection freezes when they pick their printer.
> > > >
> > > > They can pick any printer in the head office (where the TS box is),
> > > > but when they select their own printer it freezes. This happens when
> > > > they connect from home, but also when they bring their laptop into
> > > > the office and try to pick their home printer.
> > > >
> > > > Their printer is a Brother HL-5350DN network printer, directly
> > > > attached to the network. From the TS server I can ping their printer,
> > > > and get around 10-15ms response times.
> > > >
> > > > Works fine for the admin login.
> > > >
> > > > So far I have tried deleting their profile, elevating their rights to
> > > > domain admin and re-loading the printer.
> > > > This issue isn't confined to just their login - I tried another TS
> > > > user, and got the same problem. Again, logging in as admin the
> > > > problem isn't there.
> > > >
> > > > Specs:
> > > > Server - dual Xeon E5405 CPU's, 4GB RAM, SAS RAID1 array, Server 2003
> > > > R2 SP2, Microsoft Office 2007 SP2.
> > > > Printer in question: Brother HL-5350DN
> > > >
> > > > Thanks in Advance,
> > > >
> > > > Joe
> > >
> > > <!--colorc--><!--/colorc--><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

At your place only one user is having this situation?
Here all users have problems with connecting the printqueues. Only when an
administrator account for that terminal server has connected the same
printers the users should connect, then users will smoothly login (with all
printerconnections).
Thought you had the same but I guess I was wrong.

Thanks anyway. Or got a solution for this 'new problem'?
Greetings,
Edwin

"Joe from NZ" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi Edwin,
>
> I managed to get around this issue by making the printer the default for the
> user affected by this.
> It isn't so much a solution but rather a patch, and this user hasn't had any
> issues. They can easily change the default to a 'local' office printer when
> they are in the office, but when they are home they can just click print, and
> it works perfectly.
>
> Hope this helps you.
>
> "Edwin" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > Did you find any solution? I am also having this problem.
> >
> > "Joe from NZ" wrote:
> > <!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > Hi,
> > > Thanks for your reply.
> > > We are already using the WHQL driver. I downloaded and installed this last
> > > week.
> > > (I'm not a fan of installing "full driver packages" on servers if I can
> > > avoid it!)
> > >
> > > The client affected by this tells me this issue only started maybe a month
> > > ago - before this everything was fine. Unfortunately nobody seems to be able
> > > to pinpoint the exact day, or what has changed.
> > >
> > > It has to be some sort of permission issue (registry even) because it is
> > > fine when I log in as admin, although even elevating the user to domain admin
> > > (gone as far as setting the default group to this and removing domain users
> > > in case it is a deny issue instead of an allow issue) does not get the user
> > > working correctly.
> > >
> > > I'm heading out on-site later today to do some more testing. Any further
> > > thoughts would be greatly appreciated!
> > >
> > > Cheers,
> > >
> > > Joe
> > >
> > >
> > > "TP" wrote:
> > >
> > > > Hi Joe,
> > > >
> > > > Which driver are you using for the 5350DN on your TS?
> > > >
> > > > I recommend you use either the WHQL certified BR-Script
> > > > driver or the WHQL certified Printer Driver, or if those
> > > > are not suitable you could substitute a PCL driver that
> > > > shipped with 2003. The "Full Driver & Software Package"
> > > > appears to be too bloated at 125.94MB for a TS.
> > > >
> > > > Brother HL-5350DN 2003 driver downloads
> > > >
> > > >
> > > >
> > > > If you want to continue with the current driver you could
> > > > use Process Monitor to narrow down any permission
> > > > issues.
> > > >
> > > > Process Monitor
> > > >
> > > >
> > > >
> > > > Another thing to consider is to use TS printer autocreation
> > > > instead of connecting to the user's printer through the VPN.
> > > > My statements about driver versions still apply in this scenario.
> > > >
> > > > Thanks.
> > > >
> > > > -TP
> > > >
> > > > Joe from NZ wrote:
> > > > > Hi guys,
> > > > >
> > > > > I'm really hoping someone can help me here;
> > > > > We have a client running a Windows Server 2003 R2 SP2 Terminal
> > > > > server, and remote printer selection runs terribly slow.
> > > > >
> > > > > One of the people connecting to this works from home, over a hardware
> > > > > VPN (their edge firewall/router establishes this to the office
> > > > > firewall/router). When they try to print a document (from anywhere -
> > > > > Excel, Word, Moneyworks etc - the app doesn't seem to matter) the
> > > > > printer selection freezes when they pick their printer.
> > > > >
> > > > > They can pick any printer in the head office (where the TS box is),
> > > > > but when they select their own printer it freezes. This happens when
> > > > > they connect from home, but also when they bring their laptop into
> > > > > the office and try to pick their home printer.
> > > > >
> > > > > Their printer is a Brother HL-5350DN network printer, directly
> > > > > attached to the network. From the TS server I can ping their printer,
> > > > > and get around 10-15ms response times.
> > > > >
> > > > > Works fine for the admin login.
> > > > >
> > > > > So far I have tried deleting their profile, elevating their rights to
> > > > > domain admin and re-loading the printer.
> > > > > This issue isn't confined to just their login - I tried another TS
> > > > > user, and got the same problem. Again, logging in as admin the
> > > > > problem isn't there.
> > > > >
> > > > > Specs:
> > > > > Server - dual Xeon E5405 CPU's, 4GB RAM, SAS RAID1 array, Server 2003
> > > > > R2 SP2, Microsoft Office 2007 SP2.
> > > > > Printer in question: Brother HL-5350DN
> > > > >
> > > > > Thanks in Advance,
> > > > >
> > > > > Joe
> > > >
> > > > <!--colorc--><!--/colorc--><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

Hi Edwin,

The issue is only for one printer which is located off-site. the on-site
printers are fine.
The printer in question sits in a home office, and when the user who works
at home tries to switch their printer from an office printer to their home
printer the issue becomes apparent.

This happens for any user account, but because only one user has a home
office only she is affected. The other terminal server clients are
thinclients located in the office.

The admin account works fine.
The printer is a network printer, connected through a hardware VPN tunnel
and is set up like a local printer on the Terminal Server machine.

So in my case I was able to just set the Brother printer in the remote home
office as the default for the one user, as nobody else needs to print to that
printer.

Hence it isn't really a solution, but it does work and has fixed this
particular issue.

I would love to get a permanent solution, I'm betting it's only a matter of
time before another user sets up a home office...

"Edwin" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> At your place only one user is having this situation?
> Here all users have problems with connecting the printqueues. Only when an
> administrator account for that terminal server has connected the same
> printers the users should connect, then users will smoothly login (with all
> printerconnections).
> Thought you had the same but I guess I was wrong.
>
> Thanks anyway. Or got a solution for this 'new problem'?
> Greetings,
> Edwin
>
> "Joe from NZ" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > Hi Edwin,
> >
> > I managed to get around this issue by making the printer the default for the
> > user affected by this.
> > It isn't so much a solution but rather a patch, and this user hasn't had any
> > issues. They can easily change the default to a 'local' office printer when
> > they are in the office, but when they are home they can just click print, and
> > it works perfectly.
> >
> > Hope this helps you.
> >
> > "Edwin" wrote:
> > <!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > Did you find any solution? I am also having this problem.
> > >
> > > "Joe from NZ" wrote:
> > >
> > > > Hi,
> > > > Thanks for your reply.
> > > > We are already using the WHQL driver. I downloaded and installed this last
> > > > week.
> > > > (I'm not a fan of installing "full driver packages" on servers if I can
> > > > avoid it!)
> > > >
> > > > The client affected by this tells me this issue only started maybe a month
> > > > ago - before this everything was fine. Unfortunately nobody seems to be able
> > > > to pinpoint the exact day, or what has changed.
> > > >
> > > > It has to be some sort of permission issue (registry even) because it is
> > > > fine when I log in as admin, although even elevating the user to domain admin
> > > > (gone as far as setting the default group to this and removing domain users
> > > > in case it is a deny issue instead of an allow issue) does not get the user
> > > > working correctly.
> > > >
> > > > I'm heading out on-site later today to do some more testing. Any further
> > > > thoughts would be greatly appreciated!
> > > >
> > > > Cheers,
> > > >
> > > > Joe
> > > >
> > > >
> > > > "TP" wrote:
> > > >
> > > > > Hi Joe,
> > > > >
> > > > > Which driver are you using for the 5350DN on your TS?
> > > > >
> > > > > I recommend you use either the WHQL certified BR-Script
> > > > > driver or the WHQL certified Printer Driver, or if those
> > > > > are not suitable you could substitute a PCL driver that
> > > > > shipped with 2003. The "Full Driver & Software Package"
> > > > > appears to be too bloated at 125.94MB for a TS.
> > > > >
> > > > > Brother HL-5350DN 2003 driver downloads
> > > > >
> > > > >
> > > > >
> > > > > If you want to continue with the current driver you could
> > > > > use Process Monitor to narrow down any permission
> > > > > issues.
> > > > >
> > > > > Process Monitor
> > > > >
> > > > >
> > > > >
> > > > > Another thing to consider is to use TS printer autocreation
> > > > > instead of connecting to the user's printer through the VPN.
> > > > > My statements about driver versions still apply in this scenario.
> > > > >
> > > > > Thanks.
> > > > >
> > > > > -TP
> > > > >
> > > > > Joe from NZ wrote:
> > > > > > Hi guys,
> > > > > >
> > > > > > I'm really hoping someone can help me here;
> > > > > > We have a client running a Windows Server 2003 R2 SP2 Terminal
> > > > > > server, and remote printer selection runs terribly slow.
> > > > > >
> > > > > > One of the people connecting to this works from home, over a hardware
> > > > > > VPN (their edge firewall/router establishes this to the office
> > > > > > firewall/router). When they try to print a document (from anywhere -
> > > > > > Excel, Word, Moneyworks etc - the app doesn't seem to matter) the
> > > > > > printer selection freezes when they pick their printer.
> > > > > >
> > > > > > They can pick any printer in the head office (where the TS box is),
> > > > > > but when they select their own printer it freezes. This happens when
> > > > > > they connect from home, but also when they bring their laptop into
> > > > > > the office and try to pick their home printer.
> > > > > >
> > > > > > Their printer is a Brother HL-5350DN network printer, directly
> > > > > > attached to the network. From the TS server I can ping their printer,
> > > > > > and get around 10-15ms response times.
> > > > > >
> > > > > > Works fine for the admin login.
> > > > > >
> > > > > > So far I have tried deleting their profile, elevating their rights to
> > > > > > domain admin and re-loading the printer.
> > > > > > This issue isn't confined to just their login - I tried another TS
> > > > > > user, and got the same problem. Again, logging in as admin the
> > > > > > problem isn't there.
> > > > > >
> > > > > > Specs:
> > > > > > Server - dual Xeon E5405 CPU's, 4GB RAM, SAS RAID1 array, Server 2003
> > > > > > R2 SP2, Microsoft Office 2007 SP2.
> > > > > > Printer in question: Brother HL-5350DN
> > > > > >
> > > > > > Thanks in Advance,
> > > > > >
> > > > > > Joe
> > > > >
> > > > > <!--colorc--><!--/colorc--><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->