• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 141
  • Last Modified:

Lync 2013 deployment on single server

I realize that we should be using an edge server and in time we will.  However, we are just basically using lync 2013 on a single server for messaging only.  Not interested in any audio visual yet.  This has been working for months now just fine, however the server took a unplanned power outage and was shut down unexpectedly.  After getting everything back up and running, I can only get lync working internally but not externally with messaging. Given me a DNS issue.

As a note, my exchange server was affected as well, but ended up I need to set the binding back for the SSL to the port that fixed that.  No such luck with Lync.  I am positive the topology is correct as it is working internally and even double checked everything.  I checked the AD DNS for the SRV record and it works.  I know it is something simple, but no idea what to look for at this point.
0
tomtom9898
Asked:
tomtom9898
1 Solution
 
Cliff GaliherCommented:
Because of the way SIP messages work, you need an edge server to have external access work reliably. No, this isn't just a DNS issue. You can reboot the Lync server 20 times and maybe the NAT device will register properly, and maybe not. Without an edge server, it is a roll of the device every time.

The edge server is not just an audio/video thing. Even simple IM uses SIP. And that is a non-Microsoft industry standard protocol that is *not* NAT friendly. This, for external access, an edge firewall really is necessary.
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now