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 client > firewall > Win2k server issue

I currently have a good Masq, DNAT setup working with FTP, HTTP services.

My HTTP, FTP works and points to my Win2k box which is back behind my ASL firewall. I am trying to get external terminal server clients to dial in to the win2k box. The only PORT you have to open is 3389 TCP/UDP (both yes). but it doesnt work it wont connect to the win2k box. I know its not a bad filter, or dnat rule I have checked all that. Plus I have 2 ASL boxes im testing and they BOTH do the same thing.

Anyone got my setup and have this working? Let me know

Thanks
Resistance

This thread was automatically locked due to age.

0 Orjan Sandland over 23 years ago

Sorry for not being able to help out on this one. I had WTS working at a time, but I'm not sure how I did that. Tried searching for terminal server on these boards?

The reason I don't use WTS through my ASL anymore, is because I set up an SSH tunnel from external clients to an SSH server behind ASL, then I instruct the terminal server client to connect to localhost on the external clients.

Works wonders, and it is even secure :-)

Ørjan
Cancel
Vote Up 0 Vote Down

Cancel
0 Doug Vandemark over 23 years ago in reply to Orjan Sandland

I had a small problem with getting WTS setup with ASL, but I figured it out after comparing my service with the static ones. Define your server. Define your WTS D-port/Server as 3389 and S-port/Client as 1024:65535. tcp/udp for protocol. Without the 1024:65535 range on S-port, you will get SYN on your packet filter.

If this does not help you, feel free to send me a message and I will help you the best I can.
Cancel
Vote Up 0 Vote Down

Cancel
0 Resistance over 23 years ago in reply to Doug Vandemark

Thanks Doug Vandemark

It works I had the S-Port set to 3389 thanks a LOT!

Resistance
Cancel
Vote Up 0 Vote Down

Cancel