By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,939 Members | 1,602 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,939 IT Pros & Developers. It's quick & easy.

Basic ASPNet authorization question

P: n/a
dgk
I'm trying my first website on my home PC and I keep getting a logon
screen (part of windows) asking for a username and password when I
access it remotely. The with the little face in the username screen.
How do I have to set it up so that users won't get that? I can't even
figure out what username and password will work.
I'm trying this using http://nnn.nnn.nnn.nnn/dotnetnuke. (nnn to keep
the address a secret for now) Oh, I just realized something. When I
went to create a virtual directory it said that DotNetNuke wasn't
unique (which was somewhat odd because I don't think I had installed
it before - there is no such directory anywhere). So I used the alias
DNN. Now, when I try nnn.nnn.nnn.nnn/DNN, I get this:

DotNetNuke Configuration Error
Domain Name "nnn.nnn.nnn.nnn/dnn" Does Not Exist In The Database.

So it has something to do with that original failure to be able to use
DotNetNuke as the alias.

Well, any help greatly appreciated.
Nov 18 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
In the IIS manager, go to the properties for your web site, and on the
Directory Security tab click the Edit button under Access Control. Make
sure Integrated Windows Authentication is turned off, and Anonymous
access is turned on.

I'll have to pass on the second question.

-Jason

dgk wrote:
I'm trying my first website on my home PC and I keep getting a logon
screen (part of windows) asking for a username and password when I
access it remotely. The with the little face in the username screen.
How do I have to set it up so that users won't get that? I can't even
figure out what username and password will work.
I'm trying this using http://nnn.nnn.nnn.nnn/dotnetnuke. (nnn to keep
the address a secret for now) Oh, I just realized something. When I
went to create a virtual directory it said that DotNetNuke wasn't
unique (which was somewhat odd because I don't think I had installed
it before - there is no such directory anywhere). So I used the alias
DNN. Now, when I try nnn.nnn.nnn.nnn/DNN, I get this:

DotNetNuke Configuration Error
Domain Name "nnn.nnn.nnn.nnn/dnn" Does Not Exist In The Database.

So it has something to do with that original failure to be able to use
DotNetNuke as the alias.

Well, any help greatly appreciated.

Nov 18 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.