Michael -
Does your firewall offer the ability to allow programs to access the
network? If so, you should be able to configure NPF to allow emacs
to access the net. With a decent firewall, you should be able to get
a report of what executable is trying to access the 'net when you print
from emacs (in your FW logs) and allow that executable access. If NPF
is slick enough, you can allow access to a specific IP, such as that
assigned to your printer/print server (depending on the config).
There are a variety of programs available from sysinternals.com
that you might try. For example, turn off the Norton firewall and
run TCPView. Then, print from emacs and watch for the name of the
executable that comes up when you print. That should help you narrow
down which executables are active when you're printing. You can use
ProcExp to view all fo the active processes, and their relationships
(e.g. child processes spawned by emacs for printing).
I don't know enough about how emacs prints to comment intelligently
on that specific topic. However, this is how I would go about trying
to identify what exactly is causing printing to be blocked under NPF.
Also, is the firewall on the server or on the client? This might
impact the process tree required to identify what's blocking your
print attempts.
Good luck,
Charley
--
Charles Hamilton, PhD EIT PGR and Lecturer
Department of Civil and Phone: 949.824.3752
Environmental Engineering FAX: 949.824.2117
University of California, Irvine Email: [EMAIL PROTECTED]
