<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Network-Printer on BAFM</title><link>https://christian.blog.pakiheim.de/tags/network-printer/</link><description>Recent content in Network-Printer on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Sun, 04 Nov 2007 14:08:05 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/network-printer/index.xml" rel="self" type="application/rss+xml"/><item><title>Windows terminal services undamp; network printers</title><link>https://christian.blog.pakiheim.de/posts/2007-11-04_windows-terminal-services-amp-network-printers/</link><pubDate>Sun, 04 Nov 2007 14:08:05 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/2007/10/30/windows-terminal-services-network-printers/</guid><description>&lt;p&gt;Yes, yes. I do list a lot of crappy products (go on, laugh; I don&amp;rsquo;t really care). Yesterday I had quite a struggle with Microsoft Windows Server 2003 and Terminal services (or more precisely with their way on how to deal with network printers).&lt;/p&gt;
&lt;p&gt;As most of you know, there a two (possibly three) different ways on how to do network printers.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;would be, to simply share a local connected printer by simply creating a share for the printer&lt;/li&gt;
&lt;li&gt;buy a smart printer with integrated print server&lt;/li&gt;
&lt;li&gt;a combination of 1. and 2.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;We luckily enough do have printers with integrated print servers, so that wouldn&amp;rsquo;t be a problem. &lt;em&gt;&lt;strong&gt;But&lt;/strong&gt;&lt;/em&gt; you get a problem if you&amp;rsquo;re trying to monitor the printer queue if you simply create a new TCP/IP connection from another target. You simply can&amp;rsquo;t tell who&amp;rsquo;s printing what.&lt;/p&gt;</description></item></channel></rss>