RDP into Server 2003 - No session printers unless PC is joined to the domain

[mikeasa]

When I RDP into computers running Server 2003 (Domain controllers and member servers) using a computer that is NOT joined to the domain that the server is part of, none of my local printers show up as session printers.

After I have joined my PC to the domain that the Server 2003 computer is part of, my local printers show up as session printers when I RDP into the computers.

I have an outside user that is joined to a Workgroup and does not wish to join the domain, but still wants his local printers to show up as session printers when he RDP's into the server. I have spent hours scouring Google and looking through the Group Policy Object Editor for the server and for the domain. I have not found anything that helps me.

If you can spare a minute, please let me know how to do this!

Thanks.

 

[Allanv]

well thats weird as i do this all the time, but there is a issue with non standard ports and printers.

IE if the printer on the local machine isnt installed on say lpt1 or usb001 something like that anyways.

and thats just a reg fix on the local pc

But thats the only issue i have ever had and i rdp into servers 2k and 2k3 from home (remote Support) and i am not joined to any domain.

 

[mikeasa]

And your local printers become session printers for you on the 2003 servers?

I have tried this with several different 2003 servers at totally different customers, all with default "out of the box" Microsoft settings (at least as far as I know) and I have never gotten my local printers to be setup as "session printers" within my RDP session unless my PC was joined to their domain. The same servers that do not work when I am not joined to the domain, do give me session printers when I am joined. Also, many (if not all, I don't remember for sure) of these servers are not setup for Application Terminal Services. I am just RDP'ing in for tech support/administrative purposes. Would that make the difference do you think?

As far as non-standard ports and printers, I am using standard printers that have drivers in Windows and are setup on LPT1, so I don't think that is an issue.

 

[Allanv]

i do the same as you no term services just rdp for remote tech support and yes all my printers follow me

like i said the only issue i get is with my or indeed any printer is if its using the non standard port.

so you tick the printers follow me in the rdp client and it doesnt work unless joined to the domain right ?

 

[mikeasa]

Correct. Everything is set correctly in the user's properties for the session printers to be created and it works fine if the PC that the user connects from is connected to the domain. If that same user, that just got a session printer, when connecting from a PC that is joined to the domain, connects from a PC that is not on the domain, the user does not get session printers.

I am convinced that this is some sort of setting (security?) on the server or on the domain. I just do not know what the setting is.

 

[Allanv]

look in AD and the users profile look in enviroment see if printer etc are ticked.

 

[mikeasa]

Yes, all of the options in the "client devices" section of the Environment tab of the user's properties are checked.

 

[Allanv]

and the XP clients are all SP2 as well correct?

 

[mikeasa]

That is correct. The clients are Windows XP SP2.

 

[Allanv]

i have never seen the behavoiur your getting, but i will test it again tonight.

my not on the domain although it has its workgroup renamed to something i like.

the 4 servers i can test 3 on the same domain 1 not the same domain.

Will let you know how i get on, also i can rdp from this box i am on in work and connect to another domain one of the ones listed above and not in anyway part shape or form of this domain and i get the printers from here.

Will let you know how i get on

 

[mikeasa]

OK. Thank you very much for your time. Do you think it is a setting that is different on the servers you are connecting to than the server that I am connecting to?

 

[mikeasa]

Well, we have not had success with every printer that we have tried yet, but on some, simply sharing the printer and making sure that the permissions were set to allow the remote server to access the printers fixed the problem. The were setup as session printers, without sharing them, if the computer that I RDP'd from was on the same domain as the server.

Thank you very much for your help!