|
|
|
Port Scan
Showing all messages in thread #997816210 Windows 2000 Annoyances Discussion Forum
The following are all of the messages in this thread (4 in all), shown in chronological order. Click any message subject to view that message by itself or to view the thread hierarchy.
|
Port Scan
Tuesday, August 14, 2001 at 12:10 pm Posted by Stuart Clark
(1 messages posted)
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
[Reply or follow-up to this message]
| |
re: Port Scan
Tuesday, August 14, 2001 at 2:20 pm Posted by Curt R
(1315 messages posted)
Open a DOS window and type the following without quotes: "ping /?" This will
list available switches.
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
[Reply or follow-up to this message]
|
re: Port Scan
Thursday, August 16, 2001 at 6:31 am Posted by B. Hill
(1 messages posted)
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
[Reply or follow-up to this message]
|
re: Port Scan
Friday, September 5, 2003 at 1:45 am 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
[Reply or follow-up to this message]
| |
| |
Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread
| |
Return to the Windows 2000 Discussion Forum
|
|
|
|