J
Jeff Gerace
I am struggling with a problem, need some assistance. I
have a W2k Server running terminal server in application
mode. I have several W2k Pro clients that connect
terminal sessions, but they all need to print locally (in
another office). I have muddled my way through the
documentation on printing, and these are the three
scenarios I have working (sometimes):
1. I have a locally connected printer (LPT port via
parallel cable), which will create a virtual printer on
the term server and default to it based on the checkbox in
AD on the term server to default to the client printer.
This one always works
2. I create a local printer (usb printer connected
locally), and share it out locally. When I login to the
terminal server, I create a new printer there and select
the TSXXX session with my PC, and share IT out opn the
server, therefore maintaining that connection each time I
login.
3. I have a network printer with a jetdirect card. I
create a local TCP/IP port, and share it out. Then run
a "net use lpt1 \\mypc\myshare" through the local logon
script. I then create a local LPT1 printer (which works
because I have done a virtual LPT mapping) and share IT
out as well. Now when I login to the terminal server, I
can see my printer created on the terminal server (for 1
user).
Here is the problem...I duplicated the #3 scenario on a
separate PC printing to the same jetdirect based printer
that previously worked. I setup the printer exactly as
the PC that worked, but no printer shows up on the
terminal server. They are both the same OS, both have
local administrative rights, both have equal permissions
on the terminal server. I cannot find a single difference
between the two users, but one works and one does not.
Can somebody please help me determine which is the best
way to have a single printer in one office (with a
jetdirect card attached) , and be able to all login with
separate credentials to a terminal server and have access
back to that local printer. All users are in the office
with the local printer, and they all are running W2k Pro.
This is a frustrating problem, and I do not want to create
permanent printers for everybody (scenario #2 above). I
would like to be able to have the printer create itself
when they login, and be gone when they logoff.
Any help would be appreciated. Please reply directly to
my e-mail address with any suggestions. Thanks.
have a W2k Server running terminal server in application
mode. I have several W2k Pro clients that connect
terminal sessions, but they all need to print locally (in
another office). I have muddled my way through the
documentation on printing, and these are the three
scenarios I have working (sometimes):
1. I have a locally connected printer (LPT port via
parallel cable), which will create a virtual printer on
the term server and default to it based on the checkbox in
AD on the term server to default to the client printer.
This one always works
2. I create a local printer (usb printer connected
locally), and share it out locally. When I login to the
terminal server, I create a new printer there and select
the TSXXX session with my PC, and share IT out opn the
server, therefore maintaining that connection each time I
login.
3. I have a network printer with a jetdirect card. I
create a local TCP/IP port, and share it out. Then run
a "net use lpt1 \\mypc\myshare" through the local logon
script. I then create a local LPT1 printer (which works
because I have done a virtual LPT mapping) and share IT
out as well. Now when I login to the terminal server, I
can see my printer created on the terminal server (for 1
user).
Here is the problem...I duplicated the #3 scenario on a
separate PC printing to the same jetdirect based printer
that previously worked. I setup the printer exactly as
the PC that worked, but no printer shows up on the
terminal server. They are both the same OS, both have
local administrative rights, both have equal permissions
on the terminal server. I cannot find a single difference
between the two users, but one works and one does not.
Can somebody please help me determine which is the best
way to have a single printer in one office (with a
jetdirect card attached) , and be able to all login with
separate credentials to a terminal server and have access
back to that local printer. All users are in the office
with the local printer, and they all are running W2k Pro.
This is a frustrating problem, and I do not want to create
permanent printers for everybody (scenario #2 above). I
would like to be able to have the printer create itself
when they login, and be gone when they logoff.
Any help would be appreciated. Please reply directly to
my e-mail address with any suggestions. Thanks.