Topic: MS Terminal Services

[steve]

Briefly, here is my situation:

Win98SE PC at home behind e-smith 4.12.
Use SecureRemote Client to connect to Checkpoint FW1 at work.

SecureRemote Works fine, but cannot use MS Terminal Services to get to Win2K Servers behind Checkpoint FW1.
After checking into the problem, It appears I need to allow TCP port 3389 thru my e-smith box
Tried adding a port forward entry with no success.
I know it is an issue with my e-smith box, as Terminal Services works thru SecureRemote on pc connected directly to Internet.

Anyone?!?!?!

Steve

[Tom Veitch]

Something like this below did the trick for me:

ipmasqadm portfw -a -P tcp -L 213.x.x.x 3389 -R 192.168.0.1 3389
ipmasqadm portfw -a -P udp -L 213.x.x.x 3389 -R 192.168.0.1 3389

maybe it can help you

[Ritchie Logan]

I played around with the TCP/UDP ports a while back to get 4.1.2 to allow an ipsec client to pass through.

Here's the link to the original post I made

http://forums.contribs.org/index.php?topic=1855.msg6169#msg6169

This explains exactly how to change your masq settings, but remaining compliant with the template structure. You'll need to edit / add an appropriate line for your TCP 3389 This would also be valid for SME5.

Ritchie