• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu

WSEB FTP not working

Started by ddan, 2008.05.12, 20:54:19

Previous topic - Next topic

ddan

Hello all. Long-time OS/2 enthusiast registered at last because STUMPED.

Recently moved to WSEB CP2. Having problems with FTP using same FTP Server127
setup (copied the files using NetDrive) that works perfectly with W4 FP15.
Have 3 computers on router: WSEB, W4 FP 15, and PCLinuxOS 2007. FTP between
OS/2 boxes works, as does FTP from W4 to Linux, but the Linux box can't even
find the WSEB server (at varied DHCP addresses). The W4 box serves out at over
10M bytes/second to either of the others. The WSEB box serves W4 at only ONE
MB/sec, though is faster than W4 on internet (over 300KB/sec versus
150KB/sec). A WSEB ping doesn't find the Linux box.

A deal of experimentation has convinced me the problem is something running in
WSEB that interferes with FTP. It's not doing print serving or anything beyond
basic internet, and I don't need it to. Behind-router FTP would be my only
"LAN" use. I can rem out any LAN programs, haven't yet only because don't know
what else that'd affect. See nothing in CONFIG.SYS that says "FTP". I'd been
using Netdrive 2.23, but stopped NDCTL.EXE, and that didn't help. Can't
imagine that the NIC driver (Via Rhine II) has anything to do with this, but
could add a 3COM card if anyone thinks it'd help.

Have only TCPIP protocol on the VIA NIC. Have possible wrong routing in WSEB's
TCPIP setup: took me a long time to figure out how to avoid "Error: File
exists" during boot-up. My ad hoc fix was to comment out this line in
\mptn\bin\setup.cmd:
rem route add default 192.168.1.1 -hopcount
But don't understand why Linux doesn't see it at all, while the W4 box does.

Perhaps another clue is that while doing FTP from WSEB to W4, I'm essentially
locked out of all HTTP use: streaming audio and web pages simply time out,
though that concurrency also works fine on the W4 box.

My only real use for Linux is CD and DVD burning, so my choice is to either
now and then physically move the drive (PCLinuxOS 2007 has HPFS support in the
kernel) or to figure out how to burn with OS/2, which might be for the best,
as I still find OS/2 highly preferable to even Linux, and of course Windows is
OS/2's evil twin, the one they kept locked in the basement and fed stray cats.


Pete

Hi ddan (is that short for desperate dan?  :-)

I think the 1st thing I would look at is updating ftpsever to current, from http://www.pmoylan.org/pages/os2/FtpServer.html , and see if there are any cures within that update.

If not maybe you should post the contents of the \mptn\bin\setup.cmd and \ibmcom\protocol.ini files in the hope that someone can spot a configuration error.

Regards

Pete

RobertM

Hi ddan,

I've found that for some reason some machine on my network cannot find my WSeB box (via TPC/IP) either, until a ping is initiated from one or both machines. Have you tried ping to and from the Linux box from the WSeB machine?

As far as I know, the cause is something different in the way the 32bit TCP/IP stack works in WSeB. I think setting machine specific routes in the routing table will work. The problem only seems to arise for local subnet machines (ie: 192.168.0.10 -> 192.168.0.15) and does not affect routing to machines off network.

The first time I saw this problem arise was with newer "routers" - when I had a Cisco T1/DS1 router, I don't recall running into this problem (but I also may have had routes already defined for each machine).

On the WSeB machine, you can set up a simple script to ping the other machine... such as:

'ping 129.168.0.100 1 >nul'

(and something similar on the Linux machine)

This will ping the IP once. The problem I have seen is that if there is inactivity for a certain length of time, the machines once again cannot find each other until they are pinged again.

Currently, I've yet to sit down and figure out exactly what is going on - I just simply ping the necessary machine (ie: ping the WSeB machine from the Windows machine - or vice versa, then run whatever software I am using to connect from one to the other - usually FileZilla on the Win machine to FTPServer on the WSeB machine).

If I ever decide to sit down and figure it out, I will let you know what I find... and hopefully, in the meantime, someone else here can offer a more permanent, better solution...



