Thanks Ken. I probably was not clear in my question. I am a novice with IIS.
The url http://servername/appname works fine, but if I put in
http://serverip/appname, i get a pop up box for credentials. We user a round
robin DNS entry that uses the ip addresses of the server to "balance" the
load. Since the http://serverip/appname link asks for credentials, the DNS
entry does as well. All works fine if the user goes to
http://servername/appname
[quoted text, click to view] "Ken Schaefer" wrote:
> Hi,
>
> \\servername\app is a UNC path. It is not a HTTP URI. IIS does not serve
> requests based on UNC paths (that's the responsibility of the CIFS/SMB
> server). IIS only serves requests that start with http://... (or ftp:// or
> https://... etc)
>
> Cheers
> Ken
>
> "Greg M" <GregM@discussions.microsoft.com> wrote in message
> news:32DD8661-E4DA-43B7-AB56-637052ADB23A@microsoft.com...
> > Last night, I updated an application running on IIS6 to use trusted
> > logins.
> >
> > If the user go to \\servername\app
> >
> > all is fine and the app opens
> >
> >
> >
> > If the user goes to the ip address of the server then the app
> > (i.e \\10.10.10.10\app), it prompts the user for a login (generic windows
> > username password box)
> >
> > Any idea why this would happen?
> >
> >
>
Sounds like you are running into this behaviour:
http://support.microsoft.com/?id=258063 The website requires authentication. In the case of http://servername your
application meets all the requirements for IE to attempt auto-logon. with
http://ip.address the site is in the "internet" security zone by default,
and IE does not attempt autologon.
Cheers
Ken
[quoted text, click to view] "Greg M" <GregM@discussions.microsoft.com> wrote in message
news:732050EA-6331-494F-851D-35B0846B1468@microsoft.com...
> Thanks Ken. I probably was not clear in my question. I am a novice with
> IIS.
>
> The url http://servername/appname works fine, but if I put in
> http://serverip/appname, i get a pop up box for credentials. We user a
> round
> robin DNS entry that uses the ip addresses of the server to "balance" the
> load. Since the http://serverip/appname link asks for credentials, the DNS
> entry does as well. All works fine if the user goes to
> http://servername/appname
>
> "Ken Schaefer" wrote:
>
>> Hi,
>>
>> \\servername\app is a UNC path. It is not a HTTP URI. IIS does not serve
>> requests based on UNC paths (that's the responsibility of the CIFS/SMB
>> server). IIS only serves requests that start with http://... (or ftp://
>> or
>> https://... etc)
>>
>> Cheers
>> Ken
>>
>> "Greg M" <GregM@discussions.microsoft.com> wrote in message
>> news:32DD8661-E4DA-43B7-AB56-637052ADB23A@microsoft.com...
>> > Last night, I updated an application running on IIS6 to use trusted
>> > logins.
>> >
>> > If the user go to \\servername\app
>> >
>> > all is fine and the app opens
>> >
>> >
>> >
>> > If the user goes to the ip address of the server then the app
>> > (i.e \\10.10.10.10\app), it prompts the user for a login (generic
>> > windows
>> > username password box)
>> >
>> > Any idea why this would happen?
>> >
>> >
>>
>>
Don't see what you're looking for? Try a search.
