how to enable a single user account for multiple logins?

yours must be a permissions issue. the trouble user must be denied multiple logins through group policies please verify

I think this behavior is only controlled by the rdp connector properties. One way would be to add a 2nd network card. Configure rdp connector properties per nic instead of all network adapters. Set the permissions to only allow that one user to connect to the 2nd nic. Make sense?

Every account is set to allow only one session per user.  I am trying to enable multiple unique session logged under the same generic user account.  

There is a group policy setting located here:
Computer Configuration>Administrative Templates>Terminal Services> Under this there is a policy setting to: Restrict Terminal Services users to a single remote session. Configure as necessary, by default, it is not configured. If you are being limited to only one connection, this setting may be in effect on some other group policy in your domain.

just quietly, this isnt the best idea, in terminal services you are much better with individual users, if two log off, they might take over each others sessions when they log back on, i HIGHLY reccomend avoiding the path you are looking at taking, i guarrantee it will bite you

I am not sure I have been clear enough. I know how to enable multiple sessions for all users via Terminal Server Configuration and via Group policy, however I do not want all users to be able to log in to multiple sessions, just one user account, a generic intern account for example. I can see how multiple NICs might be a solution but not worth it. I am wondering if anyone knows of a trick on how to do this through Group Policy. The reason it doesn't work easily is because the setting for allowing multiple sessions is a computer configuration policy not user.

I think I understand now. Unfortunately, there is no way currently to apply different group policies (computer policies specifically) to the same computer (server) based upon the user logging in. It would be great if there was however. If you had multiple term servers, one could be set to do what you want, and the other set to operate normally.

indeed there is, you can use loopback processing in group policies to do exactly that.....

however, again, even after reading your Q again, do not go this path, you are going to invoke a loss of accountability, unmanageability, users jumping through each other sessions. this is a bad idea

hmm that sucks, sorry for the mislead, i should have read the Q deeper....

Thanks t, that's what I figured.