Sign In
Create Account
Running iDeneb 10.5.5 but I've seen this problem with genuine Tigers and Leopards too.
What happens is predictable and reproducable:
Login verifies but during the vpn connection the firewall stalls and returns the following warning:
"The following ports are currently taken on your machine by other services. SSLVPN cannot tunnel these protocols until those ports are released.
RDP - 3389"
This is the same port that the Terminal Server uses.
On a windows box this also happens when the local Terminal Server is running, which is the default setting, on the connecting machine. Disabling the local Terminal Server fixes the problem.
Does anyone know if there's any service or app that needs to be "brought to it's knees" on osx to make it release this port?
Any help appreciated.
0
Connecting osx to Win Terminal Service through VPN port issue
Started by ShortStop, Dec 11 2008 09:15 PM
1 reply to this topic
#2
Posted 01 April 2009 - 09:37 AM
kaleko
-
- Just Joined
-
- 1 posts
InsanelyMac Protégé
ShortStop, on Dec 11 2008, 09:15 PM, said:
Running iDeneb 10.5.5 but I've seen this problem with genuine Tigers and Leopards too.
What happens is predictable and reproducable:
Login verifies but during the vpn connection the firewall stalls and returns the following warning:
"The following ports are currently taken on your machine by other services. SSLVPN cannot tunnel these protocols until those ports are released.
RDP - 3389"
This is the same port that the Terminal Server uses.
On a windows box this also happens when the local Terminal Server is running, which is the default setting, on the connecting machine. Disabling the local Terminal Server fixes the problem.
Does anyone know if there's any service or app that needs to be "brought to it's knees" on osx to make it release this port?
Any help appreciated.
What happens is predictable and reproducable:
Login verifies but during the vpn connection the firewall stalls and returns the following warning:
"The following ports are currently taken on your machine by other services. SSLVPN cannot tunnel these protocols until those ports are released.
RDP - 3389"
This is the same port that the Terminal Server uses.
On a windows box this also happens when the local Terminal Server is running, which is the default setting, on the connecting machine. Disabling the local Terminal Server fixes the problem.
Does anyone know if there's any service or app that needs to be "brought to it's knees" on osx to make it release this port?
Any help appreciated.
I have this problem ....
any question for this problem, please ????
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users