Problem getting to different FTP sites...
Hello Clutch and the gang. . . We are having a problem accessing 2 seperate FTP sites on our server. The server has 2 IP's: 192. 168. 0. 10 and 192. 168. 0. 30. The main FTP site is where any user can copy and paste into, or download from.
Hello Clutch and the gang...We are having a problem accessing 2 seperate FTP sites on our server. The server has 2 IP's: 192.168.0.10 and 192.168.0.30.
The main FTP site is where any user can copy and paste into, or download from. In IIS, its IP is set to 'All unassigned'.
The second FTP site is where all of the downloads from our main webpage come from. In IIS, its IP is set to 192.168.0.30. No one has access to paste, copy, or cut from this site....except the administrator.
The problem is, when a user types ftp://shella into their address bar, it takes them to the second site, which is the incorrect FTP site.
The only way to get to the main FTP site (ftp://shella) is to type in ftp://192.168.0.10.
I have checked all of the static mappings, DNS settings, and host headers names...and everything seems to be correct. I even tryed assigning the main FTP site to 192.168.0.10, instead of 'All unassigned'.....but that didn't work either.
Clutch, I know you told me how to do this when we talked, but Im pretty positive I did it exactly as you told me. But for some reason, ftp://shella is going to the second ftp site...which sucks for everyone who needs to put something up on the server because it takes them to the second ftp site where they do not have access to paste.
Please help if you can...ThanX in advance !!
Klark...
The main FTP site is where any user can copy and paste into, or download from. In IIS, its IP is set to 'All unassigned'.
The second FTP site is where all of the downloads from our main webpage come from. In IIS, its IP is set to 192.168.0.30. No one has access to paste, copy, or cut from this site....except the administrator.
The problem is, when a user types ftp://shella into their address bar, it takes them to the second site, which is the incorrect FTP site.
The only way to get to the main FTP site (ftp://shella) is to type in ftp://192.168.0.10.
I have checked all of the static mappings, DNS settings, and host headers names...and everything seems to be correct. I even tryed assigning the main FTP site to 192.168.0.10, instead of 'All unassigned'.....but that didn't work either.
Clutch, I know you told me how to do this when we talked, but Im pretty positive I did it exactly as you told me. But for some reason, ftp://shella is going to the second ftp site...which sucks for everyone who needs to put something up on the server because it takes them to the second ftp site where they do not have access to paste.
Please help if you can...ThanX in advance !!
Klark...
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
For FTP, it's easiest to just change the port that it's hosting on for your other FTP sites so clients can connect to many of them on the same server. However, if you are looking to keep them on port 21, then you will have to disable socket pooling. I have consolidated a couple of the MSKB articles so that you can just focus on disabling socket pooling for the FTP service and then be able to bind multiple FTP site to their respective IPs on the same NIC.
To ensure that IIS only listens on a selected interface, you must disable the Socket Pooling feature and configure the FTP server to listen on a specific Internet Protocol (IP) address:
To disable the Socket Pooling feature for the FTP service, run the following commands:
1. At a command prompt, change to the \Inetpub\Adminscripts\ folder.
2. At a command prompt, type: cscript adsutil.vbs set msftpsvc/disablesocketpooling true , and then press ENTER.
3. Restart the Iisadmin service for the change to take effect. At a command prompt, type: net stop iisadmin
4. Start all of the services that had been running in Inetinfo.
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
Q238131 How to Disable Socket Pooling
Configure the FTP server to listen only on the internal interface:
1. Open the Internet Services Manager, and then expand the Computername settings.
2. Click Default FTP Site , and then right-click it.
3. On the menu, click Properties , and then click the FTP Site tab.
4. In the Identification section, click IP Address .
5. Change the IP address from "All Unassigned" to the IP address of the internal interface of the FTP Server.
6. Click OK .
7. Close IIS in Microsoft Management Console (MMC).
To ensure that IIS only listens on a selected interface, you must disable the Socket Pooling feature and configure the FTP server to listen on a specific Internet Protocol (IP) address:
To disable the Socket Pooling feature for the FTP service, run the following commands:
1. At a command prompt, change to the \Inetpub\Adminscripts\ folder.
2. At a command prompt, type: cscript adsutil.vbs set msftpsvc/disablesocketpooling true , and then press ENTER.
3. Restart the Iisadmin service for the change to take effect. At a command prompt, type: net stop iisadmin
4. Start all of the services that had been running in Inetinfo.
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
Q238131 How to Disable Socket Pooling
Configure the FTP server to listen only on the internal interface:
1. Open the Internet Services Manager, and then expand the Computername settings.
2. Click Default FTP Site , and then right-click it.
3. On the menu, click Properties , and then click the FTP Site tab.
4. In the Identification section, click IP Address .
5. Change the IP address from "All Unassigned" to the IP address of the internal interface of the FTP Server.
6. Click OK .
7. Close IIS in Microsoft Management Console (MMC).
