[Samba] The specified network name is no longer available

François Turcotte mrwolf at videotron.ca
Thu Sep 14 16:21:38 GMT 2006


>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 09/10/2006 11:38 AM, François Turcotte escreveu:
>>> Hi,
>>> I got a weird probleme.
>>> I have a fileserver running FreeBSD 6.1 and 2 client running
>>> Windows XP.
>>> Samba version 3.0.23c is installed on FreeBSD server
>>>
>>> when I'm downloading something from the server to any of my
>>> client machine, I got no probleme even with big file, but
>>> when I'm uploading from any client machine to the server if
>>> the file or folder is bigger than 20mo, after a few seconds
>>> of transfert I got this error:
>>>
>>> Cannot copy XXXXXXX: The specified network name is no longer available.
>>>
>>> so since that probleme I don't have the choice of using my
>>> ftp to upload file and folder to my server, it's the only
>>> other way I got.
>>>
>>> anyone got an idea how to fix this?
>>
>> In fact, no. I have seen lots of different types of
>> solutions, ideas and/or recommendations, from netowork problems
>> to total system reinstallation (and I'm not talking about Samba
>> systems). :-)
>>
>> What I know that worked in a lot of situations is
>> described in the following links, I hope this helps:
>>
>> http://www.chicagotech.net/troubleshooting/systemerror64.htm
>> http://reviews.cnet.com/5208-7589-0.html?forumID=62&threadID=19682&messageID=210513
>>
>>
>> And if possible, post your solution on the list using
>> a tag like [SOLVED]. :-)
>>
>>> thanks
>>
>> Kind regards,
>>
>> - --
>
> I just take another computer, install FreeBSD on it with Samba 3.0.23c and 
> test it with transfert of really big file and folder and everything works.
> so the probleme really come from the actual server itself so right now the 
> only thing I think I can do is to format and reinstall my server. I can't 
> find the issue of this probleme, the log on my server and on my test machine 
> are similar, they don't have a big difference.
>
> thanks for your help...

Well.. it's look like it was a one shot luck only cause I reinstall my server and
it's still doing the same probleme the only difference is I can send more data before
crashing. I can send arroung 300mo for mutli file and over 600 for a single file. but not
more than that. This is the log I get right after the probleme.

log.mrwolf
[2006/09/14 12:08:21, 0] printing/print_cups.c:cups_cache_reload(85)
  Unable to connect to CUPS server localhost - Connection refused
[2006/09/14 12:08:21, 0] printing/print_cups.c:cups_cache_reload(85)
  Unable to connect to CUPS server localhost - Connection refused
[2006/09/14 12:10:17, 1] smbd/service.c:close_cnum(1141)
  mrwolf (10.0.1.3) closed connection to service mrwolf
[2006/09/14 12:10:17, 0] lib/util_sock.c:read_data(534)
  read_data: read failure for 4 bytes to client 10.0.1.3. Error = Connection reset by peer
[2006/09/14 12:10:17, 1] smbd/service.c:make_connection_snum(941)
  mrwolf (10.0.1.3) connect to service mrwolf initially as user mrwolf (uid=1003, gid=1002) (pid 831)

log.smbd
[2006/09/14 12:10:17, 0] printing/print_cups.c:cups_cache_reload(85)
  Unable to connect to CUPS server localhost - Connection refused
[2006/09/14 12:10:17, 0] printing/print_cups.c:cups_cache_reload(85)
  Unable to connect to CUPS server localhost - Connection refused

I really need help, thanks


More information about the samba mailing list