Colleague not able to get Skype working with SBS 2000 and ISA 2000.
A Skype posting suggests need to open outgoing TCP ports > 1024 (or 80
and 443 but > 1024 better) and all outgoing and incoming UDP ports >
1024.
Does any of above make sense?!
Cheers
Geoff
>Hello,
>
>Colleague not able to get Skype working with SBS 2000 and ISA 2000.
>
>A Skype posting suggests need to open outgoing TCP ports > 1024 (or 80
>and 443 but > 1024 better) and all outgoing and incoming UDP ports >
>1024.
>
You might want to look here:
http://support.skype.com/?_a=knowledgebase&_j=questiondetails&_i=148
Essentially, if the users IE proxy settings are filled out, Skype will try
to use those. Note that by default, SBS2000 insists on user authentication,
so you would need to either lift that requirement, or configure Skype to
authenticate to the proxy (Tools > Options > Connection in Skype).
Alternatively, if the Firewall Client is deployed, it will authenticate to
ISA on behalf of the Skype client, and then Skype should be configured for
no proxy at all.
You don't need to configure any incoming settings at all in ISA, but Skype
quality will be better if you can arrange to server publish each individual
skype installation. By default, Skype picks a random port for listening
(again, Tools > Options > Connections), but in a corporate environment, I'd
set aside a block of high-numbered ports for all machines and manually set
the Skype ports in some organised manner, so that managing the ISA protocol
definitions and server publishing rules needed is easier.
Make sure you keep your Skype installations up-to-date though - there have
been security vulnerabilities reported in their software, and if you're
making it generally accessible, your network is potentially at risk.
--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.
>Essentially, if the users IE proxy settings are filled out, Skype will try
>to use those. Note that by default, SBS2000 insists on user authentication,
>so you would need to either lift that requirement, or configure Skype to
>authenticate to the proxy (Tools > Options > Connection in Skype).
>
>Alternatively, if the Firewall Client is deployed, it will authenticate to
>ISA on behalf of the Skype client, and then Skype should be configured for
>no proxy at all.
>
>You don't need to configure any incoming settings at all in ISA, but Skype
>quality will be better if you can arrange to server publish each individual
>skype installation. By default, Skype picks a random port for listening
>(again, Tools > Options > Connections), but in a corporate environment, I'd
>set aside a block of high-numbered ports for all machines and manually set
>the Skype ports in some organised manner, so that managing the ISA protocol
>definitions and server publishing rules needed is easier.
>
>Make sure you keep your Skype installations up-to-date though - there have
>been security vulnerabilities reported in their software, and if you're
>making it generally accessible, your network is potentially at risk.
Many thanks Steve,
Cheers
Geoff