SAMBA shares on XP

[undercover]

We have a SAMBA v2.2.2 server running on RedHat 7.1 and are having problems with XP. We can map the drive without a problem, we can even browse around and "upload" a ton of stuff. Everything seems fine ... untill we open a document from the SAMBA machine, make changes and try to save it. We get a "Network Device no longer available" message.

After some investigation ...

We notice that if we aren't browsing through the SAMBA server it shows up as 'Disconnected Network Drive' in My Computer. Now this has to be the problem. Is there some sort of "keep alive" setting we are missing? Is there any way to keep the SAMBA mapped drive connected at ALL TIMES?

 

[Nothinman]

Samba does have a keepalive setting you could check.


keepalive (G)
The value of the parameter (an integer) represents the number of seconds between keepalive packets. If
this parameter is zero, no keepalive packets will be sent. Keepalive packets, if sent, allow the server
to tell whether a client is still present and responding.

Keepalives should, in general, not be needed if the socket being used has the SO_KEEPALIVE attribute set
on it (see socket options). Basically you should only use this option if you strike difficulties.

Default: keepalive = 300

Example: keepalive = 600

 

[undercover]

thanks for the heads up.

now where do I find that setting?



smb.conf?

 

[n0cmonkey]

Probably. man smb.conf or checkout samba.org

 

[undercover]

Yeah it's in the smb.conf ... I would need to add it to the 'socket options'

ty ty

 

[brandonl]

up

 

[n0cmonkey]

<< up >>



Up for what?

 

[undercover]

I think he bumped it because there was no solution.

anyways ...

keepalive did not fix it.

still looking ...

 

[n0cmonkey]

Well since Windows 2000 SMB is a POS I would suggest moving to a more reliable way of sharing files. I havent wanted to drop kick a computer this bad in a long time.

 

[manly]

<< Well since Windows 2000 SMB is a POS I would suggest moving to a more reliable way of sharing files. I havent wanted to drop kick a computer this bad in a long time. >>



Unfortunately SMB is a virus, I mean de facto standard.

 

[n0cmonkey]

<<

<< Well since Windows 2000 SMB is a POS I would suggest moving to a more reliable way of sharing files. I havent wanted to drop kick a computer this bad in a long time. >>



Unfortunately SMB is a virus, I mean de facto standard. >>



Yeah, and I figured out my problem so I should be calmer soon

Off to samba.org to read documentation...

 

[undercover]

Let us know what you find out about XP and SAMBA playing nice ...

 

[n0cmonkey]

<<

Let us know what you find out about XP and SAMBA playing nice ... >>



I know there appears to be a reg hack for Winxp to work better with SAMBA.

EDIT: although that may have nothing to do with this problem.

 

[manly]

I occasionally run a Samba 2.2.0a server on Linux, with a VMware guest WXP client. The basic setup is a simple workgroup.

I have no particular problems browsing or doing file operations. In my case, the Samba server is configured to be a WINS server as well.

The registry modification for WXP is only to be able to join a Samba domain controller, I believe.

Are you pretty confident that your smb.conf is correct for your intended use?

 

[n0cmonkey]

Ok, I dont mess with Windows and I have a basic setup for SAMBA on my Mac so I dont need to play with silly things like that

And the configurations must be perfect since there are no logs

 

[kylef]

Have you made sure that NetBEUI is not installed? Windows seems to like using it first if installed, and that could be causing some problems, since Samba works over IP only.

 

[undercover]

Nope. No Netbeui ...

but

that makes me wanna look at the IPX that's installed for Novell.

ty