Re: IIS 5.1 not working Help

From: Jason Brown [MSFT] (i-brjaso_at_online.microsoft.com)
Date: 01/19/05 

Date: Wed, 19 Jan 2005 12:58:56 +1100

oops. I left out the all important 80 in the telnet request

open 127.0.0.1 80
GET /

sorry about that. the desired result is that you see a bunch of HTML code
come back

you have process ID 1292 listening on port 80, which is the same process as
for FTP so most likely inetinfo.exe - meaning IIS is bound to the port. try
the telnet thing again and we may be able to discount an IIS problem and
concentrate on the client (IE) instead. It doesn't seem like a security
issue to me so far. It seems to me more like a plain communications problem
between client and server. when was the last time you ran a spyware/virus
scan? 

-- 
Jason Brown
Microsoft GTSC, IIS
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Thomas Grassi" <thomasgrassi@hotmail.com> wrote in message 
news:%23qkitec$EHA.2032@tk2msftngp13.phx.gbl...
> Jason
>
> Here is the results of your requests:
>
> Welcome to Microsoft Telnet Client
>
> Escape Character is 'CTRL+]'
>
> Microsoft Telnet> open 127.0.0.1
> Connecting To 127.0.0.1...Could not open connection to the host, on port 
> 23: Connect failed
> Microsoft Telnet> get /
> Invalid Command. type ?/help for help
> Microsoft Telnet> quit
>
> C:\Documents and Settings\Thomas R Grassi Jr>netstat -a -o
>
> Active Connections
>
>  Proto  Local Address          Foreign Address        State           PID
>  TCP    tgkw001:ftp            tgkw001:0              LISTENING       1292
>  TCP    tgkw001:http           tgkw001:0              LISTENING       1292
>  TCP    tgkw001:epmap          tgkw001:0              LISTENING       784
>  TCP    tgkw001:https          tgkw001:0              LISTENING       1292
>  TCP    tgkw001:microsoft-ds   tgkw001:0              LISTENING       4
>  TCP    tgkw001:1025           tgkw001:0              LISTENING       1292
>  TCP    tgkw001:ms-sql-s       tgkw001:0              LISTENING       1564
>  TCP    tgkw001:2160           tgkw001:0              LISTENING       1256
>  TCP    tgkw001:2161           tgkw001:0              LISTENING       1244
>  TCP    tgkw001:2260           tgkw001:0              LISTENING       1256
>  TCP    tgkw001:3052           tgkw001:0              LISTENING       1244
>  TCP    tgkw001:pop3           tgkw001:0              LISTENING       1840
>  TCP    tgkw001:1039           tgkw001:0              LISTENING       3804
>  TCP    tgkw001:2010           tgkw001:0              LISTENING       1840
>  TCP    tgkw001:5180           tgkw001:0              LISTENING       880
>  TCP    tgkw001:http           tgkw001:1080           CLOSE_WAIT      1292
>  TCP    tgkw001:http           tgkw001:1084           CLOSE_WAIT      1292
>  TCP    tgkw001:http           tgkw001:1088           CLOSE_WAIT      1292
>  TCP    tgkw001:http           tgkw001:1094           CLOSE_WAIT      1292
>  TCP    tgkw001:http           tgkw001:1098           CLOSE_WAIT      1292
>  TCP    tgkw001:http           tgkw001:1103           CLOSE_WAIT      1292
>  TCP    tgkw001:http           tgkw001:1104           CLOSE_WAIT      1292
>  TCP    tgkw001:http           tgkw001:kpop           CLOSE_WAIT      1292
>  TCP    tgkw001:http           tgkw001:1121           CLOSE_WAIT      1292
>  TCP    tgkw001:http           tgkw001:1125           CLOSE_WAIT      1292
>  TCP    tgkw001:http           tgkw001:1132           CLOSE_WAIT      1292
>  TCP    tgkw001:netbios-ssn    tgkw001:0              LISTENING       4
>  TCP    tgkw001:1050           baym-gw15.msgr.hotmail.com:http 
> ESTABLISHED
> 1016
>  TCP    tgkw001:1064           64.12.25.216:5190      ESTABLISHED     880
>  TCP    tgkw001:1075           oam-m14b.blue.aol.com:5190  ESTABLISHED 880
>  TCP    tgkw001:1706           msnews.microsoft.com:nntp  ESTABLISHED 1464
>  TCP    tgkw001:1707           msnews.microsoft.com:nntp  ESTABLISHED 1464
>  UDP    tgkw001:microsoft-ds   *:*                                    4
>  UDP    tgkw001:1027           *:*                                    1244
>  UDP    tgkw001:1032           *:*                                    1132
>  UDP    tgkw001:1046           *:*                                    896
>  UDP    tgkw001:1060           *:*                                    1016
>  UDP    tgkw001:ms-sql-m       *:*                                    1564
>  UDP    tgkw001:2160           *:*                                    1256
>  UDP    tgkw001:2161           *:*                                    1244
>  UDP    tgkw001:3456           *:*                                    1292
>  UDP    tgkw001:7846           *:*                                    1244
>  UDP    tgkw001:ntp            *:*                                    840
>  UDP    tgkw001:1047           *:*                                    840
>  UDP    tgkw001:1051           *:*                                    1016
>  UDP    tgkw001:1068           *:*                                    880
>  UDP    tgkw001:1464           *:*                                    624
>  UDP    tgkw001:1593           *:*                                    1540
>  UDP    tgkw001:1900           *:*                                    1000
>  UDP    tgkw001:discard        *:*                                    1016
>  UDP    tgkw001:ntp            *:*                                    840
>  UDP    tgkw001:netbios-ns     *:*                                    4
>  UDP    tgkw001:netbios-dgm    *:*                                    4
>  UDP    tgkw001:1900           *:*                                    1000
>  UDP    tgkw001:63745          *:*                                    1016
>
> Default Web Site Properties
> Description Default Web Site
> Ip Address (All Unassigned)
> TCP Port 80
>
> I am thinking it might be one of those security fixes cause it sure seems 
> like a security issue.
>
> any thing else to check
>
> Do you think I should call Windows XP Pro support? Would they be able to 
> help this issue?
>
> Thanks for you help
>
> Tom
>
>
> "Jason Brown [MSFT]" <i-brjaso@online.microsoft.com> wrote in message 
> news:O8hqwjb$EHA.2568@TK2MSFTNGP10.phx.gbl...
>>I don't think any of those patches are known to cause an issue with IIS.
>>
>> can you do the following for me
>>
>> open a command prompt
>> type 'telnet'
>> at the telnet prompt typ 'open 127.0.0.1'
>> if it connects, type 'GET /'
>> see what comes back, if anything.
>>
>> secondly, at the command prompt,
>> type 'netstat -a -o'
>> see what process id is listening on port 80/http
>> to find out what the name of that process is, get task manager up and 
>> check under 'processes'
>> it should be inetinfo.exe
>>
>> also type start->run->inetmgr and make sure the default website is 
>> running, and that it's bound to port 80 under 'properties'
>>
>>
>> -- 
>> Jason Brown
>> Microsoft GTSC, IIS
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Thomas Grassi" <thomasgrassi@hotmail.com> wrote in message 
>> news:OwizPzW$EHA.1084@tk2msftngp13.phx.gbl...
>>> Jason
>>>
>>> 1. World wide web publishing service is running
>>> 2. no proxy sever is not enabled in IE
>>> 3. Yes I use Mcafee antivirus and Mcafee Personal Firewall
>>> 4. http://127.0.0.1 does not work I can ping that address from a cmd 
>>> prompt on my computer
>>> 5. I do not think it does just one network adapter is installed
>>>
>>> Any other ideas
>>>
>>> I also installed a lot of security fixes yesterday could that be a 
>>> problem?
>>> I did have the antivirus and firewall installed and IIS was working.
>>> Here is what installed
>>> Update for Office 2003 French GRammer Checker KB873381
>>> Office 2003 Service Pack 1
>>> Security Update for Office XP Wordperfect Converter KB873379
>>> Hotfixes
>>> KB885884
>>> KB885836
>>> KB885835
>>> KB873339
>>> KB834707
>>> KB886185
>>> KB890175
>>>
>>> Any thoughts?
>>> Tom
>>>
>>>
>>> "Jason Brown [MSFT]" <i-brjaso@online.microsoft.com> wrote in message 
>>> news:%23OuGGaW$EHA.1452@TK2MSFTNGP11.phx.gbl...
>>>> couple of things to check
>>>>
>>>> - is the 'world wide web publishing' service running?
>>>> - do you have a proxy server enabled in IE? if so, do you have 'bypass 
>>>> proxy server for local addresses' enabled
>>>> - do you have any third-party firewall/antivirus type software which 
>>>> may block or otherwise mess with IIS?
>>>> - have you tried http://127.0.0.1/
>>>> - does your computer have a network connection or loopback adapter 
>>>> active?
>>>>
>>>>
>>>> -- 
>>>> Jason Brown
>>>> Microsoft GTSC, IIS
>>>>
>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>> rights.
>>>>
>>>>
>>>>
>>>> "Thomas Grassi" <thomasgrassi@hotmail.com> wrote in message 
>>>> news:eOrtMSW$EHA.2600@TK2MSFTNGP09.phx.gbl...
>>>>> To ALL
>>>>>
>>>>> I had Windows XP Home Edition on my computer to find that it did not 
>>>>> support
>>>>> IIS, so everyone said that I would be able to upgrade to Windows XP 
>>>>> Pro and
>>>>> that failed badly. I had to reformat and start from scratch. I then
>>>>> installed IIS and I was able to do http://localhost I then continued 
>>>>> to
>>>>> install the same software that I had on Home Edition. Several third 
>>>>> party
>>>>> programs including Mcafee Security Center but I had that installed 
>>>>> from the
>>>>> beginning and it was working. I did install Office XP downloaded sp3 
>>>>> and
>>>>> apply security fixes then SQL 2000 Developer SP3a last Frontpage 2003.
>>>>>
>>>>> I now get
>>>>> Cannot find server or DNS Error
>>>>> Internet Explorer
>>>>>
>>>>> I even placed an htm file and tried http://localhost/test.htm
>>>>>
>>>>> that also failed
>>>>>
>>>>> I thought I was going to be able to use IIS for my web developement 
>>>>> and now
>>>>> I do not know why I wasted two days upgrading to XP Pro if IIS does 
>>>>> not
>>>>> work.
>>>>>
>>>>> I stopped as many services as I could without shutting down xp but it 
>>>>> still
>>>>> fails.
>>>>>
>>>>> Does anyone have an idea what I can do? I am at witts end and still up 
>>>>> at
>>>>> 3:00 AM trying to get this bloddy thing to work.
>>>>>
>>>>> Thanks in advance
>>>>>
>>>>> Tom
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>