Hi, I am having a lot of trouble with getting 0s2 to talk with samba. They seem to be making the right noises at handshake time, and seem to set up a session no problems (using ethereal, monitoring packets). However, when it comes to actually transferring information (such as doing a listing of a share from the os2 box) it crashes with the error: Open AndX Request, Path: \OSO001.MSG; Read AndX, FID: 0x0000,6 Open AndX Response, Error: File not found (pathname error) Path incorrect \OSO001.MSG So I copied one of these OSO001.MSG files from the OS2 machine and put it into the home dir of the connecting user. Then instead of the incorrect path I was getting a TCP incorrect checksum error. I don't understand why samba wants to know about an OS2 file that contains system messages. Looking in the source code, I can't find any reference to this file, and I cant find the particular error message either. The dos window on the OS2 box just crashes. NT and win2k boxes can connect without problem, but it is essential that the lanmanager connects as well. Anecdotally, samba and OS2 have worked together before, so what has changed with teh new versions? Thanks, Gillian
On Sun, Aug 15, 2004 at 03:27:15PM +1000, gillian bennett wrote:> Hi, > > I am having a lot of trouble with getting 0s2 to talk with samba. They > seem to be making the right noises at handshake time, and seem to set > up a session no problems (using ethereal, monitoring packets). > > However, when it comes to actually transferring information (such as > doing a listing of a share from the os2 box) it crashes with the error: > > Open AndX Request, Path: \OSO001.MSG; Read AndX, FID: 0x0000,6 > Open AndX Response, Error: File not found (pathname error) > Path incorrect \OSO001.MSG > > > So I copied one of these OSO001.MSG files from the OS2 machine and put > it into the home dir of the connecting user. Then instead of the > incorrect path I was getting a TCP incorrect checksum error. > > I don't understand why samba wants to know about an OS2 file that > contains system messages. Looking in the source code, I can't find any > reference to this file, and I cant find the particular error message > either. > > > The dos window on the OS2 box just crashes. NT and win2k boxes can > connect without problem, but it is essential that the lanmanager > connects as well. > > Anecdotally, samba and OS2 have worked together before, so what has > changed with teh new versions?We don't have OS/2 vmware sessions to test against, so this makes it difficult to keep OS/2 support to the same quality as Windows support. I really want to keep OS/2 working though, so can you send me an ethereal capture file of OS/2 crashing when talking to Samba, and also a debug level 10 log. Jim & other IBM'ers - can you help with this ? Jeremy.
Hi, when I tried to connect our SuSE 9.1 linux server running samba-3.0.5.1 to our anchient - but still pretty well running - OS/2 Warpserver, I ran into a lot of troubles. So I had a closer look into the samba-sources and with the help of ethereal I found some bugs, which made it impossible to talk to the OS/2 Warpserver, which is running the LANMAN2.1-protocol: On 30.07.2004 I posted a bug in the LANMAN2.1 session setup code: Summary: LANMAN2 protocol (and lower) broken in samba-3.x https://bugzilla.samba.org/show_bug.cgi?id=1571 This bug has already been fixed in 3.0.5.x by Andrew Bartlett.>From now on the two machines were able to setup a session,but the linux machine was still not able to send any data to the Warpserver. Further investigation lead to another bug-report on 7.08.2004: Summary: Any writing and spooling to LANMAN2 server broken (OS/2 Warpserver) https://bugzilla.samba.org/show_bug.cgi?id=1590 This really strange looking bug *is still unresolved* - may be I should raise it to "critical".... I did all the changes to the 3.0.5.1 source locally on my linux machine - recompiled and installed it. Now all is working as expected! Best wishes. Guenter Kukkukk -- G?nter Kukkukk Entwicklungsb?ro f. Informationstechnologien Damaschkestra?e 24 D-10711 Berlin Tel. +49 30 327 024 50