OT: IIS 6.0 Blank Title 102542

Yahoo Archive
1
Seems like directory security issue.

From Web Properties -> Directory Security -> Edit -> Check off "Anonymous Access" -> enter username and password that has access rights to the directory on local pc (Administrator for example).



--- In vantage@yahoogroups.com, "vicdrecchio" <vic.drecchio@...> wrote:
>
> Off topic question... hoping some IIS wizard can help me. :-)
>
> I'm working with a friend helping his company. I have IIS installed. Everything was working fine until some outsourced dude came in and screwed up some things (DNS?) and also installed a few things.
>
> This is all intranet. Nothing to do with a "real" external webserver. We'll call this webserver "XXX".
>
> If I am on "XXX" (terminal serviced in) and I pull up Internet Explorer.... I used to be able to enter in "http://xxx/" and it would pull up the index page. I have a whole bunch of "dashboards" that hit the Vantage tables that run on ASP on this box.
>
> But now, for troubleshooting, the html file is a simple "hello world" html file. No ASP, no bells and whistles.
>
> Obviously, from any other workstation in the company, they also could go to http:/xxx/ with no issue.
>
> Now they cannot after this guy came in and screwed with things.
>
> I can ping XXX and it resolves the IP addr just fine from all clients. So it doesn't seem like a DNS issue.
>
> So, I RDP back into server XXX. From XXX I open up IE and go to http://xxx and nothing happens (forbidden error). I can also try and go to the IP addr of the server: http://192.168.80.150 and again, nothing (same error). It doesn't pull up the simple html file.
>
> HOWEVER..... this is what is killing me.............. While RDP'd on server XXX, if I open IE and go to http://localhost/ the simple "hello world" html file comes right up.
>
> I've Googled the heck out of this problem and I'm pulling out my hair. I have no clue what could be causing this.
>
> Any input would be helpful and thanks in advance...... :-)
>
2
Off topic question... hoping some IIS wizard can help me. :-)

I'm working with a friend helping his company. I have IIS installed. Everything was working fine until some outsourced dude came in and screwed up some things (DNS?) and also installed a few things.

This is all intranet. Nothing to do with a "real" external webserver. We'll call this webserver "XXX".

If I am on "XXX" (terminal serviced in) and I pull up Internet Explorer.... I used to be able to enter in "http://xxx/" and it would pull up the index page. I have a whole bunch of "dashboards" that hit the Vantage tables that run on ASP on this box.

But now, for troubleshooting, the html file is a simple "hello world" html file. No ASP, no bells and whistles.

Obviously, from any other workstation in the company, they also could go to http:/xxx/ with no issue.

Now they cannot after this guy came in and screwed with things.

I can ping XXX and it resolves the IP addr just fine from all clients. So it doesn't seem like a DNS issue.

So, I RDP back into server XXX. From XXX I open up IE and go to http://xxx and nothing happens (forbidden error). I can also try and go to the IP addr of the server: http://192.168.80.150 and again, nothing (same error). It doesn't pull up the simple html file.

HOWEVER..... this is what is killing me.............. While RDP'd on server XXX, if I open IE and go to http://localhost/ the simple "hello world" html file comes right up.

I've Googled the heck out of this problem and I'm pulling out my hair. I have no clue what could be causing this.

Any input would be helpful and thanks in advance...... :-)
3
Have you checked your bindings?

On Fri, Jul 22, 2011 at 11:23 AM, vicdrecchio <vic.drecchio@...>wrote:

> **
>
>
> Off topic question... hoping some IIS wizard can help me. :-)
>
> I'm working with a friend helping his company. I have IIS installed.
> Everything was working fine until some outsourced dude came in and screwed
> up some things (DNS?) and also installed a few things.
>
> This is all intranet. Nothing to do with a "real" external webserver. We'll
> call this webserver "XXX".
>
> If I am on "XXX" (terminal serviced in) and I pull up Internet Explorer....
> I used to be able to enter in "http://xxx/" and it would pull up the index
> page. I have a whole bunch of "dashboards" that hit the Vantage tables that
> run on ASP on this box.
>
> But now, for troubleshooting, the html file is a simple "hello world" html
> file. No ASP, no bells and whistles.
>
> Obviously, from any other workstation in the company, they also could go to
> http:/xxx/ with no issue.
>
> Now they cannot after this guy came in and screwed with things.
>
> I can ping XXX and it resolves the IP addr just fine from all clients. So
> it doesn't seem like a DNS issue.
>
> So, I RDP back into server XXX. From XXX I open up IE and go to http://xxxand nothing happens (forbidden error). I can also try and go to the IP addr
> of the server: http://192.168.80.150 and again, nothing (same error). It
> doesn't pull up the simple html file.
>
> HOWEVER..... this is what is killing me.............. While RDP'd on server
> XXX, if I open IE and go to http://localhost/ the simple "hello world"
> html file comes right up.
>
> I've Googled the heck out of this problem and I'm pulling out my hair. I
> have no clue what could be causing this.
>
> Any input would be helpful and thanks in advance...... :-)
>
>
>



--
*Waffqle Driggers*
*High End Dev, System Design, Profit Drinking
*
*:: 904.962.2887*
*:: waffqle@...*
*:: NO FAXES*

*

*


[Non-text portions of this message have been removed]