R
rjcmi
I am still in the need for some assistance. I'd like to thank those
who replied to my previous entry. Here is what I'm trying to do, what
I've done so far, and some things that people have suggested.
I am an Americorp Volunteer working on a technology infrastructure
update for an Independent Living Center. This is my first experience
using Server 2003 and Terminal Server. I have implemented the
Terminal
Server and all appears to be working as planned with the exception of
the following.
We have 4 Satellite offices each one has their own Network Printer.
(Same Brand, Brother 2070n) These printers are assigned a static IP
address and are plugged directly into a router. Each client then
prints to that IP address. The problem I'm having is getting the
satellite offices to print directly to the printers in their own
offices while using TS. Currently they print out in the main office.
I have looked at the group and found the following MS Support Article
locacted here: http://support.microsoft.com/?kbid=302361 (Printers
That Use Ports
That Do Not Begin With COM, LPT, or USB Are Not Redirected in a
Remote
Desktop or Terminal Services Session) I have followed the directions
in the article.
I have also attempted to change the printer over to an LPT port.
I still can not get the local Network printer to show on the
Individual Clients in the Satellite Offices. They are using Windows
XP with all service packs installed.
In addition I was told the following:
The Brother 2070n driver is *not* a native driver on a Windows 2003
server. Whatever you do, don't install it on the TS, since most 3rd
party printer drivers are not TS-compatible, and some are known to
crash your printer spooler or the whole server. In stead, map the
printer to a native driver by creating a custom ntprintsubs.inf
file, as described in KB article 239088.
http://support.microsoft.com/?kbid=239088
Check with Brother which one of the native drivers on Windows 2003
is most compatible with the 2070n printer.
I did verify prior to installing the Office Printer that the driver
was not TS compatible. I called Brother and discovered I needed to
use an HP driver.
I scanned the Event log and found no errors of 1111, 1105 or 1106. I
also used the scanning tool downloaded from Microsoft and it also
found no events of those number.
I'm not sure if I'm missing a concept or I've configured it
incorrectly, so I should explain what I've done so far to make sure
I've done it correctly. Currently I do not have the Print Server
Role
installed. I just added the local printer on the main office network
though Control Panel Add Printer.
Do I need to install another driver for the satellite offices
redirection? I'm a bit confused. I was under the impression that on
the remote clients the attached printer had it's driver located on
the
client not the server. If that assumption is incorrect, do I need to
reconfigure how I've set up printing.
If creating a VPN is truly the easy solution I will look deeper into
what I need to do so.
Today I attempted to add the printers manually and that did not work.
I also tried to change the port to an lpt port and that also failed.
Any additional assistance would be appreciated. I don't have a great
deal of experience with Server 2003, but I have been able to
understand/troubleshoot all roll-out problems except this one. It has
now become extremely time sensitive as everyone is moving over to the
Terminal Server in the next week.
who replied to my previous entry. Here is what I'm trying to do, what
I've done so far, and some things that people have suggested.
I am an Americorp Volunteer working on a technology infrastructure
update for an Independent Living Center. This is my first experience
using Server 2003 and Terminal Server. I have implemented the
Terminal
Server and all appears to be working as planned with the exception of
the following.
We have 4 Satellite offices each one has their own Network Printer.
(Same Brand, Brother 2070n) These printers are assigned a static IP
address and are plugged directly into a router. Each client then
prints to that IP address. The problem I'm having is getting the
satellite offices to print directly to the printers in their own
offices while using TS. Currently they print out in the main office.
I have looked at the group and found the following MS Support Article
locacted here: http://support.microsoft.com/?kbid=302361 (Printers
That Use Ports
That Do Not Begin With COM, LPT, or USB Are Not Redirected in a
Remote
Desktop or Terminal Services Session) I have followed the directions
in the article.
I have also attempted to change the printer over to an LPT port.
I still can not get the local Network printer to show on the
Individual Clients in the Satellite Offices. They are using Windows
XP with all service packs installed.
In addition I was told the following:
The Brother 2070n driver is *not* a native driver on a Windows 2003
server. Whatever you do, don't install it on the TS, since most 3rd
party printer drivers are not TS-compatible, and some are known to
crash your printer spooler or the whole server. In stead, map the
printer to a native driver by creating a custom ntprintsubs.inf
file, as described in KB article 239088.
http://support.microsoft.com/?kbid=239088
Check with Brother which one of the native drivers on Windows 2003
is most compatible with the 2070n printer.
I did verify prior to installing the Office Printer that the driver
was not TS compatible. I called Brother and discovered I needed to
use an HP driver.
I scanned the Event log and found no errors of 1111, 1105 or 1106. I
also used the scanning tool downloaded from Microsoft and it also
found no events of those number.
I'm not sure if I'm missing a concept or I've configured it
incorrectly, so I should explain what I've done so far to make sure
I've done it correctly. Currently I do not have the Print Server
Role
installed. I just added the local printer on the main office network
though Control Panel Add Printer.
Do I need to install another driver for the satellite offices
redirection? I'm a bit confused. I was under the impression that on
the remote clients the attached printer had it's driver located on
the
client not the server. If that assumption is incorrect, do I need to
reconfigure how I've set up printing.
If creating a VPN is truly the easy solution I will look deeper into
what I need to do so.
Today I attempted to add the printers manually and that did not work.
I also tried to change the port to an lpt port and that also failed.
Any additional assistance would be appreciated. I don't have a great
deal of experience with Server 2003, but I have been able to
understand/troubleshoot all roll-out problems except this one. It has
now become extremely time sensitive as everyone is moving over to the
Terminal Server in the next week.