Okay, I've tried the stuff @ the 2nd thread.
In simple terms, the gist of what he's trying to do is to provide a webservice to communityserver to update it's own user-base when dotnetnuke adds/deletes/updates a user. So when dotnetnuke calls any of those, additional code is added to call the webservice @ communityserver to update it's own users.
There's still a problem of the cookies not reading correctly, but I'll fix it soon. :) Prepare for a great day today.