NT Application using SAMBA

[WoodLark]

We are trying to replace a Windows NT Server with a Linux server running SAMBA. There is only one application stored on the NT server, an accounting program written in Clarion.

With the old NT server, the application runs fine from an NT workstation.

With the Linux server, the application accepts user login but hangs on the first screen if the client is an NT workstation. If the client is a Windows 2000 workstation, the application runs perfectly.

Does anyone know of a difference in the way NT and 2000 interact with SAMBA that would account for this?

 

[inma]

could you send me the smb.conf for windows 2000? I am unable that it runs. Thanks.

 

[WoodLark]

Inma:

I'll be glad to send you the smb.conf file we use on the Linux server if you send me your email address to ke4dmATarrl.net (change AT to @). However, there is nothing special about the smb.conf file as far as Win 2000 is concerned; it is the same one we use for Win NT 4.0 (in fact, our domain controller is an NT 4.0 server).

 

[marsd]

Some applications do not perform correctly via samba-remember the smb implement was RE
by tridgell and is better ;-). The API for ms smb\cifs may make assumptions that sambas smb
cannot make. I have read about this elsewhere,where applications break, socket errors occur, etc...aftermoving to samba.
As far as nt 4.0 workstation, I'm sorry , I have never used it. Stupid question:
have you checked you logs and set your debug level(-d4) for samba, and checked the nt workstations logs as well for any clues?

 

[fenris]

Could it be that w2k implements full raw sockets? Troy Williams B.Eng.
fenris@hotmail.com

 

[fenris]

Could it be that w2k implements full raw sockets? I've read that w2k is the first implementation of full unix sockets that microsoft has done. Could this be the cause? Troy Williams B.Eng.
fenris@hotmail.com

 

[marsd]

Good thought fenris..
But why would a tcp sock problem be caused by raw socks.
I am not being sarcastic, I am familiar with the theory but
have never done socket programming at a low level...
I have used netcat , socket, awk 3.1.0 's /inet/tcp
and tcl's socket interfaces however..
Why would this interfere with normal tcp/ip connections when raw connects are much harder to set up? Does MS
use raw interfaces for tcp socks, I thought they used the winsock api?
Excuse my ignorance..I am interested in the theory here.

 

[ifincham]

Hi,

Have you tried putting 'strict locking = yes' in the smb.conf ? Sometimes this helps but may slow system down generally. Also there are various socket options that can be set in smb.conf - for example 'socket options = IPTOS_LOWDELAY' or 'socket options = IPTOS_LOWDELAY TCP_NODELAY' .

I know nothing about clarion and I'm not saying these will work but they could be worth trying. Otherwise, that old fave approach of upgrading to the latest version(s) might be worth trying. These are 2.2.1a for the new series and 2.0.10 for the old stream.

Rgds

 

[fenris]

Marsd,
I don't know too much about the winsock myself. I only read that w2k implments full raw sockets. As far as I could tell could be an explaination why w2k worked and not win nt 4. Now that I think about it, it is very unlikely that this is the cause.

Are all the nt boxes having an identical problem? Troy Williams B.Eng.
fenris@hotmail.com

 

[johnhoke]

It sounds like CLARION is the problem, not SAMBA...

AFAIK clarion uses a backend ODBC (read: Jet/Access) based DB to store its data in... Unless you can find something to emulate the ODBC correctly, it wont work...

Just my thoughts/2 cents

-John ---
John Hoke