Prev: Unable to view all photos on network pc
Next: one way ping and networking problem
From: Linn Kubler on 22 Apr 2008 14:07
Hi,

We are running a Windows network, 2003 Server Domain and Windows XP
workstations. I'm having trouble with a printer and a specific application
and I feel that if I can see what's getting sent to the printer then I might
be able to solve this issue. Or at least get the right vendor, software or
printer, to take a closer look at the issue.

I've been searching for packet sniffers and there are just so many that I
don't know how to choose one. Is there a favorite out there? Something
open source or free would be best for the budget of course. I went to
source forge and it seems everything there is designed for Linux, not sure I
want to hassle with setting up a Linux box right now, so something that runs
on Windows would be nice. Any suggestions?

Also, if anyone has an idea of how I could trap the print job before it gets
to the print queue on the workstation that would be helpful.

Thanks in advance,
Linn


From: smlunatick on 22 Apr 2008 15:18
Wireshark appears to be an open-source sniffer but it also requires a network
hub.

On 22/04/2008 "Linn Kubler" <lkubler(a)chartwellwisc2.com> wrote:
>Hi,
>
>We are running a Windows network, 2003 Server Domain and Windows XP
>workstations. I'm having trouble with a printer and a specific application
>and I feel that if I can see what's getting sent to the printer then I might
>be able to solve this issue. Or at least get the right vendor, software or
>printer, to take a closer look at the issue.
>
>I've been searching for packet sniffers and there are just so many that I
>don't know how to choose one. Is there a favorite out there? Something
>open source or free would be best for the budget of course. I went to
>source forge and it seems everything there is designed for Linux, not sure I
>want to hassle with setting up a Linux box right now, so something that runs
>on Windows would be nice. Any suggestions?
>
>Also, if anyone has an idea of how I could trap the print job before it gets
>to the print queue on the workstation that would be helpful.
>
>Thanks in advance,
>Linn
>
>
From: Jack (MVP-Networking). on 22 Apr 2008 18:10
Hi
May be this can Help,
http://www.windowsnetworking.com/nt/atips/atips338.shtml
Jack (MVP-Networking).

"Linn Kubler" <lkubler(a)chartwellwisc2.com> wrote in message
news:u$yS1OKpIHA.1420(a)TK2MSFTNGP03.phx.gbl...
> Hi,
>
> We are running a Windows network, 2003 Server Domain and Windows XP
> workstations. I'm having trouble with a printer and a specific
> application and I feel that if I can see what's getting sent to the
> printer then I might be able to solve this issue. Or at least get the
> right vendor, software or printer, to take a closer look at the issue.
>
> I've been searching for packet sniffers and there are just so many that I
> don't know how to choose one. Is there a favorite out there? Something
> open source or free would be best for the budget of course. I went to
> source forge and it seems everything there is designed for Linux, not sure
> I want to hassle with setting up a Linux box right now, so something that
> runs on Windows would be nice. Any suggestions?
>
> Also, if anyone has an idea of how I could trap the print job before it
> gets to the print queue on the workstation that would be helpful.
>
> Thanks in advance,
> Linn
>
>

From: Robert Moir on 26 Apr 2008 14:41
smlunatick wrote:
> Wireshark appears to be an open-source sniffer but it also requires a
> network hub.

Wireshark is awesome, and I'm honestly shocked at how the OP could
"research" open source packet sniffers and miss it, because has a massive
reputation. As for needing a hub, any packet sniffer will either need a hub,
a switch that echoes traffic to the port it's plugged into, distributed
agents or some other similar trick, they can only 'sniff' what they see
going past them, after all.


From: smlunatick on 27 Apr 2008 20:56
On Apr 26, 2:41 pm, "Robert Moir" <usenet+robspamt...(a)gmail.com>
wrote:
> smlunatick wrote:
> > Wireshark appears to be an open-source sniffer but it also requires a
> > network hub.
>
> Wireshark is awesome, and I'm honestly shocked at how the OP could
> "research" open source packet sniffers and miss it, because has a massive
> reputation. As for needing a hub, any packet sniffer will either need a hub,
> a switch that echoes traffic to the port it's plugged into, distributed
> agents or some other similar trick, they can only 'sniff' what they see
> going past them, after all.

Try finding a new "hub." There are getting to be "rare."
 |  Next  |  Last
Pages: 1 2
Prev: Unable to view all photos on network pc
Next: one way ping and networking problem