I'm sitting with an mysterious issue with regards to publishing the FTP server through my ISA Server 2006. The ISA server is configured as Single network adapter. Server has only one Network card no External Interface. I managed to Publish my OWA and Outlook Anywhere through this and it is working fine.
Firewall is configured (Public IP) to accept any connections through port 21, 22 and 20 and it will forward it into the ISA server.
FTP Server is configured on a windows 2008 R2 box and FTP connection is working fine internally.
Any Idea what could be the issue?
Mathew
_____________________________
Systems Administrator EHL Management Service U.A.E
Thank you for the reply, I've created a server publishing rule in ISA by selecting the FTP server and the destination as my FTP server. However it doesn't communicate or connect. I tried telnet this Address through port 21 and doesn't work, but the same address I telnet through port 443 (used for OWA) and it worked.
No clue what to be done, requirement is urgent and the requester is CEO, guys please throw some lights on this.
Mathew
_____________________________
Systems Administrator EHL Management Service U.A.E
Posts: 3472
Joined: 3.Jan.2008
From: Amazon, Brazil
Status: offline
Hi,
have you used a non-web server publishing rule or a web server publishing rule? As said before, single NIC has a number of limitations:
quote:
Configuring ISA Server with a Single Network Adapter Configuration Problem: There are a number of issues associated with the configuration of ISA Server on a computer with a single network adapter. Cause: The causes include:
Multi-network firewall policy. In single network adapter mode, ISA Server recognizes itself (the Local Host network). Everything else is recognized as the Internal network. There is no concept of an External network. The Microsoft Firewall service and application filters operate only in the context of the Local Host network. (ISA Server protects itself no matter what network template is applied.) Because the Firewall service and application filters operate in the context of the Local Host network, you can use access rules to allow non-Web protocols to the ISA Server computer. This has implications for running applications located on the ISA Server computer.
Application layer inspection. Application level filtering does not function, except for Web Proxy Filter for Hypertext Transfer Protocol (HTTP), Secure HTTP (HTTPS), and File Transfer Protocol (FTP) over HTTP.
Server publishing. Server publishing is not supported. Because there is no separation of Internal and External networks, ISA Server cannot provide the NAT functionality required in a server publishing scenario.
Firewall clients. The Firewall Client application handles requests from Winsock applications that use the Firewall service. In a single network adapter environment, this service is only available in the context of the Local Host network (protecting the ISA Server computer), and Firewall Client requests are not supported.
SecureNAT clients. SecureNAT clients use ISA Server as a router to the Internet, and SecureNAT client requests are handled by the Firewall service. In a single network adapter environment, this service is only available in the context of the Local Host network (protecting the ISA Server computer), and SecureNAT client requests are not supported.
Virtual private networking. Site-to-site virtual private networks (VPNs) are not supported in a single network adapter scenario. Remote client VPN access is supported in a single network adapter scenario.
I understand the limitation of Single network adapter, However you mentioned i've to use Web Server publishing rule to publish FTP. Do you have guide to do this? Or can you please help me in configuring this?
Mathew
_____________________________
Systems Administrator EHL Management Service U.A.E
Server publishing is not supported. Because there is no separation of Internal and External networks, ISA Server cannot provide the NAT functionality required in a server publishing scenario.