RPM Meter
in [Design]
|
Prev: Bad Omen?
Next: Posts with threaded holes
From: markp on 3 Aug 2010 12:08 "John Larkin" <jjlarkin(a)highNOTlandTHIStechnologyPART.com> wrote in message news:njdg569u4m8mh578m6hlqijf0vkvcrp9mc(a)4ax.com... > On Wed, 04 Aug 2010 01:01:42 +1000, David Eather <eather(a)tpg.com.au> > wrote: > >>On 3/08/2010 6:47 PM, markp wrote: >>> "markp"<map.nospam(a)f2s.com> wrote in message >>> news:8bmed6FkrhU1(a)mid.individual.net... >>>> >>>> "David Eather"<eather(a)tpg.com.au> wrote in message >>>> news:CIqdna68SMcEYcjRnZ2dnUVZ_sadnZ2d(a)giganews.com... >>>>> On 1/08/2010 3:26 PM, Grant wrote: >>>>>> On Sun, 01 Aug 2010 14:41:42 +1000, David Eather<eather(a)tpg.com.au> >>>>>> wrote: >>>>>> >>>>>>> On 1/08/2010 12:53 PM, Grant wrote: >>>>>> ... >>>>>>>> Funny, 'cos seven others found the copy I put up on >>>>>>>> >>>>>>>> http://grrr.id.au/image/DoubleTach.jpg >>>>>>>> >>>>>>>> Grant. >>>>>>> >>>>>>> Sorry. I haven't been clear. I got the image on grrr.id.au - thank >>>>>>> you >>>>>>> indeed. I'm just giving up on retrieving / viewing from >>>>>>> ftp://jjlarkin.lmi.net - although I like to follow every link and >>>>>>> have >>>>>>> a >>>>>>> read. >>>>>> >>>>>> Okay, I misunderstood what you gave up on ;) Stuff happens. >>>>>> >>>>>> Cheers, >>>>>> Grant. >>>>> >>>>> It's really annoying 'cause I can download lots of stuff from FTP >>>>> sites >>>>> like this one >>>>> >>>>> ftp://ftp.cis.uab.edu/pub/hyatt >>>> >>>> OK, try this, a web based ftp proxy server: >>>> http://www.webftp.jbi.in/ >>>> >>>> put jjlarkin.lmi.net as the ftp server, tick anonymous and passive >>>> boxes. >>>> >>>> Mark. >>>> >>> >>> Did this work? >>> >>> Mark. >>> >>> >> >>Sorry - I just tried it. Works great. > > I never intended to make this difficult. I just asked my ISP to give > me a place to post files. I haven't ever had problems accessing this > or other peoples' FTP sites using Firefox. > > It also shows up as ftp://66.117.156.8/ > > I don't know much about this stuff. If there are any settings my ISP > could change to simplify access, please let me know. > > My cabin automation system bounces status and control files through > this FTP site; see CABIN.TXT, which is updated once a minute by a > netbook PC in the ski boot closet. > > ftp://66.117.156.8/CABIN.TXT > ftp://66.117.156.8/Auto_wired.jpg > > I wrote the code in PowerBasic, shelling out to the Windows 'ftp' > command here and there. > > Note that Truckee is, in the summer, usually the coldest town in > California, and often the coldest in the country. It hit 32F last > night, when San Francisco only got down to the low 50's. It's 53F here > right now. > > John > I doubt there is anything wrong your end John, I can access it and so can most others. It's likely to be a port blocking thing IMO, either at the ISP or a firewall of some sort (personal or hardware) in the way. It could even be a modem/router blocking port 21 on outgoing accesses. The OP has tried a number of clients (unsure whether they were on different PCs though), and passive mode, which would indicate outgoing port 21 being blocked. Mark.
From: markp on 3 Aug 2010 12:32 "markp" <map.nospam(a)f2s.com> wrote in message news:8bqt7iFf69U1(a)mid.individual.net... > > "John Larkin" <jjlarkin(a)highNOTlandTHIStechnologyPART.com> wrote in > message news:njdg569u4m8mh578m6hlqijf0vkvcrp9mc(a)4ax.com... >> On Wed, 04 Aug 2010 01:01:42 +1000, David Eather <eather(a)tpg.com.au> >> wrote: >> >>>On 3/08/2010 6:47 PM, markp wrote: >>>> "markp"<map.nospam(a)f2s.com> wrote in message >>>> news:8bmed6FkrhU1(a)mid.individual.net... >>>>> >>>>> "David Eather"<eather(a)tpg.com.au> wrote in message >>>>> news:CIqdna68SMcEYcjRnZ2dnUVZ_sadnZ2d(a)giganews.com... >>>>>> On 1/08/2010 3:26 PM, Grant wrote: >>>>>>> On Sun, 01 Aug 2010 14:41:42 +1000, David Eather<eather(a)tpg.com.au> >>>>>>> wrote: >>>>>>> >>>>>>>> On 1/08/2010 12:53 PM, Grant wrote: >>>>>>> ... >>>>>>>>> Funny, 'cos seven others found the copy I put up on >>>>>>>>> >>>>>>>>> http://grrr.id.au/image/DoubleTach.jpg >>>>>>>>> >>>>>>>>> Grant. >>>>>>>> >>>>>>>> Sorry. I haven't been clear. I got the image on grrr.id.au - thank >>>>>>>> you >>>>>>>> indeed. I'm just giving up on retrieving / viewing from >>>>>>>> ftp://jjlarkin.lmi.net - although I like to follow every link and >>>>>>>> have >>>>>>>> a >>>>>>>> read. >>>>>>> >>>>>>> Okay, I misunderstood what you gave up on ;) Stuff happens. >>>>>>> >>>>>>> Cheers, >>>>>>> Grant. >>>>>> >>>>>> It's really annoying 'cause I can download lots of stuff from FTP >>>>>> sites >>>>>> like this one >>>>>> >>>>>> ftp://ftp.cis.uab.edu/pub/hyatt >>>>> >>>>> OK, try this, a web based ftp proxy server: >>>>> http://www.webftp.jbi.in/ >>>>> >>>>> put jjlarkin.lmi.net as the ftp server, tick anonymous and passive >>>>> boxes. >>>>> >>>>> Mark. >>>>> >>>> >>>> Did this work? >>>> >>>> Mark. >>>> >>>> >>> >>>Sorry - I just tried it. Works great. >> >> I never intended to make this difficult. I just asked my ISP to give >> me a place to post files. I haven't ever had problems accessing this >> or other peoples' FTP sites using Firefox. >> >> It also shows up as ftp://66.117.156.8/ >> >> I don't know much about this stuff. If there are any settings my ISP >> could change to simplify access, please let me know. >> >> My cabin automation system bounces status and control files through >> this FTP site; see CABIN.TXT, which is updated once a minute by a >> netbook PC in the ski boot closet. >> >> ftp://66.117.156.8/CABIN.TXT >> ftp://66.117.156.8/Auto_wired.jpg >> >> I wrote the code in PowerBasic, shelling out to the Windows 'ftp' >> command here and there. >> >> Note that Truckee is, in the summer, usually the coldest town in >> California, and often the coldest in the country. It hit 32F last >> night, when San Francisco only got down to the low 50's. It's 53F here >> right now. >> >> John >> > > I doubt there is anything wrong your end John, I can access it and so can > most others. It's likely to be a port blocking thing IMO, either at the > ISP or a firewall of some sort (personal or hardware) in the way. It could > even be a modem/router blocking port 21 on outgoing accesses. The OP has > tried a number of clients (unsure whether they were on different PCs > though), and passive mode, which would indicate outgoing port 21 being > blocked. > > Mark. Having said that he can access other ftp sites, so that's probably not it.
From: Grant on 3 Aug 2010 18:32 On Tue, 03 Aug 2010 08:53:04 -0700, John Larkin <jjlarkin(a)highNOTlandTHIStechnologyPART.com> wrote: >On Wed, 04 Aug 2010 01:01:42 +1000, David Eather <eather(a)tpg.com.au> >wrote: > .... >>Sorry - I just tried it. Works great. > >I never intended to make this difficult. I just asked my ISP to give >me a place to post files. I haven't ever had problems accessing this >or other peoples' FTP sites using Firefox. > >It also shows up as ftp://66.117.156.8/ That resolves anybody's DNS issues, David has a problem somehow getting through his security setup. Mostly something to do with passive FTP, and he was unlikely to change that for only one site's access problem. > >I don't know much about this stuff. If there are any settings my ISP >could change to simplify access, please let me know. What you could do is have dual ftp/http read access to the same file area, so your existing ftp stuff that works for you now keeps working, and people can access your stuff with the more common web (http) protocol as well. It means your ISP needs to setup for you a basic http (web) server with no special magic (accept for a "GET|HEAD" only filter), and link the ftp file directory area to it. Something like that, specifics depend on server OS. From the public's PoV, they use the same url body you publish, except with an 'http' in front, and totally transparent for your current ftp access. > >My cabin automation system bounces status and control files through >this FTP site; see CABIN.TXT, which is updated once a minute by a >netbook PC in the ski boot closet. > >ftp://66.117.156.8/CABIN.TXT >ftp://66.117.156.8/Auto_wired.jpg > >I wrote the code in PowerBasic, shelling out to the Windows 'ftp' >command here and there. Ftp is the usual (well, these days one uses more secure ssh and scp) protocol to write stuff to one's own or controlled remote web (http) server. You don't have to write or serve a web page with http, so there's no real difference as far as the method of offering image files like you do now. Looks like this for one file (allowing for my site and naming): http://grrr.id.au/JohnLarkin/current-source-mosfet.JPG or, if one looks on the directory: http://grrr.id.au/JohnLarkin/ Or, for basic privacy, you can have: http://grrr.id.au/JohnLarkinNoDir/DoubleTach.jpg and, there's nothing shown for http://grrr.id.au/JohnLarkinNoDir/ The difference is that the JohnLarkinNoDir directory has a blank index.html file, preventing casual http file browsing. People could still access via the ftp server for your current offering. See: http://bugsplatter.id.au/kernel/boxen/pooh64/ for a combination of no index.html file, instead a README.html tags some info on the page -- this is with the apache web server -- plus a frequently updated list of files (in the case, linux-kernel .configs for what I'm running). I don't link my ftp server to my http files, though ftp://grrr.id.au/ does link to the ftp server here, nothing there for electronics though. >Note that Truckee is, in the summer, usually the coldest town in >California, and often the coldest in the country. It hit 32F last >night, when San Francisco only got down to the low 50's. It's 53F here >right now. I don't know your geography ;) We go a little below 0'C overnight some nights in winter, but no snow here. I'm about 100 miles NNW of Melbourne, Australia, not Florida :) Grant.
From: Jim Thompson on 3 Aug 2010 19:24 On Wed, 04 Aug 2010 08:32:01 +1000, Grant <omg(a)grrr.id.au> wrote: >On Tue, 03 Aug 2010 08:53:04 -0700, John Larkin <jjlarkin(a)highNOTlandTHIStechnologyPART.com> wrote: > >>On Wed, 04 Aug 2010 01:01:42 +1000, David Eather <eather(a)tpg.com.au> >>wrote: >> >... >>>Sorry - I just tried it. Works great. >> >>I never intended to make this difficult. I just asked my ISP to give >>me a place to post files. I haven't ever had problems accessing this >>or other peoples' FTP sites using Firefox. >> >>It also shows up as ftp://66.117.156.8/ > >That resolves anybody's DNS issues, David has a problem somehow >getting through his security setup. Mostly something to do with >passive FTP, and he was unlikely to change that for only one site's >access problem. > >> >>I don't know much about this stuff. If there are any settings my ISP >>could change to simplify access, please let me know. > >What you could do is have dual ftp/http read access to the same >file area, so your existing ftp stuff that works for you now keeps >working, and people can access your stuff with the more common >web (http) protocol as well. > >It means your ISP needs to setup for you a basic http (web) server >with no special magic (accept for a "GET|HEAD" only filter), and >link the ftp file directory area to it. Something like that, >specifics depend on server OS. > >From the public's PoV, they use the same url body you publish, except >with an 'http' in front, and totally transparent for your current ftp >access. >> >>My cabin automation system bounces status and control files through >>this FTP site; see CABIN.TXT, which is updated once a minute by a >>netbook PC in the ski boot closet. >> >>ftp://66.117.156.8/CABIN.TXT >>ftp://66.117.156.8/Auto_wired.jpg >> >>I wrote the code in PowerBasic, shelling out to the Windows 'ftp' >>command here and there. > >Ftp is the usual (well, these days one uses more secure ssh and scp) >protocol to write stuff to one's own or controlled remote web (http) >server. > >You don't have to write or serve a web page with http, so there's no >real difference as far as the method of offering image files like you >do now. > >Looks like this for one file (allowing for my site and naming): > > http://grrr.id.au/JohnLarkin/current-source-mosfet.JPG > >or, if one looks on the directory: > > http://grrr.id.au/JohnLarkin/ > >Or, for basic privacy, you can have: > > http://grrr.id.au/JohnLarkinNoDir/DoubleTach.jpg > >and, there's nothing shown for > > http://grrr.id.au/JohnLarkinNoDir/ > >The difference is that the JohnLarkinNoDir directory has a blank >index.html file, preventing casual http file browsing. People could >still access via the ftp server for your current offering. > >See: http://bugsplatter.id.au/kernel/boxen/pooh64/ for a combination >of no index.html file, instead a README.html tags some info on the >page -- this is with the apache web server -- plus a frequently >updated list of files (in the case, linux-kernel .configs for what >I'm running). > >I don't link my ftp server to my http files, though ftp://grrr.id.au/ >does link to the ftp server here, nothing there for electronics though. > >>Note that Truckee is, in the summer, usually the coldest town in >>California, and often the coldest in the country. It hit 32F last >>night, when San Francisco only got down to the low 50's. It's 53F here >>right now. > >I don't know your geography ;) We go a little below 0'C overnight >some nights in winter, but no snow here. I'm about 100 miles NNW >of Melbourne, Australia, not Florida :) > >Grant. Something is hokey. For anonymous FTP, any ol' person can download... but can't upload. But I password-protect client-sensitive upload/download logins. Mostly I don't bother with loading public material in the FTP directory... just allow download access to, for instance, my SED page. ...Jim Thompson -- | James E.Thompson, CTO | mens | | Analog Innovations, Inc. | et | | Analog/Mixed-Signal ASIC's and Discrete Systems | manus | | Phoenix, Arizona 85048 Skype: Contacts Only | | | Voice:(480)460-2350 Fax: Available upon request | Brass Rat | | E-mail Icon at http://www.analog-innovations.com | 1962 | Phoenix, Arizona, Inventor of many civic-oriented innovations such as automated garbage collection has added a new tool to its Fire Department safety equipment... addressing problems with accidents involving so-called Smart Cars: A Hydraulically Assisted Spatula.
From: Grant on 3 Aug 2010 20:05
On Tue, 03 Aug 2010 16:24:31 -0700, Jim Thompson <To-Email-Use-The-Envelope-Icon(a)On-My-Web-Site.com> wrote: >On Wed, 04 Aug 2010 08:32:01 +1000, Grant <omg(a)grrr.id.au> wrote: > >>On Tue, 03 Aug 2010 08:53:04 -0700, John Larkin <jjlarkin(a)highNOTlandTHIStechnologyPART.com> wrote: >> >>>On Wed, 04 Aug 2010 01:01:42 +1000, David Eather <eather(a)tpg.com.au> >>>wrote: >>> >>... >>>>Sorry - I just tried it. Works great. >>> >>>I never intended to make this difficult. I just asked my ISP to give >>>me a place to post files. I haven't ever had problems accessing this >>>or other peoples' FTP sites using Firefox. >>> >>>It also shows up as ftp://66.117.156.8/ >> >>That resolves anybody's DNS issues, David has a problem somehow >>getting through his security setup. Mostly something to do with >>passive FTP, and he was unlikely to change that for only one site's >>access problem. >> >>> >>>I don't know much about this stuff. If there are any settings my ISP >>>could change to simplify access, please let me know. >> >>What you could do is have dual ftp/http read access to the same >>file area, so your existing ftp stuff that works for you now keeps >>working, and people can access your stuff with the more common >>web (http) protocol as well. >> >>It means your ISP needs to setup for you a basic http (web) server >>with no special magic (accept for a "GET|HEAD" only filter), and >>link the ftp file directory area to it. Something like that, >>specifics depend on server OS. >> >>From the public's PoV, they use the same url body you publish, except >>with an 'http' in front, and totally transparent for your current ftp >>access. >>> >>>My cabin automation system bounces status and control files through >>>this FTP site; see CABIN.TXT, which is updated once a minute by a >>>netbook PC in the ski boot closet. >>> >>>ftp://66.117.156.8/CABIN.TXT >>>ftp://66.117.156.8/Auto_wired.jpg >>> >>>I wrote the code in PowerBasic, shelling out to the Windows 'ftp' >>>command here and there. >> >>Ftp is the usual (well, these days one uses more secure ssh and scp) >>protocol to write stuff to one's own or controlled remote web (http) >>server. >> >>You don't have to write or serve a web page with http, so there's no >>real difference as far as the method of offering image files like you >>do now. >> >>Looks like this for one file (allowing for my site and naming): >> >> http://grrr.id.au/JohnLarkin/current-source-mosfet.JPG >> >>or, if one looks on the directory: >> >> http://grrr.id.au/JohnLarkin/ >> >>Or, for basic privacy, you can have: >> >> http://grrr.id.au/JohnLarkinNoDir/DoubleTach.jpg >> >>and, there's nothing shown for >> >> http://grrr.id.au/JohnLarkinNoDir/ >> >>The difference is that the JohnLarkinNoDir directory has a blank >>index.html file, preventing casual http file browsing. People could >>still access via the ftp server for your current offering. >> >>See: http://bugsplatter.id.au/kernel/boxen/pooh64/ for a combination >>of no index.html file, instead a README.html tags some info on the >>page -- this is with the apache web server -- plus a frequently >>updated list of files (in the case, linux-kernel .configs for what >>I'm running). >> >>I don't link my ftp server to my http files, though ftp://grrr.id.au/ >>does link to the ftp server here, nothing there for electronics though. >> >>>Note that Truckee is, in the summer, usually the coldest town in >>>California, and often the coldest in the country. It hit 32F last >>>night, when San Francisco only got down to the low 50's. It's 53F here >>>right now. >> >>I don't know your geography ;) We go a little below 0'C overnight >>some nights in winter, but no snow here. I'm about 100 miles NNW >>of Melbourne, Australia, not Florida :) >> >>Grant. > >Something is hokey. > >For anonymous FTP, any ol' person can download... but can't upload. If you let them upload to a write-only directory, it's safe enough, it's only when admins allow visible uploads that their machine gets found and used as a warez repository, at the admin's expense. > >But I password-protect client-sensitive upload/download logins. Ftp and passwords no longer secure, but you'd know your server history to know if it's time to move to ssh + scp. > >Mostly I don't bother with loading public material in the FTP >directory... just allow download access to, for instance, my SED page. Yes, seems John L. doesn't have the desire to write web pages ;) Diversity, freedom. Grant. > > ...Jim Thompson |