andersjj_IL
asked on
Publishing FTP site on ISA 2006 on alternate port
I have ISA 2006 going to a win2k3 server. I was able to setup an ftp site quite easily on port 21. But, I need to have additional ftp sites on the same IP. I setup the second ftp server on the win2k3 server easily and got it running. I have different welcome messages for each ftp site, so I know for sure which one I'm hitting. I tried to publish the second ftp site on alternate port (currently using 99). In ISA, it's listening on port 99 and forwarding the requests to port 99 on the win2k3 server. In viewing the log file on my ftp client, I'm able to see that it's hitting the ftp site on port 99 for login and gets past that. When the ftp client tries to run the port command, I get "invalid port command", which is coming from the ISA server, not the win2k3 server. I checked the ftp logs on the server and can see the authentication requests getting through, but nothing about the invalid port command, which seems to be coming directly from ISA 2006 server.
Any ideas on what I need to do to allow this second ftp server on ISA 2006 to get past the invalid port command error?
Any ideas on what I need to do to allow this second ftp server on ISA 2006 to get past the invalid port command error?
ASKER
Did that, still getting error.
But, when I'm in the paramters tab off the properties button where I checked off the FTP Access filter, the "Primary connections" box is showing port 21, even though I'm trying to do this one on 99. There are three buttons to Add Remote or Edit, but they are all greyed out. Seems like I should be putting the 99 in there also, but it doesn't seem to be any way of doing that with the buttons.
But, when I'm in the paramters tab off the properties button where I checked off the FTP Access filter, the "Primary connections" box is showing port 21, even though I'm trying to do this one on 99. There are three buttons to Add Remote or Edit, but they are all greyed out. Seems like I should be putting the 99 in there also, but it doesn't seem to be any way of doing that with the buttons.
Please tell me that you did not do this to the original FTP Protocol packaged with ISA.
Never touch the original Protocols.
Create "new" protocols and work with them for special situations like this.
Create this:
Name: "FTP-99 Server"
Port Range: 99-99
Type: TCP
Direction: Inbound
Secondary Connections: None
Application Filters: FTP Access Filter
Never touch the original Protocols.
Create "new" protocols and work with them for special situations like this.
Create this:
Name: "FTP-99 Server"
Port Range: 99-99
Type: TCP
Direction: Inbound
Secondary Connections: None
Application Filters: FTP Access Filter
Ok, wait let's just start over. Delete the Publishig Rule and delete the protocol if you created one.
Do these,..in this order:
1. Create a new protocol
Name: "FTP-99 Server"
Port Range: 99-99
Type: TCP
Direction: Inbound
Secondary Connections: None
Application Filters: FTP Access Filter
2. Create a new Non-Web Server Publishing Rule
Name: "Publishing, FTP-99"
IP#: (the IP# of the FTP Server)
Protocol: "FTP-99 Server" (do not touch the Ports Button)
Listerner: External, Selected IP (IP# you want to use)
Do these,..in this order:
1. Create a new protocol
Name: "FTP-99 Server"
Port Range: 99-99
Type: TCP
Direction: Inbound
Secondary Connections: None
Application Filters: FTP Access Filter
2. Create a new Non-Web Server Publishing Rule
Name: "Publishing, FTP-99"
IP#: (the IP# of the FTP Server)
Protocol: "FTP-99 Server" (do not touch the Ports Button)
Listerner: External, Selected IP (IP# you want to use)
ASKER
hmmm....did that, still getting the same thing. The original ftp server works fine. I can hit the second ftp server internally fine, so it works without ISA. I looked in the alerts tab and got this...
Description: The server publishing rule FTP-99, which maps 192.168.5.98:99:TCP to 63.xx.xx.xx:99 for the protocol TCP-99, was unable to bind a socket for the server. The server publishing rule cannot be applied.
The failure is due to error: You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the computer name and try again.
I know all the servers on the network have a unique IP address, so not sure where the duplication would be. The original ftp site is on this server as well, so I would think I would get an alert for both ftp publishing rules or they would both work....
Description: The server publishing rule FTP-99, which maps 192.168.5.98:99:TCP to 63.xx.xx.xx:99 for the protocol TCP-99, was unable to bind a socket for the server. The server publishing rule cannot be applied.
The failure is due to error: You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the computer name and try again.
I know all the servers on the network have a unique IP address, so not sure where the duplication would be. The original ftp site is on this server as well, so I would think I would get an alert for both ftp publishing rules or they would both work....
I'd say that the Rule and the Protocol are fine. I think you have some kind of issue that is not related to ISA.
ASKER
Oh well, not sure what I"m doing wrong. I just put up a new public IP address on the ISA, put another private IP address on the ftp server, and just did it that way. I can use another public IP on the ISA anyway, so it's not such a big deal. That way I can just leave it on port 21 on the second public IP address...
Ok, sounds good.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Contrary to what many believe FTP is not a simple protocol,..it is fact a very complex protocol. Hence without the Application Filter "FTP Access Filter" the ISA cannot keep up with and maintain all the port juggling that happens within the protocol.
Go to the Publsihing Rule properties
Go to the Traffic Tab
With the Protocol showing in the dropdown, select the Properties button
Select the Parameters Tab
Down in the Application Filters section enable the FTP Access Filter by checking the checkbox.