As more and more people want to access their data over the web, desktop application programmers such as us have to come up with ways for them to access their data.
I have been using Microsoft Terminal Server since it was an addon to NT4. Terminal Server has built in security and is VERY easy to use and administer. You do have to purchase TS CALS which can cost $100 per seat, but it is well worth it.
If the remote user prints to a network printer, most users are forced to use CITRIX to add this capability. If all you need is to print over a network, CITRIX is unnecessary.
To tell you the truth, I don't remember if I figured it out or if I found the answer online, but I will take credit for the solution.
HERE IT IS:
Most network printer manufacturers have their own network client for the printer port. What you need to do is create a TCP/IP port. Let's say you have a Ricoh MFP printer. Ricoh uses what they call a smartdevicemonitor to create the printer port. If the printer is using the IP: 192.168.1.245, you create the TCP/IP port with that address. For the name of the port, Windows adds an "IP_" to the address for the port name. Change the name to "LPTB". Windows only allows Terminal Services to print to LPT or USB ports. If you call the port "LPTB" (you can use any letter or # for the last character", Terminal Services thinks it is a local port.
For all of you that are using CITRIX to print to a network printer, you no longer have to. Hope this helps!
I have been using Microsoft Terminal Server since it was an addon to NT4. Terminal Server has built in security and is VERY easy to use and administer. You do have to purchase TS CALS which can cost $100 per seat, but it is well worth it.
If the remote user prints to a network printer, most users are forced to use CITRIX to add this capability. If all you need is to print over a network, CITRIX is unnecessary.
To tell you the truth, I don't remember if I figured it out or if I found the answer online, but I will take credit for the solution.
HERE IT IS:
Most network printer manufacturers have their own network client for the printer port. What you need to do is create a TCP/IP port. Let's say you have a Ricoh MFP printer. Ricoh uses what they call a smartdevicemonitor to create the printer port. If the printer is using the IP: 192.168.1.245, you create the TCP/IP port with that address. For the name of the port, Windows adds an "IP_" to the address for the port name. Change the name to "LPTB". Windows only allows Terminal Services to print to LPT or USB ports. If you call the port "LPTB" (you can use any letter or # for the last character", Terminal Services thinks it is a local port.
For all of you that are using CITRIX to print to a network printer, you no longer have to. Hope this helps!
