Re: Error: Protocol Not Valid for HTTP. Might Be Because Port Number Is Out of Range.
- From: "Ace Fekay [Microsoft Certified Trainer]" <aceman@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 23 Apr 2009 23:08:11 -0400
"pbd22" <dushkin@xxxxxxxxx> wrote in message news:4b709e86-9ce2-4485-933b-6dd6295234f2@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi. Thanks.
Thanks is an interesting thought.
I am using IIS 6.0 / Server 2003, not Apache.
Does anybody out there know of a DOS command
to probe port 80 and find out what processes are using it?
Or, for that matter, to find out what ports are being used
by a particular server?
I am still stuck on this one...
You can use netstat -ano, look at the PID and associate it with the PID in Task Manager.
There are other tools that can also be used, such as Process Explorer, to take it a step further, if need be, to look at the actual DLLs under a process.
Process ExplorerProcess Explorer, also known as procexp.exe, shows you information about which handles and DLLs processes have opened or loaded.
http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
aceman@xxxxxxxxxxxxxxxxxxxxxxx
For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
.
- Follow-Ups:
- References:
- Prev by Date: Re: Error: Protocol Not Valid for HTTP. Might Be Because Port Number Is Out of Range.
- Next by Date: Re: Join W2K to 2K3 domain - stymied
- Previous by thread: Re: Error: Protocol Not Valid for HTTP. Might Be Because Port Number Is Out of Range.
- Next by thread: Re: Error: Protocol Not Valid for HTTP. Might Be Because Port Number Is Out of Range.
- Index(es):
Relevant Pages
|