all groups > iis ftp > july 2005 >
iis ftp :
Problems Using FTP
I have replied you in previous thread. -- Regards, Bernard Cheah http://www.microsoft.com/iis/ http://www.iiswebcastseries.com/ http://www.msmvps.com/bernard/ [quoted text, click to view] " AA Smith" <SmithRMS@Comcast.net> wrote in message news:eUVlQH%23iFHA.3784@tk2msftngp13.phx.gbl... > Thanks, so much Dave! I really appreciate your generous help. Glad to > know I don't need a static IP. > > I guess the one remaining question I have concerns the PC's IP address > within the LAN, or, more specifically, what IP address others would use to > access my FTP. I'd appreciate it if you'd be kind enough to expand a bit > on that. > -- > With kindest regards, > > Dick Smith > "Dave" <noone@nowhere.com> wrote in message > news:ORSaCq9iFHA.1464@TK2MSFTNGP14.phx.gbl... >> on the firewall, go to the firewall configuration and allow the ftp >> service ports 20 and 21 through the firewall. >> >> you don't need any static ip's... though it makes it a bit easier at >> times. you can use services like dydns.org or noip.com to map a domain >> name to a dynamic ip address. in most cases your router will get the ip >> address from the isp then do nat and assign 192.168.*.* local ip's for >> your lan machines. the router then can forward ftp requests from outside >> to whichever machine inside you want them to go to, either by name or ip. >> it is possible to do it other ways, but that is normally the easiest for >> normal isp's. >> >> one other warning... some isp will block the ports for ftp, http, smtp, >> and some other ports to prevent you from using a home connection as a >> business. so don't be surprised if it doesn't work even after you get >> your end configured. >> >> " AA Smith" <SmithRMS@Comcast.net> wrote in message >> news:%23qopWg9iFHA.3256@TK2MSFTNGP12.phx.gbl... >>> I've setup FTP and quickly found that the WinXP Pro SP2 firewall blocks >>> access to my FTP Server. How can I permit access to resources in the >>> FTP without closing the firewall? >>> >>> Also: is it imperative that I have a static IP address on the computer >>> in our LAN that has FTP installed? Or, more to the point, CAN I have a >>> static IP address on the computer in our LAN that has FTP installed? Or >>> do ISPs only issue static IP address that way or only to the address of >>> the LAN's modem/router? >>> >>> For what it's worth, this LAN has a new LinkSys router that also offers >>> secure wireless access. >>> -- >>> With kindest regards, >>> >>> Dick Smith >>> >> >> > >
I've setup FTP and quickly found that the WinXP Pro SP2 firewall blocks access to my FTP Server. How can I permit access to resources in the FTP without closing the firewall? Also: is it imperative that I have a static IP address on the computer in our LAN that has FTP installed? Or, more to the point, CAN I have a static IP address on the computer in our LAN that has FTP installed? Or do ISPs only issue static IP address that way or only to the address of the LAN's modem/router? For what it's worth, this LAN has a new LinkSys router that also offers secure wireless access. -- With kindest regards, Dick Smith
Thanks, so much Dave! I really appreciate your generous help. Glad to know I don't need a static IP. I guess the one remaining question I have concerns the PC's IP address within the LAN, or, more specifically, what IP address others would use to access my FTP. I'd appreciate it if you'd be kind enough to expand a bit on that. -- With kindest regards, Dick Smith [quoted text, click to view] "Dave" <noone@nowhere.com> wrote in message news:ORSaCq9iFHA.1464@TK2MSFTNGP14.phx.gbl... > on the firewall, go to the firewall configuration and allow the ftp > service ports 20 and 21 through the firewall. > > you don't need any static ip's... though it makes it a bit easier at > times. you can use services like dydns.org or noip.com to map a domain > name to a dynamic ip address. in most cases your router will get the ip > address from the isp then do nat and assign 192.168.*.* local ip's for > your lan machines. the router then can forward ftp requests from outside > to whichever machine inside you want them to go to, either by name or ip. > it is possible to do it other ways, but that is normally the easiest for > normal isp's. > > one other warning... some isp will block the ports for ftp, http, smtp, > and some other ports to prevent you from using a home connection as a > business. so don't be surprised if it doesn't work even after you get your > end configured. > > " AA Smith" <SmithRMS@Comcast.net> wrote in message > news:%23qopWg9iFHA.3256@TK2MSFTNGP12.phx.gbl... >> I've setup FTP and quickly found that the WinXP Pro SP2 firewall blocks >> access to my FTP Server. How can I permit access to resources in the FTP >> without closing the firewall? >> >> Also: is it imperative that I have a static IP address on the computer in >> our LAN that has FTP installed? Or, more to the point, CAN I have a >> static IP address on the computer in our LAN that has FTP installed? Or >> do ISPs only issue static IP address that way or only to the address of >> the LAN's modem/router? >> >> For what it's worth, this LAN has a new LinkSys router that also offers >> secure wireless access. >> -- >> With kindest regards, >> >> Dick Smith >> > >
on the firewall, go to the firewall configuration and allow the ftp service ports 20 and 21 through the firewall. you don't need any static ip's... though it makes it a bit easier at times. you can use services like dydns.org or noip.com to map a domain name to a dynamic ip address. in most cases your router will get the ip address from the isp then do nat and assign 192.168.*.* local ip's for your lan machines. the router then can forward ftp requests from outside to whichever machine inside you want them to go to, either by name or ip. it is possible to do it other ways, but that is normally the easiest for normal isp's. one other warning... some isp will block the ports for ftp, http, smtp, and some other ports to prevent you from using a home connection as a business. so don't be surprised if it doesn't work even after you get your end configured. [quoted text, click to view] " AA Smith" <SmithRMS@Comcast.net> wrote in message news:%23qopWg9iFHA.3256@TK2MSFTNGP12.phx.gbl... > I've setup FTP and quickly found that the WinXP Pro SP2 firewall blocks > access to my FTP Server. How can I permit access to resources in the FTP > without closing the firewall? > > Also: is it imperative that I have a static IP address on the computer in > our LAN that has FTP installed? Or, more to the point, CAN I have a > static IP address on the computer in our LAN that has FTP installed? Or > do ISPs only issue static IP address that way or only to the address of > the LAN's modem/router? > > For what it's worth, this LAN has a new LinkSys router that also offers > secure wireless access. > -- > With kindest regards, > > Dick Smith >
Your ISP has given your "real" internet address to the Linksys router. For Linksys, browse to http://192.168.1.1 The default password is admin, leave username blank. Look for the "Status" tab to find your internet IP address. This is the address to give to Aunt Sophie so she can use her FTP client to download pictures. Since you don't have a static IP address this will change from time to time. In my case, my IP address is the same for months on end then it'll change. This is fine if, for example, you just want to distribute pictures from your vacation. But we're not done. We have to tell Linksys that when it receives an FTP packet from Aunt Sophie, that it need to be passed along to 192.168.1.x. This is called "Port Forwarding." If you google "linksys port forwarding ftp" (without quotes) there are plenty of tutorials on how to do this. One more thing, you're opening up your LAN to outside internet traffic, make sure you always keep your system up-to-date and buttoned up. I run a very simple password-protected FTP server at work and get daily break-in attempts, occasionally someone will literally try thousands of username/password combinations to get in - so far nobody has succeeded. Be careful. Lance ***** AA Smith thought carefully and wrote on 7/18/2005 2:43 PM: [quoted text, click to view] > Thanks, so much Dave! I really appreciate your generous help. Glad to know > I don't need a static IP. > > I guess the one remaining question I have concerns the PC's IP address > within the LAN, or, more specifically, what IP address others would use to > access my FTP. I'd appreciate it if you'd be kind enough to expand a bit on
Thanks, again, Lance! I sincerely appreciate your kind help. One thing more that I'd like to know is whether the port setting for FTP is TCP, UDP or both. Also, what is the name of that "very simple password-protected FTP server" that you use? -- With kindest regards, Dick Smith [quoted text, click to view] "Lance" <lltbhill@link_earth.net> wrote in message news:elA$kaBjFHA.3336@tk2msftngp13.phx.gbl... > Your ISP has given your "real" internet address to the Linksys router. For > Linksys, browse to http://192.168.1.1 The default password is admin, leave > username blank. Look for the "Status" tab to find your internet IP > address. > > This is the address to give to Aunt Sophie so she can use her FTP client > to download pictures. Since you don't have a static IP address this will > change from time to time. In my case, my IP address is the same for months > on end then it'll change. This is fine if, for example, you just want to > distribute pictures from your vacation. > > But we're not done. We have to tell Linksys that when it receives an FTP > packet from Aunt Sophie, that it need to be passed along to 192.168.1.x. > This is called "Port Forwarding." If you google "linksys port forwarding > ftp" (without quotes) there are plenty of tutorials on how to do this. > > One more thing, you're opening up your LAN to outside internet traffic, > make sure you always keep your system up-to-date and buttoned up. I run a > very simple password-protected FTP server at work and get daily break-in > attempts, occasionally someone will literally try thousands of > username/password combinations to get in - so far nobody has succeeded. > > Be careful. > > Lance > ***** > > AA Smith thought carefully and wrote on 7/18/2005 2:43 PM: >> Thanks, so much Dave! I really appreciate your generous help. Glad to >> know I don't need a static IP. >> >> I guess the one remaining question I have concerns the PC's IP address >> within the LAN, or, more specifically, what IP address others would use >> to access my FTP. I'd appreciate it if you'd be kind enough to expand a >> bit on that.
Hi, Dave; I'm not sure where to change the configuration of Windows Firewall for WinXP Pro. I tried Computer Management, but did not find anything that seemed appropriate there. I opened the WinXP Pro SP2 Security Center and opened the Windows Firewall properties dialogue, but found nothing on any tab to set firewall configuration. I also opened my router's setup and set ports 20 & 21 to be open. I tried them set to the right computer's IP address and I tried the settings of TCP, UDP and BOTH. It seems as though no matter how I have them set, the same thing happens when I access an FTP folder from another computer. The requesting computer finds the correct FTP folder on the ftp host and opens it without a problem. The filenames are all there. However, every time I try to copy a file from that folder, an error pops up stating that "an error occurred while copying this file." I would appreciate any feedback that you'd be kind enough to send to give me a boot in the right direction. -- With kindest regards, Dick Smith [quoted text, click to view] "Dave" <noone@nowhere.com> wrote in message news:ORSaCq9iFHA.1464@TK2MSFTNGP14.phx.gbl... > on the firewall, go to the firewall configuration and allow the ftp > service ports 20 and 21 through the firewall. > > you don't need any static ip's... though it makes it a bit easier at > times. you can use services like dydns.org or noip.com to map a domain > name to a dynamic ip address. in most cases your router will get the ip > address from the isp then do nat and assign 192.168.*.* local ip's for > your lan machines. the router then can forward ftp requests from outside > to whichever machine inside you want them to go to, either by name or ip. > it is possible to do it other ways, but that is normally the easiest for > normal isp's. > > one other warning... some isp will block the ports for ftp, http, smtp, > and some other ports to prevent you from using a home connection as a > business. so don't be surprised if it doesn't work even after you get your > end configured. > > " AA Smith" <SmithRMS@Comcast.net> wrote in message > news:%23qopWg9iFHA.3256@TK2MSFTNGP12.phx.gbl... >> I've setup FTP and quickly found that the WinXP Pro SP2 firewall blocks >> access to my FTP Server. How can I permit access to resources in the FTP >> without closing the firewall? >> >> Also: is it imperative that I have a static IP address on the computer in >> our LAN that has FTP installed? Or, more to the point, CAN I have a >> static IP address on the computer in our LAN that has FTP installed? Or >> do ISPs only issue static IP address that way or only to the address of >> the LAN's modem/router? >> >> For what it's worth, this LAN has a new LinkSys router that also offers >> secure wireless access. >> -- >> With kindest regards, >> >> Dick Smith >> > >
Hello, again, Dave; I checked the Windows Firewall Properties Advanced tab and Exceptions tab.the FTP application I'm using is on the list of firewall Exceptions (which means it will not be blocked if a check mark appears in the box to the left) Also on the list is an Easy-to-use FTP server for Windows. both of those are checked. Is that latter on the Windows IIS server? On Advanced tab, the only two services listed, 1394 connection and Local Area Connection are both checked. And I clicked the settings button on both of those services and placed check marks in the box beside FTP Server. Still, with all of that done, I get an error every time I try to access the folder, an error message pops up on the requesting computer stating that "An error occurred opening that folder on the FTP folder. Make sure you have permission to access that folder. Details: An internal error occurred in the Microsoft Internet extensions." No file names are listed--and this is with Windows Firewall turned off! Though the LinkSys firewall was on and ports 20 & 21 open for FTP. Actually, the FTP server on the host pops up a balloon to let me know that someone is accessing (actually trying to access) a folder in the Server. So, the requesting computer is reaching the host. As to what the error may be, I'm at a loss. The FTP server I'm using for now is not password protected. I'd really appreciate suggestions as to what might be causing this error. -- With kindest regards, Dick Smith [quoted text, click to view] "Dave" <noone@nowhere.com> wrote in message news:e8m0ZxJjFHA.3448@TK2MSFTNGP10.phx.gbl... > open the control panel for the network connections. bring up the > properties > for the connection you want to change the setting on, probably the only > one > there. on the advanced tab click the settings button on the windows > firewall section of the tab. in there you can set up exceptions to the > firewall blocking. > > " AA Smith" <SmithRMS@Comcast.net> wrote in message > news:udvYthJjFHA.1048@tk2msftngp13.phx.gbl... >> Hi, Dave; >> >> I'm not sure where to change the configuration of Windows Firewall for >> WinXP Pro. I tried Computer Management, but did not find anything that >> seemed appropriate there. I opened the WinXP Pro SP2 Security Center and >> opened the Windows Firewall properties dialogue, but found nothing on any >> tab to set firewall configuration. I also opened my router's setup and >> set ports 20 & 21 to be open. I tried them set to the right computer's >> IP >> address and I tried the settings of TCP, UDP and BOTH. It seems as >> though >> no matter how I have them set, the same thing happens when I access an >> FTP >> folder from another computer. The requesting computer finds the correct >> FTP folder on the ftp host and opens it without a problem. The filenames >> are all there. However, every time I try to copy a file from that folder, >> an error pops up stating that "an error occurred while copying this >> file." >> >> I would appreciate any feedback that you'd be kind enough to send to give >> me a boot in the right direction. >> -- >> With kindest regards, >> >> Dick Smith >> >> "Dave" <noone@nowhere.com> wrote in message >> news:ORSaCq9iFHA.1464@TK2MSFTNGP14.phx.gbl... >>> on the firewall, go to the firewall configuration and allow the ftp >>> service ports 20 and 21 through the firewall. >>> >>> you don't need any static ip's... though it makes it a bit easier at >>> times. you can use services like dydns.org or noip.com to map a domain >>> name to a dynamic ip address. in most cases your router will get the ip >>> address from the isp then do nat and assign 192.168.*.* local ip's for >>> your lan machines. the router then can forward ftp requests from outside >>> to whichever machine inside you want them to go to, either by name or >>> ip. >>> it is possible to do it other ways, but that is normally the easiest for >>> normal isp's. >>> >>> one other warning... some isp will block the ports for ftp, http, smtp, >>> and some other ports to prevent you from using a home connection as a >>> business. so don't be surprised if it doesn't work even after you get >>> your end configured. >>> >>> " AA Smith" <SmithRMS@Comcast.net> wrote in message >>> news:%23qopWg9iFHA.3256@TK2MSFTNGP12.phx.gbl... >>>> I've setup FTP and quickly found that the WinXP Pro SP2 firewall blocks >>>> access to my FTP Server. How can I permit access to resources in the >>>> FTP without closing the firewall? >>>> >>>> Also: is it imperative that I have a static IP address on the computer >>>> in our LAN that has FTP installed? Or, more to the point, CAN I have a >>>> static IP address on the computer in our LAN that has FTP installed? >>>> Or >>>> do ISPs only issue static IP address that way or only to the address of >>>> the LAN's modem/router? >>>> >>>> For what it's worth, this LAN has a new LinkSys router that also offers >>>> secure wireless access. >>>> -- >>>> With kindest regards, >>>> >>>> Dick Smith >>>> >>> >>> >> >> > > >
open the control panel for the network connections. bring up the properties for the connection you want to change the setting on, probably the only one there. on the advanced tab click the settings button on the windows firewall section of the tab. in there you can set up exceptions to the firewall blocking. [quoted text, click to view] " AA Smith" <SmithRMS@Comcast.net> wrote in message news:udvYthJjFHA.1048@tk2msftngp13.phx.gbl... > Hi, Dave; > > I'm not sure where to change the configuration of Windows Firewall for > WinXP Pro. I tried Computer Management, but did not find anything that > seemed appropriate there. I opened the WinXP Pro SP2 Security Center and > opened the Windows Firewall properties dialogue, but found nothing on any > tab to set firewall configuration. I also opened my router's setup and > set ports 20 & 21 to be open. I tried them set to the right computer's IP > address and I tried the settings of TCP, UDP and BOTH. It seems as though > no matter how I have them set, the same thing happens when I access an FTP > folder from another computer. The requesting computer finds the correct > FTP folder on the ftp host and opens it without a problem. The filenames > are all there. However, every time I try to copy a file from that folder, > an error pops up stating that "an error occurred while copying this file." > > I would appreciate any feedback that you'd be kind enough to send to give > me a boot in the right direction. > -- > With kindest regards, > > Dick Smith > > "Dave" <noone@nowhere.com> wrote in message > news:ORSaCq9iFHA.1464@TK2MSFTNGP14.phx.gbl... >> on the firewall, go to the firewall configuration and allow the ftp >> service ports 20 and 21 through the firewall. >> >> you don't need any static ip's... though it makes it a bit easier at >> times. you can use services like dydns.org or noip.com to map a domain >> name to a dynamic ip address. in most cases your router will get the ip >> address from the isp then do nat and assign 192.168.*.* local ip's for >> your lan machines. the router then can forward ftp requests from outside >> to whichever machine inside you want them to go to, either by name or ip. >> it is possible to do it other ways, but that is normally the easiest for >> normal isp's. >> >> one other warning... some isp will block the ports for ftp, http, smtp, >> and some other ports to prevent you from using a home connection as a >> business. so don't be surprised if it doesn't work even after you get >> your end configured. >> >> " AA Smith" <SmithRMS@Comcast.net> wrote in message >> news:%23qopWg9iFHA.3256@TK2MSFTNGP12.phx.gbl... >>> I've setup FTP and quickly found that the WinXP Pro SP2 firewall blocks >>> access to my FTP Server. How can I permit access to resources in the >>> FTP without closing the firewall? >>> >>> Also: is it imperative that I have a static IP address on the computer >>> in our LAN that has FTP installed? Or, more to the point, CAN I have a >>> static IP address on the computer in our LAN that has FTP installed? Or >>> do ISPs only issue static IP address that way or only to the address of >>> the LAN's modem/router? >>> >>> For what it's worth, this LAN has a new LinkSys router that also offers >>> secure wireless access. >>> -- >>> With kindest regards, >>> >>> Dick Smith >>> >> >> > >
Don't see what you're looking for? Try a search.
|
|
|