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

Terminal Services from internet

W've set up our Astaro box. I have a xp machine running Apache; no problem to connect it via the internet.
Now we want to start a remote desktop connection via the desktopclient from MS. No connection, although there is a service rule:
wTerServer tcp 1024:65535 3389.
There is also a NAT rule. What is going wrong? Something forgotten? [:S]

This thread was automatically locked due to age.

0 ReD-MaN over 22 years ago

Did you create a packet filter rule to allow this?
Cancel
Vote Up 0 Vote Down

Cancel
0 lancelot over 22 years ago in reply to ReD-MaN

Yes, with no restrictions at all....
Cancel
Vote Up 0 Vote Down

Cancel
0 Dean over 22 years ago

Did you try to telnet to port 3389 from the RDP client to see if you can at least connect to 3389? (http://support.microsoft.com/default.aspx?scid=kb;en-us;187628)

It isn't clear to me what you mean by no connection.

Microsoft has another article on troubleshooting RDP client problems, although some of it is very basic and you probably tried most/all of it:

http://support.microsoft.com/default.aspx?scid=kb;en-us;186645

What is the NAT rule?
Cancel
Vote Up 0 Vote Down

Cancel
0 lancelot over 22 years ago in reply to Dean

1. We have created a service wTerserver with the following entries:
wTerServer tcp 0:65535 3389
2. The NAT rules says:
From Any > outher-interface / wTerServer > SRC translation = None, DST translation MyPC

Again, connecting via a http://ipnr connection is no problem:
XP-webserver Any -> buiten_Interface__ / HTTP None Amamus

So the problem must be the service rule...?
Cancel
Vote Up 0 Vote Down

Cancel
0 Matjaz over 22 years ago in reply to lancelot

Lancelot!

In my opinion you will have to make also SNAT translation for packets, which are comming from your internal PC to the public NetWork.

From MyPC > any > SRC translation = outher-interface / wTerServer , DST none

BR, Matjaz
Cancel
Vote Up 0 Vote Down

Cancel
0 lancelot over 22 years ago in reply to Matjaz

Als antwoord op:

Lancelot!

In my opinion you will have to make also SNAT translation for packets, which are comming from your internal PC to the public NetWork.

From MyPC > any > SRC translation = outher-interface / wTerServer , DST none

BR, Matjaz

[/ QUOTE ]
You mean from the XP machine (=MyPC/Amamus) where to i need to connect?
So:
Name  Match parameters   SRC translation  DST translation
XP-Internet   Amamus -> Any / wTerServer   Any   Any

This is not working: The client could not connect to the remote computer... [:(]
Is there nobody with experiences with the RDP client?
Cancel
Vote Up 0 Vote Down

Cancel
0 Rudy over 22 years ago in reply to lancelot

In this NAT rule, also specify SRC Translation = Internal_interface. Please let me know if its working !

Succes,
Rudy
Cancel
Vote Up 0 Vote Down

Cancel
0 Chris Lynch over 22 years ago in reply to lancelot

You are attempting an RDP connection to an XP machine. Have you enabled Remote Desktop Connection on the machine? What happens if you attempt a TELNET connection to 3389 to the XP machine from another machine on the same subnet?

Also, what does your packet filter look like again?
Cancel
Vote Up 0 Vote Down

Cancel
0 LoosInt over 22 years ago in reply to Chris Lynch

Good Morning,

Did you enter the IP-Adress or the name of your server in the RDP-Connection window ? (maythe name-translation is not working).
What about your Filterrules in VPN-Configuration ?
Autopacketfilter on or off ?
Try to change the Autopacketfilter to on (just to exclude a manual packetfilter mistake)

Greetings
Thomas
Cancel
Vote Up 0 Vote Down

Cancel
0 techno.kid over 22 years ago in reply to lancelot

What´s about the default route of your TS? Does it point to the ASL?
AND: do what Chris Lynch told you - check if you can connect localy

techno.kid
Cancel
Vote Up 0 Vote Down

Cancel