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!

Terminal service access problem

Status
Not open for further replies.

ciscoric

IS-IT--Management
Jan 20, 2003
17
0
0
US
I am trying to get Terminal Service set up for web access. I can reach the tsweb portion from inside of the network. I need to allow web access to this server also.

I have a cisco 1760 router and with T-1 access. I also have a watchguard 700 firewall.

I assume I am not even reaching the firewall because I don't get any denies. I am guessing that it is on the router.

Here is my config... Can someone PLEASE help?

TIA

!
ip subnet-zero
!
!
no ip domain-lookup
!
!
!
!
!
!
!
!
controller T1 0/0
framing esf
linecode b8zs
channel-group 0 timeslots 1-24
!
!
!
interface FastEthernet0/0
description Connection to LAN
ip address x.x.x.180 255.255.255.240
ip nat inside
no ip route-cache
no ip mroute-cache
speed auto
!
interface Serial0/0:0
bandwidth 1536
no ip address
ip nat inside
encapsulation frame-relay IETF
no ip route-cache
!
interface Serial0/0:0.1 point-to-point
ip address x.x.x.x 255.255.255.252
ip nat outside
no ip route-cache
frame-relay interface-dlci 500
!
router rip
version 2
network 65.0.0.0
network 192.168.111.0
no auto-summary
!
ip nat pool internet x.x.x.177 x.x.x.190 netmask 255.255.255.0
ip nat inside source list 10 pool internet overload
ip nat inside source static tcp 192.168.111.2 1494 x.x.x.179 1494 extendabl
e
ip nat inside source static tcp 192.168.111.2 3389 x.x.x.179 3389 extendabl
e
ip nat inside source static tcp 192.168.111.2 80 x.x.x.179 80 extendable
ip classless
ip route 0.0.0.0 0.0.0.0 x.x.x.x
ip route 192.168.111.0 255.255.255.0 x.x.x.180
no ip http server
!
!
snmp-server community public RO
 
Hey I'm not sure what role your Watchguard firewall is playing, because typically the firewall would handle the NAT or static mappings. In the Watchguard you would configure the common service, and if it's not there configure a custom service. Also in most cases your firewall would be the default gateway for internal network, and the external interface on the firewall would connect to your internet router. Also are you trying to configure Terminal services or Citrix (NFUSE) from the outside (internet)? If it's Citrix, than you don't need port 3389 (rdp), if it's Terminal Service (remote desktop), then you don't need port 1494 (ica). I think you have quite a few things to do before you get it working. Also, it's easier to test a static mapping by just doing an ip mapping first. If the services then works, then you can reconfigure the static mappings to just the ports that are needed. Hopefully I understood your question correctly, and what I wrote makes sense to you. I am curious though to what role your Watchguard plays though. Feel free to write back.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top