ailya1960
Junior Member | Редактировать | Профиль | Сообщение | Цитировать | Сообщить модератору
hardhearted
Это точно?
вот что нашел
http://www.microsoft.com/technet/isa/2006/deployment/publishing_concepts.mspx
Server publishing allows virtually any computer on your Internal network to publish to the Internet. Security is not compromised because all incoming requests and outgoing responses pass through ISA Server. When a server is published by an ISA Server computer, the IP addresses that are published are actually the IP addresses of the ISA Server computer. Users who request objects assume that they are communicating with the ISA Server computer—whose name or IP address they specify when requesting the object—while they are actually requesting the information from the publishing server. This is true when the network on which the published server is located has a network address translation (NAT) relationship from the network on which the clients accessing the published server are located. When you configure a route network relationship, the clients use the actual IP address of the published server to access it.
When a route relationship is configured between networks, either a server publishing or access rule can be used. Specifically, when the following conditions are true, access rules and server publishing rules have identical functionality:
• A route relationship exists between the source and destination IP addresses.
• No port translation (forwarding) is needed.
• The protocol has no application filter.
• Network Load Balancing (NLB) is not used, or the number of possible clients is negligible.
И вот:
Address translation
When the network relationship is defined as NAT, the client connects to the ISA Server external address. The published server receives the packet from a source address of either the client or the ISA Server internal address, depending on how you configure the publishing rule. The default setting for server publishing rules is that the published server receives the client address. The default setting for Web publishing rules is that the published server receives the ISA Server internal address.
When the network relationship is defined as route, the client connects directly to the server. The published server will receive the packet from the client address. However, for Web publishing rules (only when publishing HTTP), you can configure whether the published server should receive the ISA Server internal address.
|
Так что вам и публикация как бы не к чему (а между сетями у вас внутри стоит route, это ваш сервак надо публиковать на первой исе) 
((( 
