Won't connect to my own running FTP or even any other!

I have Windows XP PRO Sp2, I installed the FTP Service from the IIs using the ADD/Remove Programs (Add Windows Components) in control panel, then I loaded IIs from Administrative Tools in the start menu.

1. I stopped the FTP site (the one included by default)
2. I loaded its properties, made some basic changes.
a. changed from default directory to shared folder
b. changed from "all unassigned address" to my IP from the drop down menu (i dont have a static IP)
c. changed ftpname (called description I think)

Everything else the same (default): IIs controlled password, anonymous enabled, etc..

3. Finished and Started it again. Loaded IE and typed in the address "ftp://myiphere"

It keeps searching but it finds nothing!

I cannot even connect to other ftps of my friends. It keeps searching and it does not find anything, although their ftps working fine and they connecting to each other. My ZoneAlarm firewall is also disabled (I temporarily disabled it just to be sure its not the reason).

I also have my router port forwarding (tcp port 21) to my ip address that was listed in the FTP settings, even port 20 port forwarded as well as it is for the transfer and 21 for establishing the connection itself.

Whats blocking me to access any ftp at all? What is blocking me from accessing even my own ftp which I'm running on the same computer?!! What exactly do I have to do to solve this situation? I have also tried Serv-U once, did not work.. but I prefer the XP IIs, unless you have a really good I should change to something else.

I just need to get this working, I've read a lot on the net on this issue, but I am still totally stuck. Thanks in advance for the help!
Who is Participating?
VertigoRayConnect With a Mentor Commented:
no-ip.com can help you by assigning a dynamic IP address to a Statics DNS name.  You simply run a program on your computer, and whenever your IP address changes, it sends the changes to the DNS servers owned by no-ip.com.  However, this will not help your current issue.  Personally, I use http://www.dyndns.org/

As for the TELNET ordeal, just type the command he gave you at the Command Prompt.  Your screen should black out and as you type you probably won't see anything.  You can exit the TELNET session by simply typing "exit" (You won't see the typing).
Check to make sure that the Windows XP firewall is not on.  Since you have XP SP2, it's typically on by default.  Windows firewall is configurable via the control panel in SP2.

Use all IP addresses if you do not have a static IP.
You can also test connectivity to a port by using TELNET IP space PORT, i.e:

     TELNET 21

Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

ArchmudoAuthor Commented:
The XP firewall is turned off ofcourse. Dont know what u mean by testing the port by TELNET, is it important, and should I change back to "All Unassigned" not my IP address? Will that make it work, or is it just a tip? Besides, if I change it to "all unassinged", will I still need to connect using ftp://myipaddress?

I also heard others tell me something no-ip.com address or something. Whats that about? Can it help me since I dont have static IP?
Also, you may want to try connecting to your own FTP site using "localhost" or ""
Archmudo, yes change the setting back to "All Unassigned Addresses".  This will help alot with testing since it removes one more potential set of problems.  It does not limit the way you connect at all.  It actually increases the options that the FTP service will respond to.  Such as ftp://xx.xxx.xx.xxx assigned by the DSL / Cable provider.  Or the mentioned above.  Or FTP:// assigned by an internal router (The 192.x.x.x addresses can only be used for testing inside your home, it will never translate across the internet).

So, did you fix everything?  Got an update?  More issues?  Fell off the face of the earth?

Let us know if we can be of further assistance.
ArchmudoAuthor Commented:
Sorry for late reply.. I did as you told me, opened command prompt, and typed the following..

telnet 21

I got the message below:

Connecting to not open connection to the host, on port 21: Connect failed

You should know that I have a network, my lan IP is

my router has port 21 forwarded to that LAN IP

soo.. any more ideas?
You will not be able to do an 'inside - out' telnet or other connection.  To test internally, you have to use the interal IP of you computer, in your case you mentioned it was  So try telnet 21.  If that command gives the same message (or a similar message), then you know that you have a firewall issue OR the FTP service is not laoding properly and you can check the Application Event Log for errors on that.  
Oh, and I was able to telnet into port 21 from this PC, so you are probably closer than you thought and need to look at username password and other configuration steps.  Remember, do all you testing to the address as long as you are doing it at home.  The outside world will see the same view on port 21 of your IP address even though it seems like the wrong IP to you.
ArchmudoAuthor Commented:
ok this time I did "telnet 21"

and nothing is happening.. cursor blinking and that's it
cwisofskyConnect With a Mentor Commented:
Sounds good to me, you 'connected' to your ftp server.  Use that IP address when you continue your testing.  

For example to test from Internet Explorer use:


Since that is currently not working, I would try removing IIS via the add/remove programs interface and then readding it with the default settings.  They work fine and you should always test them out before you make changes to FTP settings.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.