• 1 Votes
    1 Posts
    365 Views
    No one has replied
  • PDQ Link

    IT Discussion
    13
    2 Votes
    13 Posts
    2k Views
    M

    @ambarishrh said in PDQ Link:

    @jaredbusch said in PDQ Link:

    @Ambarishrh said in PDQ Link:

    The only catch I could see is the mandatory port 443 as per their site

    The majority of work for Link is done with our installer, but there is one bit that will have to be done by you or your network team. Your external firewall will need to route incoming TCP 443 to your PDQ Link server. 443 is the only port SSTP can utilize. This configuration is mandatory to allow your external clients to connect.

    If you already have another service on 443 with a public IP, we need to use an additional IP for PDQ link.

    That is what inbound proxy servers are for.

    digging an older topic as I am testing this now. Regarding inbound proxy
    , what would you suggest to be used?

    This isn't that simple, you need a proxy that supports TCP streams, unless SSTP behaves just like HTTPS. You'd need to talk to PDQ support to get more details. If you do end up needing TCP streams, I think Nginx, Traefik, and Haproxy all support that, and there's a mod for Apache too, but if I recall it correctly, it was specifically for MSRPC, so Exchange OWA or RDS.

  • 2 Votes
    16 Posts
    3k Views
    travisdh1T

    @dafyre said in Experiencing an NPS related issue:

    @DustinB3403 said in Experiencing an NPS related issue:

    Stupid Fing wireless AP giving me a hard time for nothing....

    I swapped the AP's from the two areas, "the one that had issues", came up and worked, no changes.

    Put the other in place of the one with issues and it works without any changes.

    What the heck...

    ROFL. The gremlins are out to get you today.

    Man, I need to grab a picture of me petting my cat. She's a calico that looks like Gizmo when scratching behind the ears.