Yes, the binary/put of the savf is there. This can happen either manually typing the commands or through the script. I can telnet then to the rstobj from the savf just sent. This is how I solved the client prob two days ago...now it's my 'quickie' problem. Yes, I telnet to client then do a wrkreginf and page down. I did not look at our local machine as this same script works with other clients. That seems to me that our ftp client side is okay. Maybe not though...our dev box has the same thing as client for those two exit points. Bruce <rob@xxxxxxxxx> wrote in message news:OF341B15FF.3F62C14C-ON05256E4D.0072D75C-05256E4D.00739889@xxxxxxxxxx > Man is that frustrating. Here's a few points and questions. > > Granted the problem could still be on the server. For instance, commands > may only be allowed if executed from certain addresses. However it looks > like you've already verified the lack of any ftp exit point programs. So > how they would do that is befuddling. > > Here's a (possibly stupid) question. Back at your location, if you PUT a > file to the remote and then you telnet to the remote, is the file really > there? Or is the ftp session being routed to Lord knows where? > > And, just to beat that dead horse into hamburger, you are looking at the > exit points after you telnet to the remote site, right? And on your local > site also? > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.