TCP Traceroute utility for windows?

Ali195 · 22 Jul 2012 at 01:44

Been messing with a Cisco firewall i found at work. Never played with one before so find it quite interesting.

I want to run a TCP/I.P traceroute not IMCP but cannot find any working utilities online.

I'ved allowed IMCP & UDP traffic on the firewall (the application we use sends an initial UDP packet to our data centre in NY requesting a TCP/I.P address for one of the gateway servers in said data centre).

I.P traffic is allowed by default on the firewall but i have not allowed TCP so the application will not connect, which is fine. I noticed our application can trace to the data centre yet not connect but realised the trace uses IMCP.

I want to do a TCP/IP trace, with the idea being it will fail & thus prove TCP traffic is being blocked without viewing the Cisco log/utility.

Maybe i'm looking too much into this but as i'm new to this kind of jizz, its been bugging me, forgive my ignorance

Nunzio · 22 Jul 2012 at 02:52

Ermm.. try tcptraceroute

Or http://www.elifulkerson.com/projects/tcping.php

Weazle · 22 Jul 2012 at 03:05

Ping Plotter Standard or Freeware is quite good:
http://www.pingplotter.com/freeware.html

Ali195 · 22 Jul 2012 at 03:09

Nunzio said:
Ermm.. try tcptraceroute Or http://www.elifulkerson.com/projects/tcping.php

Yeah that tcping app is perfect. Many thanks.

Nunzio · 22 Jul 2012 at 03:50

http://www.elifulkerson.com/projects/mturoute.php

that is also handy for testing your MTU sizes over networks to make sure everything is configured right

Chief Wiggum · 22 Jul 2012 at 06:25

The syslog on the firewall is your biggest ally on something like this. Sure the utility will be handy but you need to keep in mind how TCP and UDP work.

TCP is connection orientated, so by default a firewall will expect a response from a device when a request is sent, this is automatically fixed up on the firewalls connection table and permitted by the firewall when the return traffic comes back to the firewall.

UDP is connection-less, it's fire and forget - the firewall will not expect a response for most UDP traffic (DNS and NTP are some of the exceptions as they are known protocols that require a response). This means that for most UDP traffic you have to permit the return traffic in the firewall policy.

While it is handy to be able to trace things with an App, learning to use and read Firewall syslog is one of the most important tools a firewall admin has at their disposal (it's not hard to read once you know what to look for).