View Single Post
  #3 (permalink)  
Old December 31st, 2003, 07:43 AM
Andrew Antoniak Andrew Antoniak is offline
Authorized User
 
Join Date: Dec 2003
Location: Ravenshead, Notts, United Kingdom.
Posts: 13
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Good Morning Imar,

My service is provided by Frontier, and I am connected at home to my office 8 miles away so I can pick up my Outlook emails from there.

I tried pinging 127.0.0.1, and received a positive message that nothing was lost in the loop. However when I browsed to
http://127.0.0.1/localstart.asp I first received a message the page could not be displayed:-

"The page cannot be displayed
There is a problem with the page you are trying to reach and it cannot be displayed.

--------------------------------------------------------------------------------

Please try the following:

Open the 127.0.0.1 home page, and then look for links to the information you want.
Click the Refresh button, or try again later.

Click Search to look for information on the Internet.
You can also see a list of related sites.

HTTP 500 - Internal server error
Internet Explorer"
__________________________________________________ ________________________________

but then having tried it again (by clicking on the link in your email) I received the following message:

"You are not authorized to view this page
You do not have permission to view this directory or page using the credentials you supplied.

--------------------------------------------------------------------------------

Please try the following:

Click the Refresh button to try again with different credentials.
If you believe you should be able to view this directory or page, please contact the Web site administrator by using the e-mail address or phone number listed on the 127.0.0.1 home page.
HTTP 401.2 - Unauthorized: Logon failed due to server configuration
Internet Information Services

--------------------------------------------------------------------------------

Technical Information (for support personnel)

Background:
This is usually caused by a server-side script not sending the proper WWW-Authenticate header field. Using Active Server Pages scripting this is done by using the AddHeader method of the Response object to request that the client use a certain authentication method to access the resource.

More information:
Microsoft Support "

Does this help?

Regards,
Andrew Antoniak


Reply With Quote