The problem is not FTPServer by Peter Moylan. That much I do know. On that note though, Peter has a newer version (v1.30) on his site. While it wont fix your issue, you should consider upgrading. It will add large file support (ie: files over 2GB sent or received - as long as the FTP directories are on a JFS drive), as well as a couple other fixes for it.



-Robert


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


ddan

Tried FTP Server130; previously got garbage characters in its VIOSETUP
permissions, but this time copied from the 127 setup using the included
loadprm, and checked that were set. No avail, though.

Tried the mutual pings: no effect.

By the way, had gotten desperate enough to swap to a long cable because read
somewhere that routers must have a minimum physical delay time. Didn't work
here. File it next to swinging a dead cat over the system.

However, then tried killing processes using PSTAT in PMPatrol, starting with
c:\mptn\bin\dhcpcd.exe. Hit first time. FTP now appears to be working normally
at 10M/sec. -- Interesting discovery next because surprise and joy wiped from
my tiny little mind what process I had killed, so re-booted to look at the
list, and to confirm, again tried FTP before killing dhcpcd.exe. Guess what?
It's still working. Some sort of once-per-power-up phenomena, so though
working, it's not exactly solved. As I rarely backup to the Linux box, guess
it's good enough for now...

Thanks, Pete and Robert, though, for effort here besides your numerous previous posts that HAVE helped.

Fahrvenugen

Yup, that's a part of the DHCP stuff, if you dig through your:

c:\mptn\bin\setup.cmd

file you might find a reference to dhcpstrt or something like that.  Since you're using static addressing anyways, REM that stuff out.

If it isn't in your setup.cmd file. search your config.sys file, your c:\startup.cmd file, and of course the startup folder for any references to starting dhcp, rem it out.

As I seem to recall, IBM released a few  updates to the DHCP stuff that came with WSEB...  the later versioons/updates worked properly, but the one that shipped with the product had issues.


ddan

Uh, going to post more whining because still STUMPED.

More experiment reveals nothing firm. Robert's pinging does after all seem to
be necessary, but it's definitely not reliable. Stopping DHCPCD.EXE (which I
clarify that I am using though not crucial if would make problem go away) does
seem necessary. However, repeating all previous steps that got it going didn't
work a second time (though yet more fiddling DID), and between two CP2 boxes,
doing same to each, wouldn't work at all.

As FTP is something of a basic service, surely someone has SOME idea where to
start. I'm not convinced that removing DHCPCD.EXE is a solution (tests where I
stopped just it didn't work, besides that once I had it going without stopping it);
it's some obscure combination and or sequence. (And such fiddling is simply invoking magic, NOT a technical FIX. Must I try swinging a dead cat over it, after all?)

When re-started routing using \mptn\bin\setup.cmd, it crashed the running HTTP
streams (duh), then it didn't like the routing, but on third try the FTP
worked.

My focus is on fact that W4 FP15 works just fine, so what's different in WSEB?

Blonde Guy

Quote from: ddan on 2008.05.19, 20:43:58

My focus is on fact that W4 FP15 works just fine, so what's different in WSEB?


Pretty much all the networking software is different. To see the version numbers, type "inetver". Warp 4 had a 16-bit stack. FP 15 does nothing for TCP/IP -- there are other fixpaks for that.

That said, everything should work. If you have a later version of TCP/IP, use it. I'd say that's true for either W4 FP15 or WSeB CP 2.

If you are using DHCP, you shouldn't have to enter any routing information in your configuration.

Expert Consulting for OS/2 and eComStation

Fahrvenugen

I think this has something to do with the TCP/IP stack installed, as I have yet to run into difficulties like you've described on  a machine brought up to the latest TCP/IP level.

Could you open up a command prompt and type:

inetver

And then paste the results to the forum here?

I have a feeling you may have an older stack.


ddan

AHAH. All hail the Blonde Guy for hitting the crucial point: don't need the
routing setup at all! I just commented it out in \mptn\bin\setup.cmd,
rebooted, and now works fine first time from Linux, no fiddling.

THAT'S what different from W4, as I was careful to set all the same, or as
near as possible. WSEB TCP config on the one hand nagged me about no routing
setup, and on the other hand, didn't accept the same routing numbers as W4, so
I guessed a default path to 192.168.1.0, the router, was the right way...

Thanks to all, especially The Blonde Guy, whose website has helped too.