re: Port Scan
Friday, September 5, 2003 at 1:45 am
Windows 2000 Annoyances Discussion Forum
Posted by asdfasdfa
(1 messages posted)
Pinging by default with Win2K cmd line is bound to ICMP packets. These are different
than TCP or UDP packets, so they can be controlled differently. Sometimes systems
are set to reject all ICMP ping packets, but are left wide open to TCP and UDP pings.
ping -v TCP (or udp if you prefer) IP. However, I do not believe a ping can be
directed at a specific port from a cmd prompt in Win2k.
On Thursday, August 16, 2001 at 6:31 am, B. Hill wrote:
>
>Ping relies on ICMP packets which know nothing about ports. Therefore no "ping"
tool
>(windows, unix, etc.) can "ping ports". You can use an application or a port scanner
>to test for ports. But remember ports are only reachable at "Layer 4 - Transport
>Layer" communications involving UDP or TCP. Ping operates only at "Layer 3 - Network
>Layer" using ICMP (i.e. 'echo request' and 'echo reply' packets). Hope this helps.
>
>
>On Tuesday, August 14, 2001 at 12:10 pm, Stuart Clark wrote:
>
>All -
>
>
>
>Is it possible to ping a specific port within the windows 2000 command line "ping"
>
>command? I'm not sure that there is, and if that is the case, is anyone aware of
>
>an Nmap type program that is compatable with W2K?
>
>
>
>Thanks,
>
>Stu
- Written in response to:
- re: Port Scan (B. Hill: Thursday, August 16, 2001 at 6:31 am)
There are presently no replies to this message.
|
|
All messages in this thread [show all]
 | Port Scan (Stuart Clark: Tue, Aug 14, 2001, 12:10 pm) |
 | |  | re: Port Scan (asdfasdfa: Fri, Sep 5, 2003, 1:45 am) |
| |
| |
Return to the Windows 2000 Discussion Forum
|
|
