samba - Sep 2000 - Cannot copy files from Samba 2.0.6 to NT 4.0 (SP6)

me wrote:
> 
> Hi,
> 
> I saw your posts on comp.protocols.smb and thought you may have some
> ideas about this problem...
> 
> I cannot copy files or directories from a RedHat Linux 6.2 (Samba
> 2.0.6) machine to an NT 4.0 Server (SP6) machine.  I consistently
> get the following an error "File creation error - The session was
> cancelled.", followed by this warning in the NT Event Log:
> 
> ID: 3013 -- The redirector has timed out a request to ...
	This is another variant of the "the client timed out,
	the network is suspect"
> <clientName>.log
> ----------------
> 
> [2000/09/04 20:34:16, 0] locking/locking_shm.c:shm_get_share_modes(213)
>   get_share_modes: process 1621 no longer exists
	The client disconnected, so the smbd exits...
> [2000/09/04 20:33:37, 0] lib/util_sock.c:set_socket_options(148)
>   Failed to set socket option SO_KEEPALIVE (Error Bad file descriptor)
	And it looks like there are a side-effect...

	The things to look for are
	1) ethernet cards set to a different speed as the hub
	2) ethernet cards set to half/full duplex when the hub
	   is at a duifferent duplicity (;-))
	3) bad hubs
	4) late-model 3com cards
	5) bad routers.

--dave
-- 
David Collier-Brown,  | Always do right. This will gratify some people
185 Ellerslie Ave.,   | and astonish the rest.        -- Mark Twain
Willowdale, Ontario   | //www.oreilly.com/catalog/samba/author.html
Work: (905) 415-2849 Home: (416) 223-8968 Email: davecb@canada.sun.com

David (and anyone else)

Would you care to elaborate on item 4 (late model 3Com) from your message
below? 

I have seen some 'strange' error messages as well, and following some of
these
posts regarding network/hub problems I'd like to do a bit more
investigating. In our case, I often see a lot of the following:

[2000/08/31 14:25:07, 0] lib/util_sock.c:write_socket(191)
 write_socket: Error writing 4 bytes to socket 5: ERRNO = Broken pipe
[2000/08/31 14:25:07, 0] lib/util_sock.c:send_smb(606)
  Error writing 4 bytes to client. -1. Exiting
[2000/08/31 14:25:20, 0] lib/util_sock.c:write_data(415)
  write_data: write failure. Error = Broken pipe

Is it possible (by cranking up the debug level) to find out
'which' client is actually having the problems?

I am in the process of tracking down and replacing suspect hubs
but this info (below) about possible problems with 3Com cards
is new to me. FWIW, I have 4 older Kingston hubs, a newer
Netgear hub, and have them attached to a FS508 Netgear switch (in
case there are known issues with any of them). My clients are
using older 10Mb/s Novell/Anthem compatible cards but I am in
the process of upgrading a couple of 'power users' to 10/100
(Netgear) and giving them access to a 10/100 switch. There may be one of
more machines that got 3Com cards (as either part of some
replacements, or they came pre-installed when the computers
were purchased).

Also, does anyone have a sense of whether the 'autosense' feature of
some hubs/switches is reliable in the sense that it really negotiates
sucessfully whether full/half duplex is set? (point 1 and 2 below)

Thanks,

Rich Parker
Director of Engineering
Vermont Public Radio
    
    	And it looks like there are a side-effect...
    
    	The things to look for are
    	1) ethernet cards set to a different speed as the hub
    	2) ethernet cards set to half/full duplex when the hub
    	   is at a duifferent duplicity (;-))
    	3) bad hubs
    	4) late-model 3com cards
    	5) bad routers.
    
    --dave
    -- 
    David Collier-Brown,  | Always do right. This will gratify some people
    185 Ellerslie Ave.,   | and astonish the rest.        -- Mark Twain
    Willowdale, Ontario   | //www.oreilly.com/catalog/samba/author.html
    Work: (905) 415-2849 Home: (416) 223-8968 Email: davecb@canada.sun.com
    


----------

Web page:   http://www.vpr.net

Rich Parker wrote:
| Would you care to elaborate on item 4 (late model 3Com) from your
message
| below? 

	Sure: we saw this a lot this year, and several victims
	had 3com ethernet cards talking to 10/100 hubs of
	various brands.  In some cases, the auto-recognize
	code on the ethernet card or the hub misconfigured
	the card (or port) to a different speed, or to full-duplex
	where the hub only supported half-duplex.

	A "duplicity" error shows up as near-constant collissions,
	a speed mismatch shows up as eitehr no connection or a very 
	slow connection in one direction.

	This is a common problem when the vendor changes the chipset,
	as their old drivers get rewritten in a panic (;-))

	If you have different hubs and cards available, you
	can find out which combination is doubtfull by looking at
	which client is failing: put 
		debug timestamp = yes
		debug pid = yes
	in your smb.conf and use smbstatus to save which 
	clients connect to which pid. When one fails, look
	up the pid in the saved smbstatus output.

--dave

David Collier-Brown,  | Always do right. This will gratify some people
185 Ellerslie Ave.,   | and astonish the rest.        -- Mark Twain
Willowdale, Ontario   | //www.oreilly.com/catalog/samba/author.html
Work: (905) 415-2849 Home: (416) 223-8968 Email: davecb@canada.sun.com