About

I am a senior consultant working for a company called DIPS ASA (we develop electronic health record systems among other things), where I work with the internal IT dept. My main field of expertise is Microsoft Lync, but I am also a Cisco CCNA and UC consultant (certification pending).

I live in Bodø, in the northern Norway. Although I have an exciting job and three kids to manage I still try to find some time to share my experiences from everyday life as I am very fond of my job / hobby.

Advertisements

7 thoughts on “About

  1. Hi Rune,

    I have some problem with Lync Edge.

    Lync message between 2 networks only work one way

    I am able to Instance Message(IM) and see the presence information of the internal users, however the internal users (internal network) cannot reply my IM (external network).

    I don’t have public IP address, I want to connect Lync Edge Server with 2 different networks.

    I have set up a VMware lab environment (internal network) with 3 servers:

    – Domain Controller Server (with DHCP, DNS, Certification Authority), Full computer name: W2012R2QA2.pronexuslab.com (domain:pronexuslab.com), IP: 10.89.89.1 (internal network) and IP: 10.207.241.11 (external network), OS: Window2012R2

    – Lync Front End Server, Full computer name: W2012R2-Lync.pronexuslab.com (domain:pronexuslab.com) with Lync Server 2013 Standard Edition, IP: 10.89.89.2 (internal network), OS: Window2012R2

    – Lync Edge Server, Full computer name: W2012LYNCEDGE.pronexuslab.com (not a member of the domain), IP: 10.89.89.3 (internal network) and IP: 10.207.241.12 (external network), OS: Window2012R2

    Lync Edge Server:
    I have 2 networks one internal (the VMware lab environment with domain:pronexuslab.com) and one external(with physical computers, other domain), I have set up a Lync Edge Server with 1 IP address to connect to an external network and another IP address to connect to the internal network.

    Internal server FQDN : W2012LYNCEDGE.pronexuslab.com
    Internal IPv4 address : 10.89.89.3
    Federation (port 5061): Enabled
    XMPP federation (port 5269): Disabled
    Internal Configuration Replication Port (HTTPS): 4443

    External FQDNs with single IP address:
    Access Edge Service : edge.pronexuslab.com, IPv4 address: 10.207.241.12, Port:5061, Protocol: TLS

    Web Conferencig Edge Service: edge.pronexuslab.com, IPv4 address: 10.207.241.12, Port:444, Protocol: TLS

    A/V Edge Service: edge.pronexuslab.com, IPv4 address: 10.207.241.12, NAT: Disabled, Port:443, Protocol: TCP

    I have also set up a Web Application Proxy on Lync Edge Server.

    Users:
    I have created 4 users: u1@pronexuslab.com, u2@pronexuslab.com, u3@pronexuslab.com, u4@pronexuslab.com
    I also have installed the Lync Client Basic 2013 on each server (u1@pronexuslab.com on Lync Edge Server, u2@pronexuslab.com on Domain Controller Server, u3@pronexuslab.com on Lync Front End Server)

    Test 1: User1 can send instant message and chat to User2,User3 and vice versa without problem. (users on internal network + user on Edge Server can sent instant messages and chat without problems)

    Test 2: I have my physical PC (external network) with u4@pronexuslab.com I can sent IM (Instant Message) to User1, User2 and User3 (they can receive the message), but they can’t sent an IM to User4

    Error ID 504 (source ID 239)

    The following information was included with the event:

    Lync
    80ef01f8
    RequestUri: sip:u4@pronexuslab.com
    From: sip:u1@pronexuslab.com;tag=22012ccb88
    To: sip:u4@pronexuslab.com;tag=69FF3C90B094576EAEC7EC1AD289D4E2
    Call-ID: b9858363879046e198b9327df4265abc
    Content-type: application/sdp;call-type=im

    v=0
    o=- 0 0 IN IP4 10.89.89.3
    s=session
    c=IN IP4 10.89.89.3
    t=0 0
    m=message 5060 sip null
    a=accept-types:text/plain multipart/alternative image/gif text/rtf text/html application/ms-imdn+xml text/x-msmsgsinvite

    Response Data:

    101 Progress Report
    ms-diagnostics: 13004;reason=”Request was proxied to one or more registered endpoints”;source=”W2012R2-LYNC.PRONEXUSLAB.COM”;Count=”1″;appName=”InboundRouting”

    504 Server time-out
    ms-diagnostics: 1014;reason=”Unable to resolve host name record”;LookupFQDN=”W2012LYNCEDGE.pronexuslab.com”;source=”W2012R2-Lync.pronexuslab.com”;OriginalPresenceState=”3000″;CurrentPresenceState=”3000″;MeInsideUser=”Yes”;ConversationInitiatedBy=”14″;SourceNetwork=”2″;RemotePartyCanDoIM=”Yes”

    Question:
    Do I need to open ports on the Edge Server firewall and Client’s firewall for internal network and external network?

    Thank you for your help.

    Oscar Osorio

    • Hi Oscar.

      From what I can see it looks like you have a DNS issue, where the Front End cannot resolve the IP address of your Edge server FQDN. Verify this by pinging or resolving (nslookup) the FQDN from your Front End.
      Firewall exceptions Are generated automatically when running Deployment on server or client installer.

      Best regards,
      Rune

  2. Hi Rune,
    Thanks for sharing your smartdock experience.
    I have the same query : “how can we use PXE install instead of USB key ?”
    You write “The latter can be a pain, because PXE booting a Surface Pro 4 turned out such big a problem I had to go on using USB bootable media instead”…
    What kind of configurations did you test ?
    Do you know if a network solution would be possible ?
    Best Regards,
    Jean-Noel

    • Hi Jean-Noel.

      I haven’t done any testing on the subject afterwards, as we have only deployed a few number of systems. It is probably possible to PXE boot using native USB-Ethernet adapters made for the Surface Pro 4 like others have suggested in their comments, but I have not heard of it being confirmed.

      Brgds
      Rune

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s