Microsoft Remote Desktop over L2TP/IPSec VPN to Tiger Server not working
I need to use Microsoft Remote Desktop over an L2TP VPN connection to a Mac OS X Server (10.4.2). the VPN connection itself is working fine, I can use AFP, SSH, LPT and any other thing I've tested. The only thing that doesn't work is MS-RDC. (Version 1.0.3 (040913))
The exact Error message I get from MS-RDC Client is:
The client computer could not connect to the remote computer
Either remote connections are not enabled, the computer is too busy to accept new connections, or network problems are preventing your connection. Try connecting again later or contact your administrator.
I really like the clear and focused error message with a lot of possibilities...
Remote connections are enabled on the remote computer and that machine is definitely not too busy to accept new connections. Connecting at a later time doesn't help either which leaves me with the "network problems" and contacting my administrator. I am quite confident that I do not have problems with the network as I can use any other service over that VPN connection. My administrator, which I am myself, didn't have a solution for me yet. 🙂
Afaik MS-RDC only uses TCP port 3389, just like AFP uses TCP port 548. The difference is, that AFP works just fine, whereas RDC keeps telling me about not beeing able to connect. When physically connected to the network there RDC works just fine. I am connected over 3Mbit DSL, so bandwidth shouldn't be a problem.
The "example" connection in RDC is listed as IP 192.168.255.255 which would be the broadcast address of a private IP range. This is a little annoying though a broadcast IP doesn't exist on this VPN connection. (At least not according to ifconfig ppp0) RDC doesn't seem wanting to connect to the braodcast or DSN, or mDNS or anything else but the remote computer's IP. Still leaves me confused.
I've seen quite a lot of info over the net of people using RDC over VPN connections, and my personal guess is, that I am not the first and only one to try this.
The system.log and console.log on the client (my PowerBook) stay empty. As far as I can tell, access is not restricted by either firewall.
Regards MacLemon
PowerBook G4 Mac OS X (10.4.3)
The exact Error message I get from MS-RDC Client is:
The client computer could not connect to the remote computer
Either remote connections are not enabled, the computer is too busy to accept new connections, or network problems are preventing your connection. Try connecting again later or contact your administrator.
I really like the clear and focused error message with a lot of possibilities...
Remote connections are enabled on the remote computer and that machine is definitely not too busy to accept new connections. Connecting at a later time doesn't help either which leaves me with the "network problems" and contacting my administrator. I am quite confident that I do not have problems with the network as I can use any other service over that VPN connection. My administrator, which I am myself, didn't have a solution for me yet. 🙂
Afaik MS-RDC only uses TCP port 3389, just like AFP uses TCP port 548. The difference is, that AFP works just fine, whereas RDC keeps telling me about not beeing able to connect. When physically connected to the network there RDC works just fine. I am connected over 3Mbit DSL, so bandwidth shouldn't be a problem.
The "example" connection in RDC is listed as IP 192.168.255.255 which would be the broadcast address of a private IP range. This is a little annoying though a broadcast IP doesn't exist on this VPN connection. (At least not according to ifconfig ppp0) RDC doesn't seem wanting to connect to the braodcast or DSN, or mDNS or anything else but the remote computer's IP. Still leaves me confused.
I've seen quite a lot of info over the net of people using RDC over VPN connections, and my personal guess is, that I am not the first and only one to try this.
The system.log and console.log on the client (my PowerBook) stay empty. As far as I can tell, access is not restricted by either firewall.
Regards MacLemon
PowerBook G4 Mac OS X (10.4.3)
