Oh damn, It is a http://www.hotbrick.com/produto.asp?tipo=2&codPro=22 . Do you think I am out of luck achieving this? One more thing, after doing the registry settings I couldn't connect to exchange from von which I used too. So I deleted the reg key and restarted exchange system attendant and it fine for now. Any idea? Ara Avvali Boss Audio Systems Phone: (805)988-0192 Ext 276 Email: ara.avvali@xxxxxxxxxxxxx <mailto:ara.avvali@xxxxxxxxxxxxx> ________________________________ From: Thomas W Shinder [mailto:tshinder@xxxxxxxxxxx] Sent: Sunday, November 13, 2005 4:49 PM To: [ISAserver.org Discussion List] Subject: [isalist] RE: Enabling Full Outlook Client Access Anywhere using the ISA Firewall's Secure Exchange RPC Filter http://www.ISAserver.org Hi Ara, If the ISA firewall is behind a NAT device, you're at the mercy of the intelligence (or lack thereof) of that devices RPC awareness. Unless you're using a front end ISA firewall, its probably no more intelligent than a mere PIX, which means, not much. HTH, Tom Thomas W Shinder, M.D. Site: www.isaserver.org <http://www.isaserver.org/> Blog: http://spaces.msn.com/members/drisa/ Book: http://tinyurl.com/3xqb7 <http://tinyurl.com/3xqb7> MVP -- ISA Firewalls **Who is John Galt?** ________________________________ From: Ara Avvali [mailto:ara.avvali@xxxxxxxxxxxxx] Sent: Sunday, November 13, 2005 4:31 PM To: [ISAserver.org Discussion List] Subject: [isalist] Enabling Full Outlook Client Access Anywhere using the ISA Firewall's Secure Exchange RPC Filter http://www.ISAserver.org Dear Tom, Following your wonderful article posted on http://isaserver.org/pages/article_p.asp?id=1325 1. I have checked to see if my isp block port 135. when I type the telnet <ip> 135 I get a response back so it should be fine 2. ISA is behind a nat device, so I forwarded tcp 135 to external face of ISA 3. did what you suggested for adding registry key to exchange and restarted IIS admin service and exchange system attendant which restarted depending services too 4. created the exchange rpc rule 5. Created an outlook profile, but every time I load the outlook I get the connection to Microsoft exchange server is unavailable. Outlook must be online or connected to complete this action 6. I monitor ISA logs from my home ip address and the only thing shows up is ISA - TCP - - 3647 63 0 228 0x80074e24 0x0 0x0 Firewall 11/13/2005 2:16:12 PM 192.168.0.11 135 Exchange RPC Server Closed Connection Inbound Exchange RPC External Internal - - There is no initiated connection. Only closed. 7. it is outlook 2003 sp2 on xp sp2 connecting to exchange sp2 behind isa 2004 sp1 both on server 2003 sp1 Thank you for help. If anyone else got a suggestion I would appreciate it ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Visit TechGenix.com for more information about our other sites: http://www.techgenix.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: tshinder@xxxxxxxxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report abuse to listadmin@xxxxxxxxxxxxx All mail to and from this domain is GFI-scanned. ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Visit TechGenix.com for more information about our other sites: http://www.techgenix.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: ara.avvali@xxxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report abuse to listadmin@xxxxxxxxxxxxx