Default printer won't stay default

val · 16th April 2008

After installing a new printer onto our terminal servers our staff computers keep forgetting their default printer (it defaults to the wrong printer on another floor), this appears to happen only after they have been logged off overnight.

Is there a fix for this?

mflynn · 16th April 2008

Hi Val

Welcome to the BBS!

OK need more info.

1. Is this Terminal Server also a File server for a LAN?

2. If also a file server is the clients that lose the printer on the LAN. Or only losing it in the Terminal Service client logon?

Mike

val · 16th April 2008

No, our file server is separate. The problem only happens for our terminal server users logins.

mflynn · 16th April 2008

Okey dookie!

Next!

How is printer installed on the TS. To a LPT port, USB or TCPIP port.

What process do the users have to take after they loose the printer to get it back?

Mike

val · 16th April 2008

When they log on in the morning the printer has simply reverted to the wrong one, so what they have to do is set it to the correct default again. Not a huge thing to do, but doing it every day gets old fast.

The printers are are all installed via TCPIP ports.

mflynn · 16th April 2008

On the TS are both these printers installed in the printers folder?

If so is one of these printers set as default on the server itself?

If so is this the one that comes up s default fo the client.

If so set another printer as defaudt on the Server besides one of these and see if the defaults don't stick on the clients then!

Post back after you do this and I will anser tommorow as I am off to bed!

Good night.

Mike

val · 16th April 2008

"On the TS are both these printers installed in the printers folder?"

Yes, they are.

"If so is one of these printers set as default on the server itself?
If so is this the one that comes up s default fo the client."

On both our TSs the default printer was set to a printer other than one which is causing problems. I've set the default on both to the one that is desired by the clients that are experiencing the problem. I will know tomorrow whether this has made any difference.

Thank you for your help so far!

mflynn · 16th April 2008

Uhh!

Both "TSs"!?

I will dig all this out one way or another!

Tell me some details about your "2" terminal servers.

Are the 2 TS on the same subnet is one or more a DC, if on a DC then you best go thu the config?

Are you using the same Sharename for the printers.

Mike

**Scott Smith** · 16th April 2008

Just some random thoughts here.

How many TS clients are connecting to the T Server?

Do all the clients use different accounts?

Was OS are the clients using?
First thing I do On the client machines is in Windows explorer / Tools / Folder Options / view tab / and untick the very top box. "Automatically search for network folders and printers"
This little monster will make the desktop map to every share it finds and make a mess of the printer folder.

val · 18th April 2008

"How many TS clients are connecting to the T Server?"

There are about 70 client machines, probably about 50 will be used at any one time during the day, with load more or less balanced between the two terminal servers.

"Do all the clients use different accounts?"

We have 166 accounts in all, however not all of these use TS. The machines in question have one main user, but may occasionally be used by others as well.

"Are the 2 TS on the same subnet is one or more a DC, if on a DC then you best go thu the config?"

They are on the same subnet, but I'm sorry I don't know what a DC is?

"Was OS are the clients using?"

They are using a home-made Debian build which connects to our TSs.

"First thing I do On the client machines is in Windows explorer / Tools / Folder Options / view tab / and untick the very top box. "Automatically search for network folders and printers""

Thanks for the suggestion. I have done this with one of the affected machines, and will check back on Monday to see if this has corrected the problem.

"Are you using the same Sharename for the printers"

Yes, we are.

mflynn · 18th April 2008

I think Scott hit it!

Quote:

The machines in question have one main user,

If all users are using the same profile then if one of them changes the default printer then it will change it for all. If this change is made by one user it will not effect the other currently logged on users until they log off then back on.

I think it is a bad practice to do this and all should have seperate logons.

A test for this would be, one user to change the default printer then log off. Then back on and the default should still be as he set it. Then have a different user to log on, if off and check the default printer. Or log off someone that is on and back on.

Perhaps Scott has some thoughts!

Mike

PS DC=Domain Controller

**Scott Smith** · 19th April 2008

Quote:

They are using a home-made Debian build which connects to our TSs.

You lost me on that one.

mflynn · 22nd April 2008

Hi Val

What did you do to resolve this?

May be a help to others seeking help.

Mike

val · 23rd April 2008

Hi there,

Sorry for the erratic replies - I work part time.

I tried Scott's suggestion on one of the machines but it hasn't made a difference.

mflynn · 23rd April 2008

Windows is not doing this nor is some gremlin.

Someone TS user or LAN user is changing the default printer. Your job is to find out who and why?

What about the test I proposed in post #11.

Quote:

A test for this would be, one user to change the default printer then log off. Then back on and the default should still be as he set it. Then have a different user to log on, if off and check the default printer. Or log off someone that is on and back on.

Mike