I have 10 parent portals and 5 child portals running on my server. Only one installation of DotNetNuke. When I try to add user in one of the portals which has been added to another portal (it does not matter if it is parent or child) I get the error "User already exists". Username John in one portal is not nesseserly the same John in another portal - but it is possible. Has anybody exerienced this kind of behaviour?

I dont understand this. Are you saying that if I have two portals in my Dnn installation (p1=parent, p2=parent) I cannot have two John's, only one? So if I have John in p1 I must have John2 in p2. So users are not specific to portals.

This is not a DNN issue but an ASP.NET issue that has been imported in DNN.

I think at the moment this is a big limitation for a powerful product like DNN.
How many installations of DNN have many different portals? Why limit possible usernames of  P2, P3, P4, ...  just because in P1 there is already a username?

This i particularly bad for simple username like "Fred", "John", ....

I hope Microsoft or DNN guys will redesign this approach in future versions.

Bye

Luca
Italy