Re: RDP and pcAnywhere

You can clear the spooler queue with this batch file:
@echo off
net stop Spooler
ping localhost -n 4 > nul
del /q %SystemRoot%\system32\spool\printers\*.*
net start Spooler

A more elegant method would be to use Remote Desktop to start or shadow a
"Console Session" - see here: http://support.microsoft.com/kb/278845/.

"SP_1" <none@xxxxxxx> wrote in message
news:OmBwm$l2JHA.1380@xxxxxxxxxxxxxxxxxxxxxxx
I agreed, and that would make my day, too.

Unfortunately with servers (at least in our case), sometimes pcAnywhere
works better than RDP. Here is an example, and I haven't yet found a
solution for it.

Say, a shared printer (an HP4200 with its own NIC) somehow lost connection
to the network (perhaps because it was turned off overnight). In the
morning, people sent printjobs to the printer without first turning it on.
This caused the server to pop the below message at the display of the
server (not at the workstations').

"The print spooler was unable to connect to your printer. This can be
caused by your printer being turned off, the cable being unplugged, or
being connected to a VPN, which will block your access to your local
network."

"Your document will print when the printer becomes available." (OK
button)

At this point, someone had to click the OK button on that message at the
server to clear it; otherwise, the above message would just stay there
forever, and nobody could print - even if the printer was now turned on.
There are only 2 options as far as I know. One is to physically be at the
server, and the other is to use pcAnywhere. If I used RDP, I would not
see the spooler message, so I couldn't clear it. If I use pcAnywhere, I
can see the message.

Here is another kicker. So, as I'm offsite, I would RDP into the server,
and then I started a pcAnywhere remote session to the same server itself.
That's how I got to the spooler message and cleared it.

So, that's my experience with RDP vs. pcAnywhere. Let me know if there is
something I can do so that I don't have to rely on pcAnywhere.

Thanks
Steve

"Pegasus [MVP]" <news@xxxxxxxxxxxxx> wrote in message
news:ey2mjWl2JHA.1092@xxxxxxxxxxxxxxxxxxxxxxx

"SP_1" <none@xxxxxxx> wrote in message
news:O90z5Rl2JHA.1096@xxxxxxxxxxxxxxxxxxxxxxx
Hi

For quite a while now (couple years perhaps), I was able to use RDP and
pcAnywhere together on our Windows Server 2003 Std. For the longest
time, I would RDP from other remote locations in to the server and
subsequently run pcAnywhere to connect to other servers/workstations
(when needed). Back then, at the very beginning, I was surprised that
both can work that way as I was aware about the awgina.dll and
msgina.dll issues.

Recently, our server crashed, and it had to be rebuilt and restored,
etc. In the process, I cannot get both RDP and pcAnywhere to operate
like before. In other words, I cannot initiate an RDP connection first
to the server. I can only connect to the server if I have pcAnywhere
installed on my workstation (or wherever I'm from the remote location).
After that, I can use RDP from the server to connect to other servers.
The down side is that I would need pcAnywhere software, which is not as
readily available as the built-in RDP counterpart. Plus, pcAnywhere
(v10) is a lot slower comparing to using RDP in our situation.

Does anyone know how to get this to work again ? Or, was it a quirk
that I happened to come across just for one time ?

Thanks
Steve

Wouldn't it be simpler to use Remote Desktop for all remote sessions?


You can clear the spooler queue with this batch file:
@echo off
net stop Spooler
ping localhost -n 4 > nul
del /q %SystemRoot%\system32\spool\printers\*.*
net start Spooler

A more elegant method would be to use Remote Desktop to start or shadow a
"Console Session" - see here: http://support.microsoft.com/kb/278845/.


.