On Tue, 21 May 2013 14:59:27 +0100 steve-ALUG@hst.me.uk allegedly wrote:
I suspect it's after something else, like the DCOM port, or samba ports or something like that. I'll give that a try. But in the meantime, any suggestions for any good, simple to understand (use of and output of) traffic monitoring apps so I can see what the drive is trying to connect to? Wireshark comes to mind. Am I right?
Certainly. Or if running on a server, try tcpdump and then run the output file through wireshark.
But, there are a bunch of other tools I find useful when looking at traffic. Try iptraf, iftop and tcptrack (curses based so will run in a terminal window. Nethogs is good for seeing what is chewing up all your bandwidth and it is also useful because it aggregates traffic by program.
If you have an X display available then etherape is a good way to visualise connections (and can be a scary experience when running a browser).
Meanwhile, I'll have a think about your problems. My first reaction was that you /must/ have UPnP running on the router, but you say not.
Mick ---------------------------------------------------------------------
blog: baldric.net gpg fingerprint: FC23 3338 F664 5E66 876B 72C0 0A1F E60B 5BAD D312
---------------------------------------------------------------------