ftp site

several issues:

as you can reach it from outside, this means there is a software blocking you when you connect to your office network

there is no proxy. the firewallis and anti virus is turn off. our network have 3 subnets,
192.168.1.xx - ftp server
192.168.2.xx - clients
192.168.3.xx - clients - another building

it was working before. I can access the ftp from 192.168.3.xx network or from my home but i cannot access on 192.168.2.xx network.

There must be something wrong with the routing then.

Check whether you can ping and telnet over 21 22 ports towards FTP server. If it fails then it is network issue. You simply have to check the routing and add routing on your 192.168.2.xx network. It should resolve your problem I guess.

Hello,

Any restriction of FTP server? Are you connecting through IP address or FQDN?

Regards,
Sanjay Santoki

192.168.x.x is a private network so if you are able to log in from outside does that mean you are using a public address instead?  Perhaps the server software is only listening to the public address.

@reach2sandeep -
yes I can ping the ftp server from 168.2.xx network -no issue pinging the ftp, just can't access it.

@Sanjay
-connecting throuGh FQDN.

Hello,

I would suggest you to please try with IP address and still if you are facing the issue share FTP client logs.

BTW: are you able to telnet FTPSERVERIP on TCP 21 ?

Regards,
Sanjay Santoki

@JessIT2013 -- In my last post I also asked you to Telnet and advise? As you said you can ping properly then there should not be any routing issue, but could be related tot he ports which may be getting blocked due to which it may not be accessible.

Try this command telnet 192.168.1.xxx 21 and see if it connect or halts at Connecting screen. If this is not through then its Ports issue. You may need to check either on FTP server or Local Machine for any Firewall issues. Try disabling firewall on FTP Server and Client and see if it makes any difference.

Also you can test at below settings

http://i1.iis.net/images/configreference/ftpServer_ipSecurity_howto_1.png?cdn_id=2013-05-01-001

http://i1.iis.net/media/7186606/iis-80-dynamic-ip-address-restrictions-1093-image003.png?cdn_id=2013-05-01-001

@reach2sandeep
yes, I was able to telnet 192.168.1.xxx 21 but if i use this telnet mydomain.com 21, it wont connect from 192.168.2.xxx network.

from 192.168.3.xxx network- using telnet mydomain.com 21 is working here.

-I also disabled the server antivirus and clients PC, connection is still failed.

If you are not sure or do not have rights on the DNS Server to add DNS Entry, you can add DNS Entry in Local Host File also.

C:\Windows\System32\Drivers\Etc

Go to above path on your Client PC, and you will find there hosts file. Open that file with Notepad. Make sure you have created backup of it first. Now go to the end of file and add there below entry

192.168.1.xxx     mydomain.com

and Save the file. Between IP and domain name there should be TAB Space (5 Spaces). Now go to command prompt and type ipconfig /flushdns

and now try whether you access the site or not? This would be a Workaround if you do not have DNS Server.

Also it would be worth checking if DNS Server is different for 192.168.3.xxx, if yes you can try to match it by adding it in Additional DNS on 192.168.2.xxx network.

Hope that makes sense.

From inside the network you can connect using the external IP address but you can't connect using the internal private IP address?   Or do both IP addresses connect OK internally and the only problem is DNS resolution?

reach2sandeep and sanjsantoki are both right. It is all about DNS. I forgot to add it in the DNS forward lookup zone. It's all working now. thanks


Jess