Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Windows Terminal Server port forwarding

Status
Not open for further replies.

Cjbuechler

IS-IT--Management
Dec 12, 2001
19
0
0
US
Hi,

I'm sorry to start another thread on port forwarding but I'm a little confused by the other threads I've read on this matter but I'm sure I'm just missing something simple...

I have an internal server running terminal services (192.168.1.249)
I have a single router (PIX 506E) with an internal address of 192.168.1.1 and exterior of something like 66.195.196.114.

How do I allow access from any host coming from outside to that server on port 3389?

I tried the following with no sucess:
static (inside,outside) tcp 66.195.196.114 3389 192.168.1.249 3389 netmask 255.255.255.255 0 0
access-list 101 permit tcp any host 66.195.196.114 eq 3889
access-group 101 in interface outside

Once I looked in the PDM the rule appears to allow access FROM the server out and not the other way around. Did I mix up the order?

Here is the config before I made the changes (I've since wiped those changes):
PIX Version 6.3(3)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password YL.QT.2ao6ZdmINq encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname SBPIX
domain-name PIM2002
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
object-group service TerminalServices tcp-udp
description Windows Terminal Services
port-object range 3389 3389
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside 66.193.198.111 255.255.255.0
ip address inside 192.168.1.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
route outside 0.0.0.0 0.0.0.0 66.193.198.1 1
timeout xlate 0:05:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
aaa-server LOCAL protocol local
http server enable
http 192.168.1.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd address 192.168.1.2-192.168.1.254 inside
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
terminal width 80
 
Never mind. I tried to put it in again and this time it worked.

 
dont use 101 in your access list try this

access-list fromoutsite permit tcp any host x.x.x.x eq 3389
access-group fromoutside in interface outside
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top