Cannot access out FTP server from any workstation 2

[DawnP]

I have an FTP server on Windows 2000 Server O/S that nobody can access from any workstation in the company.
We just recently relocated our company, and am not sure if it worked after the relocation. We did get new external IP address' for this location, but all internal remained the same so not sure if that has anything to do with it or not.
Yesterday I couldn't even get on the internet from the FTP server, and it was only sending packets and not receiving.
Today I changed the slot on the motherboard that the network card was in, and now I can get on the internet, and am sending and receiving packets, but still cannot FTP to it. The error message I'm getting is, "FTP folder error. Windows cannot access this folder. Make sure you typed the file name correctly and that you have permission to access the folder. Details: The operation timed out." I'm thinking it had more than one problem. Any suggestions on how to troubleshoot this?

 

[burtsbees]

Well, is it there under C:\inetpub\ftproot? Also, check that none of the settings "magically" changed under Control Panel-->Administrative Tools-->Internet Information Services-->FTP sites Right click the default or whatever you named it, then properties). When I say "magically" changed, I am not being sarcastic!

Burt

 

[AndyPunt]

The thing you mentioned about the moving of the network card was pretty strange, which makes me wonder if it is at the physical layer. I don't know if you tried this yet, but try these from the FTP server machine:
1) ping localhost
2) ping gateway
3) ping

http://www.tek-tips.com

4) browse internal network (My Network Places)
5) ftping from the ftp server to itself

If all that works, try this from another machine:
1) telnet "ftp server address" 21

These steps should help determine if it is a network problem or a application problem.

 

[burtsbees]

Also, what device is doing the routing? Is the static NAT statement (if any) still in place?

Burt

 

[DawnP]

In reponse to your first burt yes, it is there under ftproot. As far as the settings, under Admistrative Tools I don't have Internet Information Services, but I do have an Internet Services Manager. When I try to click on it though it says "MMC cannot open the selected file". Trying other suggestions now all.

 

[DawnP]

Andy,
1) localhost replies
2) gateway times out
3)

http://www.tek-tips.com

replies
4) am able to browse network
5) same result as from all workstations. Doesn't work.

 

[DawnP]

Burt,
Not sure what device is doing the routing. Can you give more detail? Not sure how to check the static NAT.

Dawn

 

[burtsbees]

What is the gateway, as shown from
C:\ipconfig /all
on all machines not working? Are the IP address, mask, gateway and DNS servers dynamically or statically assigned? If you cannot ping the gateway, it could be a router not allowing echo replies, or a Windows server with Windows Firewall on it, or even some other firewall. Find out what device resides at the IP address the workstations and FTP server report it is.
Static (or dynamic for that matter) NAT allows you to get back and forth, to and from the internet from your network behind your gateway/router, so this does not sound like the issue.

Burt

 

[AndyPunt]

If the mmc isn't working, the IIS/FTP might have been uninstalled:

1) Check to see if the FTP Service is still configured
- Start | Settings | Control Panel | Add/Remove Programs
- Add/Remove Windows Components
- In the Windows Component Wizard, click Internet Information Services | Details
- Ensure Fil Transfer Protocol (FTP) Server is selected
If not, then you need to reconfigure the FTP service. Unless, you are not using the Windows FTP service and a third party application. If that is the case, then you need to verify what that is.

2) Try and see if the FTP Service is started from Computer Management
- Right-click My Computer | Manage
- In the Computer Management windows, expand Services and Applications, then Internet Information Services
- Right click the FTP site and Start should be greyed out
If it is not, the FTP service is not started, so click start. If you don't see Internet Information Service under the Services section, you need to install the MMC

I hope this helps...

 

[DawnP]

Burt,
The gateway that is shown when I do ipconfig /all from my FTP server is that of my firewall.
Yes, all machines are not working. IP, mask, gateway and DNS servers all all statically assigned. When I ping gateway from my workstations and FTP server, although it times out, it shows the IP address of the company that hosts my domain name.

 

[DawnP]

Andy,
File Transfer Protocol was selected in the Internet Information Services.
Also
The FTP site was already started under Internet Information Services, yes.

 

[burtsbees]

Can you telnet into your firewall from the FTP server?

Burt

 

[DawnP]

When I try to telenet from my FTP server to my firewall I get this message: "Could not open a connection to host on port 23 : connect failed

 

[burtsbees]

I don't know why I got off track, but pinging the gateway is not the problem...since the ftp server can get out, the gateway is obviously letting packets out and back in. However, since this is the gateway, it may still be blocking port 21, or whatever you may be using for FTP. When you say that nobody in the company can FTP to it...first off, is this company all in one building? Did you have it set up where people can FTP to it from the internet (using the public IP address, rather than any private IP within the company)? I imagine anyone can still ping it from anywhere, since you can browse the network from the FTP server. It boils down to 2 possible things, from what I can see...either the FTP port is being blocked (sometimes when people have multiple FTP servers on the same network, they use port 21 for one, and maybe port 2121 for another, and this may involve port mapping configurations in the gateway device), OR the Windows set up is messed up---if you sneeze too loud, sometimes Windows applications crash and stop working. In other words, back up the FTP files, and delete the FTP server configuration and re-configure it. In the properties of the ftp services in Windows, you could check what port you tell it to use, what windows profile, where to write the ftp logs, etc.

Burt

 

[AndyPunt]

Dawn, I believe you have some kind of firewall on the FTP server enabled. This could be something like Norton Client Security or another security bundle. If that is the case, you need to look through the documentation to create exceptions.

 

[DawnP]

Burt,
I've checked, and port 21 (which is the port we're using) is not being blocked. The company is yes, all in one building, I have it set up that people can use the public and private IP address over the internet. People from outside the company as well (it's not working for them either).

Andy,
I've checked, and there's no other firewall installed on the actual FTP server.

 

[burtsbees]

I can't remember how to check this in 2000, but is it set up as an anonymous FTP?

Burt

 

[DawnP]

allow anonymous" is not checked. Should it be?

 

[burtsbees]

Yes, if you want anonymous connections. You can also control read only, read/write, etc, and who controls the password. The way I have always set mine up is to allow anonymous connections, set up an account for ftpusers, password protect it, and specify that account in "username" box, and allow IIS to control password, and I don't check "allow ONLY anonymous connections".

Burt

 

[DawnP]

Well thanks for all your help. I finally figured it out.

While troubleshooting I identified that the IP Configuration on the FTP server was incorrect.

It was on the wrong subnet.