RE: FTP to a Windows server with periods and underlines in a folder name -- MIDRANGE-L

"550 Folder _HOLD_ not found" is the exact error

Ls command shows the folder

Using WS_FTP Server with SSL enabled.

Getting setup to try using Windows FTP server to see if it acts the same

[cid:image001.png@01CB2351.92F739F0]

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dennis Lovelady
Sent: Wednesday, July 14, 2010 11:56 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: FTP to a Windows server with periods and underlines in a folder name

Hmmm... in my testing, I have not been able to reproduce this.

What telnet server are you using, and what is the exact error you get when

you try cd to a "bad" directory? The only thing I can imagine that might

cause this is if the server has separate settings for "read directory" and

"change to directory"

Dennis Lovelady

http://www.linkedin.com/in/dennislovelady

--

"He is so unlucky that he runs into accidents which started out to happen to

somebody else."

-- Don Marquis

Windows server 2008 R2. DOS Box browsing also works OK. Can get to any

directory.

-----Original Message-----

From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-

bounces@xxxxxxxxxxxx] On Behalf Of Dennis Lovelady

Sent: Wednesday, July 14, 2010 8:30 AM

To: 'Midrange Systems Technical Discussion'

Subject: RE: FTP to a Windows server with periods and underlines in a

folder name

Which version of Window is this?

What I suggested was not obvious, so: I would recommend doing this

outside

of explorer, in a "DOS box." Explorer is capable of masking this stuff;

DOS

hasn't the nerve. :)

Dennis Lovelady

http://www.linkedin.com/in/dennislovelady

--

"Some see the problem in every opportunity, some see the opportunity in

every problem."

-- Kevin Cowling

Thanks Dennis. Already did go direct to the server with remote

console

as the FTP user and could browse anywhere I wanted in explorer. It is

not iSeries only. It does the same using core-ftp from my PC. Server

is

Windows 2008.

bounces@xxxxxxxxxxxx] On Behalf Of Dennis Lovelady

Sent: Tuesday, July 13, 2010 11:17 PM

First thing I would try to do, is to see if this is unique to the i.

I'm

betting not. Try this same action from a PC, and see what happens.

If (when?) that fails, then I would go to the server in question

(what

OS

does that server use, by the way?). Get to that directory, and try

the

same

cd command from there. Same failure? Yup, that'd be because of

control

characters or other unprintables in at least one of the directory

names.

Dennis Lovelady

http://www.linkedin.com/in/dennislovelady

--

"You grow up the day you have the first real laugh -- at yourself."

-- Ethel Barrymore

I am FTPing from an iSeries to a Windows server to copy some files.

I

have done this many times before without a problem. On this

particular

server the developers of the application decided to use periods(.)

and

underlines(_) as part of folder names. So a path on the windows

server

might be

apphome/CF.SOURCE/_HOLD_/filename

I can get to the home directory of apphome and do a ls command and

see

the CF.SOURCE folder but when I try to do a "cd CF.SOURCE" it says

it

is not found. I tried cd "CF.SOURCE" and cd 'CF.SOURCE' and nothing

works. Just for fun at had our Windows admin make the home folder

for

the user the CF.SOURCE folder and I can then get inside that folder

but

can't cd into the _HOLD_ folder. It is not an authority issue as

the

same username/password I am using for the FTP can remote to the

server

and see all the folders and files. I think this must be an FTP

issue

but I don't think it is unique to iSeries FTP but still hoping

someone

here might have some suggestions.

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx

To subscribe, unsubscribe, or change list options,

visit: http://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxx

Before posting, please take a moment to review the archives

at http://archive.midrange.com/midrange-l.

--