Skype for Business Server

I have an existing Lync2013 server and Edge pool that I have just upgraded to SFB2015, during the upgrade process it comes up with an error that I can move past that is
•      This topology contains the following servers or clusters that use a NetBIOS name as the fully qualified domain name (FQDN) value, which is not supported.  Please update the NetBIOS name to an FQDN, for example pool01.contoso.com.

I have now done the upgrade but I can no longer call from my client to myself, also running SFB2015.

Process was upgrade my own SFB2015 - all good; communications between both OK
Upgrade clients and can now no longer communicate...can IM, but cannot enable calls, they just stop, but have an error
Condition failed with 80ee002a

I cannot see anyway to fix the FQDN on the SFB server, but the thing I don't get is that it is a FQDN....so I can't understand where the NetBIOS part is being pulled from.

Please help
LVL 3
activitAsked:
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.

Mohammed HamadaSenior IT ConsultantCommented:
What's your Pool name on Lync ? are you using Standard or Enterprise edition? In Standard edition the pool must match the server's FQDN or else it'll fail to authenticate with the SQL express.
0
activitAuthor Commented:
Standard - it is working except for the Voice between the myself and them...so everything else is working...it is just not connecting the call.
0
activitAuthor Commented:
on my server I have the same NetBIOS and FQDN and it works fine and I don't get any error.  I am thinking there must be an issue in the server and considering redoing it....not a fun prospect
0
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

Mohammed HamadaSenior IT ConsultantCommented:
Which guide have you followed for the upgrade? Have you done an in-place upgrade or deployed S4B on a separate server?

In order to upgrade to S4B without any issues you must have at least CU5 deployed on Lync 2013 and have Powershell RTM version 6.2.92.0.

Do you get any errors in the event viewer where it says "Lync Server" Under Applications and Services?
0
activitAuthor Commented:
It went through fine, the only error I have is about the FQDN and NetBIOS name.  But I can call from my mobile to the client fine and if I take my laptop to an external connection it also connects fine.  The issue is client to client when both on the inside of the domain network.
0
Mohammed HamadaSenior IT ConsultantCommented:
From the client PC can you press CTRL and right click on Skype for Business client in the tray bar and then choose "Configuration information" and check where are the clients connected to? is it the correct Front end?
0
activitAuthor Commented:
Yes it is...all looks good.  I have heard that this may be an MS bug, as I can now no longer talk to any of the other federated sites I have connected too.  Can IM no problem
0
Mohammed HamadaSenior IT ConsultantCommented:
What version of Ms Skype for Business have you upgraded too? As far as I know now there's only the Preview version available. the RTM is not officially released! or is it?
0
activitAuthor Commented:
Yes it has been released
0
activitAuthor Commented:
I fixed this...had a wrong External IP used my old topology to walk through it and check..
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
Mohammed HamadaSenior IT ConsultantCommented:
Great, congrats
0
activitAuthor Commented:
Miss configured an IP, so having a backup of my original topology allowed me to work back and see that I had an External IP round threw wrong way
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.