Wolfgang Bornath wrote:
>
> On Fri, Apr 06, 2001 at 18:30 -0400, Pierre Fortin wrote:
>
> > Did you make any changes to molch recently?
[...]
> After that I had a close look at my desktop and discovered that the
> nic was just plugged in but not the screw to hold it. I did that and
> now the connection works on both systems!
[...]
> Thanks to all who helped me and shared their ideas!
Glad we could help; but you found the real problem, so pat yourself on the back!
:>
> Now to something totally different....
>
> As you may remember I tried to install Mandrake through eth0 from the
> desktop to the notebook (i.e. from molch to lapmolch).
>
> I put the pcmcia bootdisk into lapmolch and it boots. It recognizes
> the pcmcia-card and configures eth0.
> Connection is established and I put in the IP, the IP of molch (the
> server) and now it asks for the path to the installation files. These
> files are in /misc2/Mandrake/....
> When I put that in lapmolch and hit ok it says:Bad server response
>
> At the same time tcpdump on molch tells me that the connection is ok
> but something else is wrong:
[...] Seems to be starting fine, though the packet contents are not included.
For tracing, tcpdump is showing its age. Better info can be obtained from Spy
(not open source; but free for up to 10 machines) or better: ethereal which can
sometimes be a pain to install; but worth it...
Machines seem to be OK so far...
> lapmolch.wolf-b.de.1026 > molch.wolf-b.de.ftp: F 29:29(0) ack 181 win 16060
> (DF)
> molch.wolf-b.de.ftp > lapmolch.wolf-b.de.1026: . ack 30 win 32120 (DF)
> [tos 0x10]
> molch.wolf-b.de.ftp > lapmolch.wolf-b.de.1026: P 181:218(37) ack 30 win 32120
> (DF) [tos 0x10]
until lapmolch decides to slam the tcp window shut here:
> lapmolch.wolf-b.de.1026 > molch.wolf-b.de.ftp: R 3528238393:3528238393(0) win
> 0 [tos 0x10]
^
Do you have enough memory on lapmolch? I never traced the ftp install; but mine
would bomb because ftp requires more than my laptop's 32MB to install. NFS on
the other hand does not need to buffer the files during transfer. Check the
virtual consoles for error messages...
Send the trace file created with: tcpdump -w tracefile
[...]
HTH,
Pierre
