Trouble accessing ftp server internally

Hi,
Totally new to ftp servers and have been struggling for a couple of days now.

Got the server up, and you can access it externally... but not internally. I've set up a domain, with a static ip on it (The static ip provided by my ISP)

This then points to my router. I've made the servers ip static, set up port forwarding and put it in the DMZ.

The domain when used externally to the local network of the server works a treat. But inside that same domain throws up an error.

Could it be that i've set the static ip of the server to something stupid? ie. i've got it set to 192.168.1.2. The router is 192.168.1.1 (internally)

I appreciate any help, cheers

You wouldn't expect this to work. If the domain points to your external IP address you can only use this domain name from outside of the local network. Either you need to connect to the server using its internal IP address (192.168.1.2) or setup a local DNS server to resolve the domain name to 192.168.1.2 (rather than the external static IP address). Alternatively, a new line in your hosts file would work.

Hi! Thanks for that, seems to be working fine.

I've got a new problem, users are complaining of timeouts (more frequently than is acceptable)

What are the main reasons for timeouts?

Thanks.

I'm not sure. I did have one issue recently where the local FTP server was doing a reverse DNS lookup and ident lookup for every client that connected. Since there was no local DNS server this caused quite considerable delays. Disabling these two checks speeded things up. Perhaps it's related to something like this.

Since this is in your home, what is the bandwidth that you have available? Note that even if you have 6 megabit connection, the upload speed is typically still a couple of hundred kilobits. This then is the download speed for all the clients connecting to your server.

What does your server typcially do - just sit there and serve the clients? how about the network traffic? do you use the network for anything else that is heavy? like streaming, downloading, playing games. All these factors decide on whether a client can connect to your machine or not in a timely manner.

hi,
yea the upload on the isp isnt too hot. but that would mean slow transfers not timeouts wouldn't it?

i thought timeouts were to do with not recieving ACK packets for a designated time and so the machine believes the connection is lost?

it's a serv-u ftp server, so i'l just play (mash my palm on the keyboard) with the DNS and timeout settings.

Thanks for all your help.