Printing to a TCP/IP printer

[Guest]

I have several computers at remote sites that connect to the terminal server
and are able to print fine to their local LPT1 printers. I now have a TCP/IP
printer at a new remote office. Could someone provide a bit of guidance as
to how I have to set up this printer on the server for it to map back to the
remote site when running in application mode. The remote site is using
Windows XP Professional. The printer is a Xerox M20i.

Thanks a bunch.

Bob

 

[Mike D]

E-mail me for possbile solution
Mike D

 

[Vera Noest [MVP]]

One way is to install the printer on the TS (thereby in effect
making the TS function as a PrintServer as well). If you have a
separate PrintServer, that would be even better.

Once the printer is reachable throughout the network, your clients
can connect to it on their XP clients, making it the default
printer. It will then automatically be redirected into their rdp
session

Or define this printer as the default printer for TS users in a
login script. You'll need some sort of utility to do this:
Defprint.exe controls local printers (local to the TS),
Con2prt.exe controls network printers, or use a KiXtart script.

Examples (check for correct syntax!)

if %Clientname% == CLIENT01 DefPrint.exe /d "HP OfficeJet"

if %clientname% == CLIENT01 con2prt.exe \\PrintServer\printer01

if %clientname% = "CLIENT01"
SetDefaultPrinter ("\\TS\printer01")
endif

Defprint.exe can be downloaded here:
http://www.dcug.de/phpnuke/html/modules.php?
name=Downloads&d_op=MostPopular

con2prt.exe is part of the NT Resource Kit.
KiXtart can be downloaded from http://www.kixtart.org

 

[Guest]

Mike, thanks for reply, and for the offer to accept eMail. Unfortunately,
the eMail address linked to didn't work. So here is the whole situation here:

The situation I have is a Windows XP Pro system connecting to a Windows 2000
Terminal Server. The terminal server is behind a Symantec firewall. The
remote desktop is behind a DSL router with NAT. The local printer for the
desktop is a Xerox M20i connected via Ethernet. When the remote office logs
into the main server, it firsts sets up a VPN with the Symantec firewall.
Then it uses RDP to establish the Terminal Server connection.

The local IP addresses on the home office network are 192.169.0.xx. The
local IP addresses at the remote site are 192.168.3.xx (the printer being
192.168.3.5).

What I tried was installing the printer on the terminal server (even though
it wasn’t there) with a TCP port address of 192.160.3.5 (even though that is
not a valid address on the local network at the home office but is the way
it is installed at the remote office). But when I connect and try to print
back to the local printer, nothing comes back, or if it does it never makes
it to the printer.

Have I done something wrong in how I set the printer up on the server; or is
the VPN preventing the printer output from getting from the computer to the
printer; or is there still something additional I need to do in the setup
like mapping the printer to a printer port like lpt1:.

Again, thanks for the help.

Bob Showalter, Packer International
(e-mail address removed)

 

[Guest]

Vera,

Thanks for the reply. I have a couple of questions about what you wrote.
You can see my reply to Mike D for complete details about the set up, but
basically, the IP address scheme for the home office local network (behind
the firewall) is 192.168.0.xxx, and the IP address scheme at the remote site,
behind their DSL router/firewall is 192.168.3.xxx. So, I am not sure:

1. How to set the printer up at the Terminal Server end. The Xerox tech
that delivered the printer installed it (the driver & software) as though the
printer were actually there at the Terminal Server, but with an IP address
matching the scheme for the remote office.

2. If the VPN that is established before logging into the terminal server
is keeping the computer from senting stuff out to other IP's at the remote
site.

The client logon scripts need to be flexible enough for the to log on at the
remote site, or to a local workstation at the home office.

Thanks again for your reply.

Bob Showalter, Packer International
(e-mail address removed)

 

[Vera Noest [MVP]]

I would suggest a different approach:

The remote Windows XP client can print to this printer, correct?
Assuming it can, the printer is defined on the XP client in the
users profile as a (local) network printer.

If you then start a rdp session from the XP client to the Terminal
Server, why is the printer not autocreated in the users session?
It should be, assuming that you have configured rdp to
autoredirect client printers. Also make sure that you run at least
rdp 5.2 on the client (which supports redirection of network
printers).

Have you checked the EventLog on the TS? Maybe the only thing you
have to fix is to map the printer driver to a native driver on the
server.

239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

 

[Mike D]

Also if you install the printer on a print server (therefore making it a
network printer) after you log into the TS just go to start > settings>
printers > add printer and browse to the printer then install it. You might
need local admin privliges to do so too.
Mike D

 

[Guest]

Thanks again for the help. Turns out that the only thing needed was the
update to RDP 5.2. The strange thing is the way Microsoft has that update
install. Instead of replacing the RDP at the OS level, it installs it as a
program so that if you just try to use the old link, it still comes up
5.1.xxx. That was a bit puzzling at first. But once I realized that to get
to the new version I had to run it as its own program rather than a
"system/communications" program, the new version came up and the printer
mapped just fine.

Thanks to both of you and Mike for your responses.

Bob Showalter