Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Hi, We just installed terminal Server in windows 2003 at our corporate office. We have about 30 remote site will be using to connect to the terminal server. The users does not have any problem login and access the DATA. The problem is they have a printer that is assign static 192.X.X.X. and which they can't print local. So this mean do I have to assign external static IP on the remote site printer? What if our employee need to print from home and they just have a regular inkjet printer and how would they print to it? Is there a way to configure the setting so it can see local desktop? Thank, Timmy

If they're connecting to a terminal server, then the only configuration that matters is the terminal server's. (NOTE: NOT server. A Terminal server and a Server are two very different beasts.) If you can log onto the terminal server and print, so can everyone else, with the right permissions.
If they're trying to print something off their remote location, then they should enable Printers under the Local Resources tab.

Hi Razor, Thank for your respond. Actually we have a server and terminal server seperatly.
For the remote site don't have any servers. I want the users capable to access the data remotely when they login to terminal server.
So if remote site have local printer and they login to terminal server that is in corporate office, can they print locally?
Where can I enable Printer under the Local Resource tab? Are you referring in terminal setting? Thank, Timmy

It's a client-side setting. Not a server setting.
And yes, they'll be able to print locally. It'll show up as: <printer name> (from <client name> in Session <session number>).

Razor, it doesn't show my printer locally. The only option I see in terminal server is to add a printer. Any other suggestion? Thank,Tim

You're in the wrong place entirely.
It's a client side setting. As in not on the server. You know that dialog that comes up when you start Remote Desktop Connection? The one where you probably hit Connect without thinking? It's in that.

Thank Razor it work now :)
Hey do you know about login script?
Hi, is there a way to configure the login script in active directory in one place so I don't have to copy and pase login.bat in every users? We have total about 200 users and I don't want to copy and pase the login.bat in the profile setting in user accounts.
example:\\test1-documents
Everything is working fine but it would be nice if I can configure in one setting so it will apply to every users when they login.

I know how to do it for an AD logon, but I don't know if it's different for a Terminal Server logon. For a plain old AD logon, you stick your script in the PDC's NETLOGON share.

![]() |
ftp--my head hurts
|
Terminal Server- Login s...
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |