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 (not Business) + socks problems

mabornma over 8 years ago

Hello,

i have big trouble with skype (not business) over Sophos Socks since two weeks.

It comes “over night“…… befor 2 – 3 month no problems!

Mostly is impossible to make outgoing calls…….sometimes also incoming.

Webfilter SSO is activ with SSL URL scan enabled.

IDS/IPS not activ. I cant find any errors in socks log.

FYI: Sophos central endpoint is installed on all clients ( win7/10).

Is anybody out there who have actually problems with skype over socks?

thx

This thread was automatically locked due to age.

Parents

0 Daniel Boese over 8 years ago

We also had some trouble with that!
We figured out, that some Skype Versions don't pass the SOCKS Credentials to UTM (see in Log).

Currently we distribute Version 7.16.32.101, which don't has any of the problems.
Cancel
Vote Up 0 Vote Down

Cancel

0 mabornma over 8 years ago in reply to Daniel Boese

No socks authentication activated....

In SOCKS log i see only this:

2017:02:07-10:22:01 sophos sockd[5107]: info: pass(1): tcp/accept [: 192.168.121.182.58225 192.168.121.240.1080
2017:02:07-10:22:01 sophos sockd[5108]: info: pass(4): udp/udpassociate [: 0.0.0.0.52683 192.168.121.240.64269 -> 0.0.0.0.52683 0.0.0.0.0

Reply

0 mabornma over 8 years ago in reply to Daniel Boese

No socks authentication activated....

In SOCKS log i see only this:

2017:02:07-10:22:01 sophos sockd[5107]: info: pass(1): tcp/accept [: 192.168.121.182.58225 192.168.121.240.1080
2017:02:07-10:22:01 sophos sockd[5108]: info: pass(4): udp/udpassociate [: 0.0.0.0.52683 192.168.121.240.64269 -> 0.0.0.0.52683 0.0.0.0.0

Children

0 Daniel Boese over 8 years ago in reply to mabornma

Do you have the Skype SuperNode deactivated ?
Sometimes this causes some problems.
Cancel
Vote Up 0 Vote Down

Cancel
0 mabornma over 8 years ago in reply to Daniel Boese
I dont think that this is our problem beaucse of this constelation:

There are several ways to prevent Skype from becoming a supernode:

Beginning with Skype 3.0, an explicit switch is provided in the registry settings to allow the disabling of supernode functionality.

Any computer hosted on a network that is behind a network address translation (NAT) device or restrictive firewall will disable supernode functionality.

Skype clients behind an HTTP or SOCKS5 proxy will not serve as supernodes.
Cancel
Vote Up 0 Vote Down

Cancel
0 mabornma over 8 years ago in reply to mabornma

I also dont understand the communication behavior:

If i disable outgoing 80/443 rule skype is unable to connect. Why? I thought skype fully connect over SOCKS if activated?
Cancel
Vote Up 0 Vote Down

Cancel
0 mabornma over 8 years ago in reply to mabornma

Update:

There are serveral threads in skype forum like this:

https://community.skype.com/t5/Windows-desktop-client/Skype-new-version-not-woking-with-proxy-environment/td-p/4498984/page/13

The proxy implementation in the newer clients (above v7.16.) seems to be buggy.....
Cancel
Vote Up 0 Vote Down

Cancel
0 mabornma over 8 years ago in reply to mabornma

Update:

Skype seems to ingnore SOCKS connection settings IF direct internetaccess (80/443) is possible OR a system wide HTTP(S) proxy is configured.
If i drop all outgoing traffic via FW ruleand disable IE HTTP(S) proxy, Skype "fall back"to the configured SOCKS proxy!
BUT no outgoing calls possible! ECHO test drops call after 10-12 sec with no sound.
During call attemp i recognize in FW log, that UDP 3480 is blocked. After permitting this port, et voila.... ECHO test call works as expected....WTF?
Further problem:
Group calls ends unexpected when one called member tries to pick up the call.
I opened further ports (UDP 3478+3479). ....BINGO.... for this moment....

It is very frustrating....
Cancel
Vote Up 0 Vote Down

Cancel