Unable to sign onto Skype for Business in a test environment

My organization is testing Lync 2013 server in a test environment.  We are a small organization, so we are just testing using a single Standard Edition Lync 2013 server.   We Lync-enabled four test users using the Lync Server Control Panel.  My client machine was already automaticallly updated to Skype for Business 2015.  When first launching, it auto-filled the user account as testuser@sip.domain.org.  We used the SIP domain of our real organization when setting up the Lync topology as we weren't yet going to be using any voice features of Lync in the test environment, but we had to put something in.

When I changed the sign-in address to testuser@test.local, SfB was able to contact the Lync server and it prompted me for a username and password.  I tried test\testuser, test.local\testuser, and even testuser@test.local along with the password for that user.  Every time it says incorrect username or password, even though I am sure the password is correct since I'm logged onto the client machine with that account.

Do you have any suggestions as to where I might look to resolve this issue?
ejscnITAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jakob DigranesSenior ConsultantCommented:
do you have separate domains, or do you have a domain zone and UPN for test?
Each user in Lync needs to have a login to lync bound to SIP-domain.
So if your username in AD is testuser@test.local but you sip-domain is domain.org - you need to either add sip-domain test.local and create all referencing DNS and certificate changes, or you need to user testuser@sipdomain.org to login
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ejscnITAuthor Commented:
Jakob,

Thanks for your help!  I changed the test SIP domain to match my AD Domain (test.local) and was able to get in.  However, that is not how our real organization is set up.  We use mybusiness.org for our AD domain and facility.mybusiness.org for SIP domains - one domain per facility.  While we do have an overarching mybusiness.org SIP domain, it is not used.  When I tested using facility.test.local as the SIP domain in my test environment, I had the same issue of not being able to log on.  

In the end, the only connection that needs to be made to our SIP environment is to enable dial-in conferencing.  We are not going to enable Enterprise Voice features in Lync.  With that in mind, should we just have multiple SIP domains set up in Lync (our AD domain and our SIP domains) so that we can eventually roll out dial-in conferencing?

I appreciate your help.
0
Jakob DigranesSenior ConsultantCommented:
When using multiple SIP-domains you complicate your installation quite a bit, but it should be possible (altough I haven't done it using sub-domains, just completely different domains, like test1.com, test2.com etc).  To be able to use several SIP-domains, consider the following:

- the SIP-domains needs to be added to Lync
- DNS-records must be in place, for all SIP-domain
- Certificates must have all records for services (sip.sub.domain.com, dialin.domain.com (just one))
- do SIP-addresses match email-addresses?
0
ejscnITAuthor Commented:
No, email addresses use the user@mybusiness.org format.  Our network/phone guy told me that we do have mybusiness.org as an available SIP domain, and we can assign extensions to it, we just haven't yet and he would prefer not to.  Based on what you're saying, it may be worth convincing him to point a few extensions to the mybusiness.org domain to make the Lync deployment simpler.

I really can't thank you enough for your help.  Thanks again.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Chat / IM

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.