I have a Server running Windows Server 2003 R1 I'll call Server 'A' connected via LAN to another Server running Windows Server 2003 Standard I'll call Server 'B'. I've set up a ftp site thru the IIS console on Server 'A'. From Server 'A' I can connect, to the internet and am able to access the ftp site. When I go to a client computer to try to access the ftp site I cannot. Server 'A' use to be the network server at another office and Server 'B' is our DHCP Server at this office. I cannot figure out, nor am I sure that it has to be done, how to connect Server 'A' to Server 'B' to make Server 'A' a client computer to Server 'B'. I've opened ports 20 and 21 on our router, checked to see if there is a firewall running on Server 'A' and there is no, given Server 'A' a static ip address and used the ip port from my isp that I am using as my ftp address as my alternet dns server. I've connected Server 'A' directly to our router and still a client computer cannot connect. I've checked ports 20 and 21 on our hardware firewall using software I found on the internet and supposedly those ports are open. I'm a newbie and don't know much about ftp but it is supposed to be easy. Do I have to make Server 'A' a client to Server 'B' and if so, how? Is there a setting on Server 'A' that I am missing? I would rather use the ftp setup from Windows Server 2003 Standard R1 than a third party software such as Filezilla, etc. Can anybody point me in the right direction? Do you need any more facts than what I've given you? The reason I am using Server 'A' is because of the harddrive space I need for the ftp site that Server 'B' does not have available. I'm sorry for the long post, but I have been beating my head against the wall trying to figure it out. I've added virtual ftp directories so clients will only be able to log into their folders via a user name and password. Any help would be appreciated, but please remember I am a newbie.
↧