ISA 2006 vs Exchange 2007 RPC

I have an ISA server which is not in the domain, and rules were created for OWA works perfectly with the certificate, the drama is that the autodiscover as rpcproxy not work because the ISA blocks it. was tested for that opening all traffic that even so it blocks (An HTTP 403 Was Received Because ISA denied the URL Specified) reading and reading it appears that the ISA must be within the domain for this to work so is this true? Or is there any way to make standalone. Any other information would be really helpful.

he recommendation we have is to put your ISA within the domain so that everything works properly and to create a better compatibility of your applications. You can put your ISA Server in your domain? And suppose unfortunately you can place the ISA in the domain as the company is very large and a change of this magnitude is complicated, then you can not do what you want with your current environment. :no: To assist protect your Exchange 2007 deployment, you can make use of firewall hardware and software explanations. You should use a higher firewall server such as Exchange 2007 with ISA Server 2006, since the two products are premeditated to work mutually and to help protect and augment client access.

ISA Server 2006 is the security gateway that facilitates protects your mission-critical applications from Internet-based intimidation. ISA Server enables your business to do more, with protected access to Microsoft applications and data. Secure your Microsoft application communications by protecting your corporate applications, services, and data across all network layers with stateful packet examination, application-layer filtering and inclusive publishing tools. Streamline your network administrator and user Experiences with simplify through a unified firewall and virtual private network (VPN) structural design. Safeguard your information technology environment to diminish security-risks and costs, and help eradicate the effects that have attackers and malicious software on your business.

Is the most recent Microsoft Exchange 2007 messaging and association server software product that runs on servers. With Exchange 2007, you can send and receive electronic mail and additional forms of interactive communication through computer networks. Designed to interoperate with a software client application such as Microsoft Office Outlook, Exchange 2007 also interoperates with Outlook Express and other e-mail client applications. E-mail messages are sent through what is commonly received and referred to as a client device Such as a personal computer, workstation, or a mobile device Including mobile phones or Pocket PCs. Typically the client connects to a network of Centralized computer systems comprised of servers or mainframe computers where the e-mail mailboxes are stored. The Centralized e-mail servers connect to the Internet and private networks where, and email messages are sent to and Received from other e-mail users. Also Exchange 2007 enables companies to send and receive Internet e-mail messages.

When somebody on the Internet needs to send e-mail messages to an employee in your company, all the sender has is the employee's e-mail address, for example, emp@techarena.com. When the e-mail message is sent to emp@techarena.com, the sender's e-mail program or e-mail server needs to find out where to send the message for the Requested domain, in this case, techarena.com. This is done by inquiring the Domain Name System (DNS) for the mail exchange (MX) record for techarena.com. The MX record is an extraordinary type of resource record in DNS Specifying a host record of servers accepting incoming e-mail messages for the domain. To receive e-mail messages from the Internet, a domain should have at least one MX record, but may have multiple MX records to supply fault forbearance. The DNS server will return all listed MX records for a domain, and the e-mail client will endeavor to launch an SMTP connection using the listed MX records, in preference order. The MX record points to the A record, which points to the IP address of the SMTP server. The following necessities must be met before publishing your SMTP server:

• Create an A record and point the A record to the external IP address of the ISA Server computer.
• Create an MX record pointing to the A record.

After you configure inbound Internet e-mail, the subsequently step is to configure outbound e-mail message traffic from your association to be sent to the Internet through ISA Server. Characteristically, you have one Exchange 2007 server configured to send e-mail messages to the Internet via the SMTP protocol. Normally this is an Exchange 2007 server with the Hub Transport or Edge Transport server role installed. In this scenario, the Hub Transport or Edge Transport server Accepts SMTP requests from the additional Exchange servers in your organization and promotes the requests to the suitable mail server on the Internet. The Hub Transport or Edge Transport server requires being able to create SMTP sessions to mail servers on the Internet. Furthermore, the Hub Transport or Edge Transport server must be able to Perform DNS queries to find the MX record for the domain to the e-mail message which is being sent.