How can I Access {VIA FTP or Network} ...

a file {Called StockLibrary.xml} that is within a directory on a Unix system?

I cannot access the system directly. However:

This System can access another Unix system Via FTP and its own internal server, and the other Unix system can communicate back.
I can easily access The other UNIX system easily via FTP from my PC.

So if we call the system containing the xml file that I want to access Unix_A, and call the other Unix system that I can see and that can see Unix_A, Unix_B, is there some way to Actively reach out from My PC, go thru Unix_B to get to Unix_A, and grab the xml file?

Or, does someone know how to CShell {or equivalent} a script that would, on a timed interval, FTP the file from Unix_A {Running the script} to Unix_B, which I could then easily retrieve from my PC via a progie?




:wave:
-Lou

You need telnet access to unix_b in order to acheive this easily.
You would telnet to unix_b, and from there, ftp to unix_a.

An interesting idea, which might be the easiest, would be to setup a small ftp server on your local computer. Just get some freebie piece of crap from the web.
Telnet to unix_b. From unix_b, telnet to unix_a. From unix_a, ftp the file to your computer.

Because otherwise, you would have to telnet to unix_b, ftp from unix_b to unix_a, get the file to unix_b, and then from your computer ftp to unix_b and get the file from there.
Having unix_a ftp'ing directly to your computer would save time and would make more sense in my opinion.

Quote:

---

Originally posted by plenderj
Having unix_a ftp'ing directly to your computer would save time and would make more sense in my opinion.

---

True, but I don't have any Idea how to access my PC from unix_A.

Unix_B can see My PC, easily established via ping.
Unix_A can't ping my pc.

Unix_A is supposedly running an Apache server, but I'm clueless when it comes to Apache. It was set up to be inaccesable except thru Unix_B, by Our printers Manufacturing company.

So, I've come up with a somewhat satisfactory solution.

I enabled Unix_A to be able to rcp files to Unix_B, and using SCM or SMC, {Solaris Management Console? Must be SMC, Whatever...} I set up a scheduled job to rcp the file that I want to access to Unix_B on a daily basis. Now, whenever my programs require access to the file, they can conveniently grab a relatively recent version from Unix_B anytime they want.

Of course, it bugs me that I can't access the file live.

But, A copy < 24 hors old is almost good enough.

Hmmm, If I set up 47 more scheduled jobs, I could get that file down to being no more than 30 minutes old.
Hmmmm,...

:wave:
-Lou

I'd say its a routing issue - i.e. unix_a is on a different subnet to yours, and its only got routing information to get to unix_b, and not your pc.

If unix_a is running apache, you could use lynx from unix_b to grab the file via http.
So unix_a plonks the file into a public folder every time its created/changed (you could use a small tcl script to check and copy (use a crontab to schedule it)).

Then from unix_b it could use lynx or whatever to grab the file.
Again a small tcl script setup via a crontab could schedule this.
It could plonk it into a folder to which you have access on unix_b, and then your pc just grabs it from unix_b...