| Groups | Blog | Home |
iis ftp : I cannot get my damn FTP server to work? Really frustrating.
Or are you attempting to ftp from PC1 (192.168.1.101) to your IIS/FTP PC (192.168.1.100)? If this is the case, then you don't have to go through your router at all. You just FTP to 192.168.1.100 from PC1. If this works then you're good to go. Otherwise, your FTP server is configured incorrectly. This is likewise your first step to identify the issue (try internally first). In your setup, port forwarding on routers is *only* for allowing ***outside*** machines to connect to your **internal** machine (either PC1 or PC2). -- Cheers, Ed [quoted text, click to view] "David Mills" <davidmillsjd@yahoo.com> wrote in message news:V9WdnbsOp-YwZE_enZ2dnUVZ_tOdnZ2d@adelphia.com... >I cannot get my damn FTP server to work? Really frustrating. > > Ok, here is my setup. > > -Linksys cable modem and a Linksys router. > -I have 2 pc's connected to the modem sharing the cable connection. > -The pc's internal ip addresses are 192.168.1.100 and 192.168.1.101 > -My Wan/Internet ip address is 69.167.219.111 > > I have my IIS server running and setup correctly. I have "Allow IIS to > control password" checked under security accounts inside IIS. > On my router setup pages, under the "forwarding" tab, I have ports 20 thru > 21 forwarded to 192.168.1.100 > I checked on Linksys' knowledge base and it says to have the ip address > set to 192.168.1.3. I tried using that address and it didn't work either. > I have searched all over Google for FTP setup using port forwarding and > they all basically say the same thing, but it isn't working. > The only thing I tried but didn't work at all is setting up a static ip > address within my router. > I went into the router and typed in 69.167.219.111 for my static ip > address and then that killed my internet access. > I am assuming you can't just type in whatever "static" ip address you > want. > Checking the research I have done, you shouldn't have to have a static ip > address in order to get this to work. > > If I open up windows explorer and type in ftp://69.167.219.111/ then I get > this 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 connection with the server was reset > ------------------------------------------------------ > > Does anyone have any ideas what I am doing wrong? > > Thanks. > > DM. >
I cannot get my damn FTP server to work? Really frustrating.
Ok, here is my setup. -Linksys cable modem and a Linksys router. -I have 2 pc's connected to the modem sharing the cable connection. -The pc's internal ip addresses are 192.168.1.100 and 192.168.1.101 -My Wan/Internet ip address is 69.167.219.111 I have my IIS server running and setup correctly. I have "Allow IIS to control password" checked under security accounts inside IIS. On my router setup pages, under the "forwarding" tab, I have ports 20 thru 21 forwarded to 192.168.1.100 I checked on Linksys' knowledge base and it says to have the ip address set to 192.168.1.3. I tried using that address and it didn't work either. I have searched all over Google for FTP setup using port forwarding and they all basically say the same thing, but it isn't working. The only thing I tried but didn't work at all is setting up a static ip address within my router. I went into the router and typed in 69.167.219.111 for my static ip address and then that killed my internet access. I am assuming you can't just type in whatever "static" ip address you want. Checking the research I have done, you shouldn't have to have a static ip address in order to get this to work. If I open up windows explorer and type in ftp://69.167.219.111/ then I get this 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 connection with the server was reset ------------------------------------------------------ Does anyone have any ideas what I am doing wrong? Thanks. DM.
[quoted text, click to view]
"Ed" <Ed@discussions.microsoft.com> wrote in message news:OX27JlxHGHA.916@TK2MSFTNGP10.phx.gbl... > Are you connecting from an external machine to test your configuration? > > Or are you attempting to ftp from PC1 (192.168.1.101) to your IIS/FTP PC > (192.168.1.100)? If this is the case, then you don't have to go through > your router at all. You just FTP to 192.168.1.100 from PC1. If this works > then you're good to go. Otherwise, your FTP server is configured > incorrectly. This is likewise your first step to identify the issue (try > internally first). > > In your setup, port forwarding on routers is *only* for allowing > ***outside*** machines to connect to your **internal** machine (either > PC1 or PC2). > -- > Cheers, > Ed > No, I am not connecting from an outside machine. I am using http://www.web2ftp.com/ for my testing purposes. If I try and ftp using the internal router address (192.168.1.100), it works fine. If I try using the outside ip address, it gives me an error.
[quoted text, click to view]
"Bernard Cheah [MVP]" <qbernard@hotmail.com.discuss> wrote in message news:uZWuOhxHGHA.604@TK2MSFTNGP14.phx.gbl... > First, verify that IIS ftp is working via ftp.exe locally > ftp.exe yourinternaliisftpip > > can you login and do a dir listing? if yes, then IIS ftp is fine. > > Then you need to configure port-forwarding on your router. > you need 21 -> inbound and 20 outbound. IE default is passive mode, which > uses another port range. > > so always try ftp.exe active mode client to test first. > > -- > Regards, > Bernard Cheah Bernard, I tried using ftp.exe and it works perfectly. (using the internal router ip address) If I try using the external internet ip address, I get the error. I have the ports forwarded, so I'm not sure why it doesn't work, this is such a pain. Thanks for the effort though.
[quoted text, click to view]
> No, I am not connecting from an outside machine. I am using > http://www.web2ftp.com/ for my testing purposes. > If I try and ftp using the internal router address (192.168.1.100), it > works fine. If I try using the outside ip address, it gives me an error. That is expected and is the way it is. If I understand your post, here's how your network is setup: 1) PC1 = 192.168.1.101 2) PC2, which is the IIS/FTP server = 192.168.1.100 Your router is anywhere in the 192.168.1.x range, just not .100 nor .101 (likely 192.168.1.1). If you ftp from PC1 (.101) to PC2 (.100), and it works, then yes, your FTP is setup properly. When you created a port forwarding entry in your router, it had *nothing* to do with your internal setup. What you did was allow *anyone* outside of your internal network (anyone on the internet) to access your ftp server. In other words, just as an example, I can access your ftp server if I knew what your external/public IP is. Your external IP is the one your ISP assigns to your router, and in your example, is the 69.x.x.x address. Without getting into networking concept/details: - you **cannot** test your ftp from your internal PC (192.x.x.x) by going to the 69.x.x.x address. It will not work, nor should it. - your *only* choice for ftp **within your internal network** is to connect via the *internal* IP address of your IIS/FTP (192.168.1.100), unless you have some name resolution setup installed (dns, static hosts files, etc.) so that you can use names like your example of "www.web2ftp.com" (internally, netbios will also work). - if you want to test your router port forwarding setup, then you have to do so from **outside** - not from any 192.168.1.x address. This means that you are testing OUTSIDE access to your internal FTP server, *NOT* testing whether your internal PCs can connect with each other successfully. The above are general "rules"/concepts for your type of use - in other words, in larger, more complex networks (ex. multiple internal routers) my comments don't apply. -- Cheers, Ed [quoted text, click to view] "David Mills" <davidmillsjd@yahoo.com> wrote in message news:nLednexIJf4Ork7enZ2dnUVZ_vydnZ2d@adelphia.com... > "Ed" <Ed@discussions.microsoft.com> wrote in message > news:OX27JlxHGHA.916@TK2MSFTNGP10.phx.gbl... >> Are you connecting from an external machine to test your configuration? >> >> Or are you attempting to ftp from PC1 (192.168.1.101) to your IIS/FTP PC >> (192.168.1.100)? If this is the case, then you don't have to go through >> your router at all. You just FTP to 192.168.1.100 from PC1. If this works >> then you're good to go. Otherwise, your FTP server is configured >> incorrectly. This is likewise your first step to identify the issue (try >> internally first). >> >> In your setup, port forwarding on routers is *only* for allowing >> ***outside*** machines to connect to your **internal** machine (either >> PC1 or PC2). >> -- >> Cheers, >> Ed >> > > No, I am not connecting from an outside machine. I am using > http://www.web2ftp.com/ for my testing purposes. > If I try and ftp using the internal router address (192.168.1.100), it > works fine. If I try using the outside ip address, it gives me an error. >
First, verify that IIS ftp is working via ftp.exe locally
ftp.exe yourinternaliisftpip can you login and do a dir listing? if yes, then IIS ftp is fine. Then you need to configure port-forwarding on your router. you need 21 -> inbound and 20 outbound. IE default is passive mode, which uses another port range. so always try ftp.exe active mode client to test first. -- Regards, Bernard Cheah http://www.iis-resources.com/ http://www.iiswebcastseries.com/ http://msmvps.com/blogs/bernard/ [quoted text, click to view] "David Mills" <davidmillsjd@yahoo.com> wrote in message news:V9WdnbsOp-YwZE_enZ2dnUVZ_tOdnZ2d@adelphia.com... >I cannot get my damn FTP server to work? Really frustrating. > > Ok, here is my setup. > > -Linksys cable modem and a Linksys router. > -I have 2 pc's connected to the modem sharing the cable connection. > -The pc's internal ip addresses are 192.168.1.100 and 192.168.1.101 > -My Wan/Internet ip address is 69.167.219.111 > > I have my IIS server running and setup correctly. I have "Allow IIS to > control password" checked under security accounts inside IIS. > On my router setup pages, under the "forwarding" tab, I have ports 20 thru > 21 forwarded to 192.168.1.100 > I checked on Linksys' knowledge base and it says to have the ip address > set to 192.168.1.3. I tried using that address and it didn't work either. > I have searched all over Google for FTP setup using port forwarding and > they all basically say the same thing, but it isn't working. > The only thing I tried but didn't work at all is setting up a static ip > address within my router. > I went into the router and typed in 69.167.219.111 for my static ip > address and then that killed my internet access. > I am assuming you can't just type in whatever "static" ip address you > want. > Checking the research I have done, you shouldn't have to have a static ip > address in order to get this to work. > > If I open up windows explorer and type in ftp://69.167.219.111/ then I get > this 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 connection with the server was reset > ------------------------------------------------------ > > Does anyone have any ideas what I am doing wrong? > > Thanks. > > DM. >
Hi David,
Well, that's "good" in a way because there's really nothing wrong with your setup. Basically, you don't need to setup router port forwarding just to FTP between 2 of your *internal* PCs. You would only "open" a port in your router (via port forwarding) if you intend to allow someone from the outside (anywhere on the internet) to have FTP access into your internal PC (the one providing FTP services). I'm leaving out a lot of networking concepts in the above to avoid confusing you. I hope I've helped clear things up for you. -- Cheers, Ed [quoted text, click to view] "David Mills" <davidmillsjd@yahoo.com> wrote in message news:grudna6LH6f--0nenZ2dnUVZ_tadnZ2d@adelphia.com... > "Ed" <Ed@discussions.microsoft.com> wrote in message > news:u0kn1w4HGHA.1192@TK2MSFTNGP11.phx.gbl... >>> No, I am not connecting from an outside machine. I am using >>> http://www.web2ftp.com/ for my testing purposes. >>> If I try and ftp using the internal router address (192.168.1.100), it >>> works fine. If I try using the outside ip address, it gives me an >>> error. >> >> That is expected and is the way it is. If I understand your post, here's >> how your network is setup: >> >> 1) PC1 = 192.168.1.101 >> 2) PC2, which is the IIS/FTP server = 192.168.1.100 >> >> Your router is anywhere in the 192.168.1.x range, just not .100 nor .101 >> (likely 192.168.1.1). >> >> If you ftp from PC1 (.101) to PC2 (.100), and it works, then yes, your >> FTP is setup properly. >> >> When you created a port forwarding entry in your router, it had *nothing* >> to do with your internal setup. What you did was allow *anyone* outside >> of your internal network (anyone on the internet) to access your ftp >> server. In other words, just as an example, I can access your ftp server >> if I knew what your external/public IP is. Your external IP is the one >> your ISP assigns to your router, and in your example, is the 69.x.x.x >> address. >> >> Without getting into networking concept/details: >> >> - you **cannot** test your ftp from your internal PC (192.x.x.x) by going >> to the 69.x.x.x address. It will not work, nor should it. >> >> - your *only* choice for ftp **within your internal network** is to >> connect via the *internal* IP address of your IIS/FTP (192.168.1.100), >> unless you have some name resolution setup installed (dns, static hosts >> files, etc.) so that you can use names like your example of >> "www.web2ftp.com" (internally, netbios will also work). >> >> - if you want to test your router port forwarding setup, then you have to >> do so from **outside** - not from any 192.168.1.x address. This means >> that you are testing OUTSIDE access to your internal FTP server, *NOT* >> testing whether your internal PCs can connect with each other >> successfully. >> >> The above are general "rules"/concepts for your type of use - in other >> words, in larger, more complex networks (ex. multiple internal routers) >> my comments don't apply. >> -- >> Cheers, >> Ed >> >> >> "David Mills" <davidmillsjd@yahoo.com> wrote in message >> news:nLednexIJf4Ork7enZ2dnUVZ_vydnZ2d@adelphia.com... >>> "Ed" <Ed@discussions.microsoft.com> wrote in message >>> news:OX27JlxHGHA.916@TK2MSFTNGP10.phx.gbl... >>>> Are you connecting from an external machine to test your configuration? >>>> >>>> Or are you attempting to ftp from PC1 (192.168.1.101) to your IIS/FTP >>>> PC (192.168.1.100)? If this is the case, then you don't have to go >>>> through your router at all. You just FTP to 192.168.1.100 from PC1. If >>>> this works then you're good to go. Otherwise, your FTP server is >>>> configured incorrectly. This is likewise your first step to identify >>>> the issue (try internally first). >>>> >>>> In your setup, port forwarding on routers is *only* for allowing >>>> ***outside*** machines to connect to your **internal** machine (either >>>> PC1 or PC2). >>>> -- >>>> Cheers, >>>> Ed >>>> >>> >>> No, I am not connecting from an outside machine. I am using >>> http://www.web2ftp.com/ for my testing purposes. >>> If I try and ftp using the internal router address (192.168.1.100), it >>> works fine. If I try using the outside ip address, it gives me an >>> error. >>> >> >> > > You are right about how I have everything setup and how it is working. (or > not working) :) > >
[quoted text, click to view]
"Ed" <Ed@discussions.microsoft.com> wrote in message news:u0kn1w4HGHA.1192@TK2MSFTNGP11.phx.gbl... >> No, I am not connecting from an outside machine. I am using >> http://www.web2ftp.com/ for my testing purposes. >> If I try and ftp using the internal router address (192.168.1.100), it >> works fine. If I try using the outside ip address, it gives me an error. > > That is expected and is the way it is. If I understand your post, here's > how your network is setup: > > 1) PC1 = 192.168.1.101 > 2) PC2, which is the IIS/FTP server = 192.168.1.100 > > Your router is anywhere in the 192.168.1.x range, just not .100 nor .101 > (likely 192.168.1.1). > > If you ftp from PC1 (.101) to PC2 (.100), and it works, then yes, your > FTP is setup properly. > > When you created a port forwarding entry in your router, it had *nothing* > to do with your internal setup. What you did was allow *anyone* outside of > your internal network (anyone on the internet) to access your ftp server. > In other words, just as an example, I can access your ftp server if I knew > what your external/public IP is. Your external IP is the one your ISP > assigns to your router, and in your example, is the 69.x.x.x address. > > Without getting into networking concept/details: > > - you **cannot** test your ftp from your internal PC (192.x.x.x) by going > to the 69.x.x.x address. It will not work, nor should it. > > - your *only* choice for ftp **within your internal network** is to > connect via the *internal* IP address of your IIS/FTP (192.168.1.100), > unless you have some name resolution setup installed (dns, static hosts > files, etc.) so that you can use names like your example of > "www.web2ftp.com" (internally, netbios will also work). > > - if you want to test your router port forwarding setup, then you have to > do so from **outside** - not from any 192.168.1.x address. This means that > you are testing OUTSIDE access to your internal FTP server, *NOT* testing > whether your internal PCs can connect with each other successfully. > > The above are general "rules"/concepts for your type of use - in other > words, in larger, more complex networks (ex. multiple internal routers) my > comments don't apply. > -- > Cheers, > Ed > > > "David Mills" <davidmillsjd@yahoo.com> wrote in message > news:nLednexIJf4Ork7enZ2dnUVZ_vydnZ2d@adelphia.com... >> "Ed" <Ed@discussions.microsoft.com> wrote in message >> news:OX27JlxHGHA.916@TK2MSFTNGP10.phx.gbl... >>> Are you connecting from an external machine to test your configuration? >>> >>> Or are you attempting to ftp from PC1 (192.168.1.101) to your IIS/FTP PC >>> (192.168.1.100)? If this is the case, then you don't have to go through >>> your router at all. You just FTP to 192.168.1.100 from PC1. If this >>> works then you're good to go. Otherwise, your FTP server is configured >>> incorrectly. This is likewise your first step to identify the issue (try >>> internally first). >>> >>> In your setup, port forwarding on routers is *only* for allowing >>> ***outside*** machines to connect to your **internal** machine (either >>> PC1 or PC2). >>> -- >>> Cheers, >>> Ed >>> >> >> No, I am not connecting from an outside machine. I am using >> http://www.web2ftp.com/ for my testing purposes. >> If I try and ftp using the internal router address (192.168.1.100), it >> works fine. If I try using the outside ip address, it gives me an error. >> > > You are right about how I have everything setup and how it is working. (or not working) :)
There you go... this is not ftp issue. you need to refer your router product
doc and see how to configure the port forwarding. After that try ftp.exe again and post the output here -- Regards, Bernard Cheah http://www.iis-resources.com/ http://www.iiswebcastseries.com/ http://msmvps.com/blogs/bernard/ [quoted text, click to view] "David Mills" <davidmillsjd@yahoo.com> wrote in message news:Qvidnbb3gOplrk7enZ2dnUVZ_tGdnZ2d@adelphia.com... > "Bernard Cheah [MVP]" <qbernard@hotmail.com.discuss> wrote in message > news:uZWuOhxHGHA.604@TK2MSFTNGP14.phx.gbl... >> First, verify that IIS ftp is working via ftp.exe locally >> ftp.exe yourinternaliisftpip >> >> can you login and do a dir listing? if yes, then IIS ftp is fine. >> >> Then you need to configure port-forwarding on your router. >> you need 21 -> inbound and 20 outbound. IE default is passive mode, which >> uses another port range. >> >> so always try ftp.exe active mode client to test first. >> >> -- >> Regards, >> Bernard Cheah > > Bernard, > > I tried using ftp.exe and it works perfectly. (using the internal router > ip address) > If I try using the external internet ip address, I get the error. > I have the ports forwarded, so I'm not sure why it doesn't work, this is > such a pain. > Thanks for the effort though. > > >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |