From: Dale Shaw (dale.shaw@gmail.com)
Date: Fri Apr 11 2008 - 20:42:58 ART
Hi,
On Sat, Apr 12, 2008 at 4:26 AM, groupstudy email <groupstudy@gmail.com> wrote:
> Does anyone know what the heck this port is for???
>
> I can't find anything at all on this. All searches tell me this is for
> something called "natuslink".
Do you have access to either endpoints? (src or dst IP)
If so, capture some traffic, figure out which end is the client and
which end is the server, then access one or both and use a host-level
tool to map TCP ports to process IDs.
I use "netstat -ona" on Windows-based systems frequently to grab the
process ID (PID) of a listening port. There are one or two
SysInternals tools that do it for you too.
On *NIX-like/based systems, there are heaps of different ways to do it.
Looking at a packet capture (can be tedious) or investigating at the
endpoints can sometimes be the only way to figure out exactly what the
traffic is -- tcp/2895 could be HTTP for all you know.
cheers,
Dale
Pass the CCIE in six weeks, Guaranteed!
http://www.certscience.com/CCIE
This archive was generated by hypermail 2.1.4 : Thu May 01 2008 - 08:25:50 ART