PIX501: configuring Service object for Remote Desktop/Polycom/Custom PcAnywhere?

My current following settings are working good for Remote Desktop and Web:

access-list outside_access_in permit tcp any interface outside eq 5451
access-list outside_access_in permit tcp any interface outside eq 5452
access-list outside_access_in permit tcp any interface outside eq 5455
access-list nonat permit ip 192.168.100.0 255.255.255.0 192.168.101.0 255.255.255.0

static (inside,outside) tcp interface 5451 192.168.100.6 www netmask 255.255.255.255 0 0
static (inside,outside) tcp interface 5452 192.168.100.6 3389 netmask 255.255.255.255 0 0
static (inside,outside) tcp interface 5455 192.168.100.8 www netmask 255.255.255.255 0 0

Actually I am trying to utilize the object service to setup firewall for remote desktop at first and later for other applications like polycom and custom applications I have done this in Netscreen products but I am new to Cisco.

In above setup Windows XP Remote Desktop to 141.157.233.104:5452  is working fine but why not in the following senario when I try to implement services?

 object-group service RmDskTp tcp
 description Remote Desk Top
 port-object range 3389 3389
 access-list outside_access_in permit tcp any object-group RmDskTp interface outside object-group RmDskTp

Or how can I make custom services say PC101Any for following?

access-list outside_access_in permit tcp any interface outside eq 5634
access-list outside_access_in permit udp any interface outside eq 5635
static (inside,outside) tcp interface 5634 192.168.100.8 5634 netmask 255.255.255.255 0 0
static (inside,outside) udp interface 5635 192.168.100.8 5635 netmask 255.255.255.255 0 0

thanks,

faruqi
sfaruqiAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

grbladesCommented:
> access-list outside_access_in permit tcp any object-group RmDskTp interface outside object-group RmDskTp
This will allow only traffic coming from a port listed in the object group and going to a port in the object group. Normally when a client establishes a connection it establishes it from a high port number (>1023) so you cannot normally use this in access lists except for specific protocol such as DNS. Therefore I suggest you change the line to the following and try it again:-
access-list outside_access_in permit tcp any  interface outside object-group RmDskTp
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Software Firewalls

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.