J
Justin
We have a 2000 server in one location with 3 local clients connected
direct. In another physical location we have a small LAN, and each
computer individually connects to the server (running MAS90) via
MSTSC.
We all use the MAS90 software, and we need everyone to be able to
print to any printer (regardless of whether or not they are local or
remote). We have a high-speed printer in the satellite office (Minolta
Di470). It is nescessary for management in the main office to be able
to print to the Minolta Di470.
I'm the IT guy responsible to insuring everything works. When I
initially set everything up I had to write some DOS script (can't
recall exactly what it was), but basically it redirected the local
192. TCP/IP address of the satellite office printer, to the local LPT1
of a client in the satellite office. As long as that client was
connected to the server in the main office, everyone was able to print
to the satellite office printer.
This configuration has been working for almost a year, but now after a
few more people being added to the ACL for the server, we are starting
to experience intermittent (but on a regular basis) issues with the
satellite office printer.
As more people sign on the server, mapping their local printers to the
server, it almost seems to be bumping the high-speed printer off the
server. There are now around 30-40 "Inactive TS Ports" listed under
available ports, and I can't seem to delete them. There are also hung
TS ports for users who arn't signed on, but the port still exists (ie.
\\JOHNDOE\Canon BubleJet PRN1), these won't delete as administrator
from the server either. Now, occasionally the satellite office will
sign on the server, but that clients local printer will no longer
redirect to the server. In other words, the high-speed printer doesn't
even show up in the list, and there is no TS**** port with the Minolta
printer listed, despite printer sharing being enabled in the MSTSC
client.
I've looked up some stuff on Google, some similar posts suggested
modifications to some .inf files (ntprint.inf, etc), but these are for
people who never got the printer working in the first place. Another
post suggested upgrading the RDP package from version 5 to verstion
5.*.*.* (Microsoft doesn't seem to have any updates on their site)?
Also we have always installed all updates, SP's, and patches.
Does anyone have any suggestions on what could be causing this
problem? Even better yet, if anyone has a suggestion on a better way
to setup this remote printer (w/ out needing a client)? It does have a
network card (the minolta printer). It's currently set to
192.168.0.100, but we dont' use it as a TCP/IP printer, it's still
remapped as an LPT for all the clients. Due to the size of our MAS90
database, setting up a real virtual private network bridging the
main-office and sattellite office (which really makes the most sense
for our purposes) is impossible, as MAS90 has poor support for VPN's,
and would transfer the entire database to the clients, which would
result in unacceptable performance.
Thanks,
Justin
direct. In another physical location we have a small LAN, and each
computer individually connects to the server (running MAS90) via
MSTSC.
We all use the MAS90 software, and we need everyone to be able to
print to any printer (regardless of whether or not they are local or
remote). We have a high-speed printer in the satellite office (Minolta
Di470). It is nescessary for management in the main office to be able
to print to the Minolta Di470.
I'm the IT guy responsible to insuring everything works. When I
initially set everything up I had to write some DOS script (can't
recall exactly what it was), but basically it redirected the local
192. TCP/IP address of the satellite office printer, to the local LPT1
of a client in the satellite office. As long as that client was
connected to the server in the main office, everyone was able to print
to the satellite office printer.
This configuration has been working for almost a year, but now after a
few more people being added to the ACL for the server, we are starting
to experience intermittent (but on a regular basis) issues with the
satellite office printer.
As more people sign on the server, mapping their local printers to the
server, it almost seems to be bumping the high-speed printer off the
server. There are now around 30-40 "Inactive TS Ports" listed under
available ports, and I can't seem to delete them. There are also hung
TS ports for users who arn't signed on, but the port still exists (ie.
\\JOHNDOE\Canon BubleJet PRN1), these won't delete as administrator
from the server either. Now, occasionally the satellite office will
sign on the server, but that clients local printer will no longer
redirect to the server. In other words, the high-speed printer doesn't
even show up in the list, and there is no TS**** port with the Minolta
printer listed, despite printer sharing being enabled in the MSTSC
client.
I've looked up some stuff on Google, some similar posts suggested
modifications to some .inf files (ntprint.inf, etc), but these are for
people who never got the printer working in the first place. Another
post suggested upgrading the RDP package from version 5 to verstion
5.*.*.* (Microsoft doesn't seem to have any updates on their site)?
Also we have always installed all updates, SP's, and patches.
Does anyone have any suggestions on what could be causing this
problem? Even better yet, if anyone has a suggestion on a better way
to setup this remote printer (w/ out needing a client)? It does have a
network card (the minolta printer). It's currently set to
192.168.0.100, but we dont' use it as a TCP/IP printer, it's still
remapped as an LPT for all the clients. Due to the size of our MAS90
database, setting up a real virtual private network bridging the
main-office and sattellite office (which really makes the most sense
for our purposes) is impossible, as MAS90 has poor support for VPN's,
and would transfer the entire database to the clients, which would
result in unacceptable performance.
Thanks,
Justin