Pmagistra
asked on
Terminal server Client doesn't see local printer
I got a terminal server with a remote client. If I log in via the internet with MSTC/console I have two situations:
1) If I log in on the remote PC as administrator (same log as the admin on the tem.server), and then start mstc/console as administrator everything works fine.
2) If I log in on the remote PC as "peter" ( who is made administrator local and on the terminal server as well) and start mstc/console and login in as administrator or Peter (no difference) I CANNOT GET MY LOCAL PRINTER CONNECTED.
I am getting crazy.
1) If I log in on the remote PC as administrator (same log as the admin on the tem.server), and then start mstc/console as administrator everything works fine.
2) If I log in on the remote PC as "peter" ( who is made administrator local and on the terminal server as well) and start mstc/console and login in as administrator or Peter (no difference) I CANNOT GET MY LOCAL PRINTER CONNECTED.
I am getting crazy.
ASKER
In situation 1. I can see on the terminal server at "Printers and faxes", brother at PCname in sessie 1. PCname is the name of my local PC at home. To get this I have to login on home PC with the administrator account from the terminal server.
Are these local users or domain users? If these are local users you need to make sure your passwords are the same.
ASKER
Thx guys, I found out that the registry change (below) mentioned elsewhere on expert exchange that SHOULD make your local printer work is doing the opposite. DONT USE THIS UNLESS NO OTHER OPTIONS ARE AVAILABLE. In my case the situation became worse!!
1.
Click Start, click Run, type regedit, and then click OK.
2.
Locate and then click the following key in the registry:
HKEY_CURRENT_USER\Software
3.
On the Edit menu, point to New, and then click DWORD Value.
4.
Type FilterQueueType, and then press ENTER.
5.
On the Edit menu, click Modify.
6.
Type FFFFFFFF, and then click OK.
1.
Click Start, click Run, type regedit, and then click OK.
2.
Locate and then click the following key in the registry:
HKEY_CURRENT_USER\Software
3.
On the Edit menu, point to New, and then click DWORD Value.
4.
Type FilterQueueType, and then press ENTER.
5.
On the Edit menu, click Modify.
6.
Type FFFFFFFF, and then click OK.
That instruction is only if your printer is using a DOT4 port, per this MS KB http://support.microsoft.com/kb/302361/EN-US/. If your printer isn't using a DOT4 port (HP PSC's use these) then remove that key that you added.
What it sounds like to me is a Firewall issue... while logged in as Peter, open the Windows Firewall settings and make sure that File and Print Sharing is enabled.
You could also create a NEW user and add them to the administrator's group and then see if that user can connect. It's definitely a problem with your local computer and not the Terminal Server because the TS doesn't care about the user account on a remote machine unless that remote machine is part of the same domain structure.
Jeff
TechSoEasy
What it sounds like to me is a Firewall issue... while logged in as Peter, open the Windows Firewall settings and make sure that File and Print Sharing is enabled.
You could also create a NEW user and add them to the administrator's group and then see if that user can connect. It's definitely a problem with your local computer and not the Terminal Server because the TS doesn't care about the user account on a remote machine unless that remote machine is part of the same domain structure.
Jeff
TechSoEasy
ASKER
It had to do with the printer type. Some printers (older) don't work well with TS. Solution was to connect this printer with the serial cable and not with the USB. Worked immediately.
Changed recommendation: PAQ and points refunded
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
How are checking the printer....did you try logging onto Terminal server using a client machine ?