Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 6 replies
  • Subscribers 6 subscribers
  • Views 14523 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Skype ports?

Mateusz Bender

I do realize that questions regarding Skype should be posted on the Skype forums and / or resolved with Skype support. But Skype is common enough, I'm hoping someone else here might have some insight if they allow Skype in their environment.

Namely, I've noticed that Skype stopped working properly recently - i.e. messages work, voice connections work, but the icon in the app is a constant "trying to log in" icon for everyone on our network and people have been pestering me about this. I've traced the problem and found that Skype is trying to use unlisted ports. Unlisted according to this page: https://support.skype.com/en/faq/FA148/which-ports-need-to-be-open-to-use-skype-for-windows-desktop

(That port list in the FAQ already contains HUGE ranges!)

I've found it tries to use TCP/UDP ports 40000+, and on top of that port 12350 on startup. All of this is seriously p*****g me off, as the official FAQ is clearly misleading, and I don't know where to turn to get any sensible answers as Skype community managers can reference the FAQ at best and I can't really find a way to get in touch with any Skype devs to tell them their FAQ is in dire need of an update.

I don't want to open hundreds of ports just to get Skype working correctly in our environment. How do people set up UTM to allow Skype to work but keep the network secure?



This thread was automatically locked due to age.
  • 0

    We just experience the same since middle/end of last week. We opened some ports in 40000 range in Germany and all works fine. Did the same in UK but did not have any effect. Instead I see connections trying the 30000 range. This is really annoying. Will try the socks thing.

    Btw: It only seems to affect the "legacy" Desktop Client. The newer Windows 10 app works fine without any additional ports.

  • 0 in reply to astiadmin

    SOCKS is also not a solution at the moment.

    While, yes, you can configure SOCKS and it will work, you can't use authentication, as there seems to be a bug in Skype which messes that up as well. So - either set up the port exceptions on the FW, or configure an "open" SOCKS to the outside world for everyone / everything in your network to use. :|

  • 0 in reply to Mateusz Bender

    Hallo Mateusz,

    I just updated Skype to 7.40.0.104 and am using SOCKS5 with 9.506 successfully.  There was a Skype bug in the past.  Do you have better luck with the versions I mention?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    I saw your other reply. It seems this version of Skype can connect using just 80 / 443? I've enabled proxy + authentication, but the logs still show failed connection attempts.

  • 0

    I had all of your same frustrations.   Web search said to apply updates, but Skype For Desktop (v7.x) said there were no updates available.   Eventually I downloaded and installed Skype on a different device, and realized I had not been on the current version.   Removed version 7, then downloaded and installed version 8.16.   It appear to operate using port 443 only -- UDP 443 is preferred if it is available, but it will fall back to TCP 443 if UDP 443 is blocked.

    Is this consistent with other's experience?

Unfiltered HTML