[Samba] The specified network name is no longer available
I feel stupid even asking, and I have a feeling the solution is something that has been staring me right in the face for hours. I can't seem to access network shared on my samba PDC. I've done this before, and I am using a similar smb.conf file and I am just at the point where I can't get anything else to happen with this thing. My original problem was that I could not get WINXP machines to join the domain and I upgraded my version of Samba in hopes that it was just a fluke. It made things worse. Everytime I navigate to \\server I just receive the error "The specified network name is no longer available". Same thing when I try to join the domain. It does prompt me for a username and password, but beyond that, I have nothing. I need help!! Thank you!! current versions: CentOS 5.2 Samba 3.0.28-1.el5_2.1.x86_64 /etc/samba/smb.conf [global] log file = /var/log/samba/log.%m max log size = 50 workgroup = NMTWebDev netbios name = Server passdb backend = tdbsam security = user add user script = /usr/sbin/useradd -m %u delete user script = /usr/sbin/userdel -r %u add group script = /usr/sbin/groupadd %g delete group script = /usr/sbin/groupdel %g add user to group script = /usr/sbin/usermod -G %g %u add machine script = /usr/sbin/useradd -s /bin/false -d /dev/null -g machines %u # The following specifies the default logon script # Per user logon scripts can be specified in the user # account using pdbedit logon script = logon.bat # This sets the default profile path. # Set per user paths with pdbedit logon drive = U: domain logons = Yes os level = 65 preferred master = Yes domain master = Yes local master = Yes wins support = Yes name resolve order = wins lmhosts hosts bcast dns proxy = Yes socket options = IPTOS_LOWDELAY TCP_NODELAY load printers = Yes printing = cups printcap name = cups # bind interfaces only = yes logon path = \\%L\%U\windowsprofile server string = PDC encrypt passwords = yes null passwords = no # interfaces = lo eth0 map to guest = Never hide unreadable = yes [homes] comment = Home Directory for %u browseable = no valid users = %S read only = no guest ok = no create mask = 0600 directory mask = 0700 inherit permissions = yes [netlogon] path = /var/lib/samba/netlogon guest ok = no read only = yes browseable = no [Public] comment = Public File Share writeable = yes path = /home/public force directory mode = 777 force group = users force create mode = 777 force user = root valid users = @users create mode = 777 directory mode = 777 [www] comment = Website Share writeable = yes path = /www force directory mode = 777 force group = users force create mode = 777 force user = root valid users = @users create mode = 777 directory mode = 777 [printers] comment = All Printers path = /var/spool/samba/print printer = IBMInfoP browseable = No public = Yes guest ok = Yes writable = No printable = Yes [print$] comment = Printer Drivers Share path = /var/lib/samba/drivers write list = @users Greg Koch -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] The specified network name is no longer available
Thanks for the suggestion Andrew. I gave it a try - no difference in my case, unfortunately. (My client is Windows XP SP3, by the way). Anyone, any other ideas? Thanks! Jay -Original Message- From: Colb, Andrew [mailto:[EMAIL PROTECTED] Sent: Thursday, July 24, 2008 4:32 PM To: Jay Libove; samba@lists.samba.org Subject: RE: [Samba] The specified network name is no longer available Jay, We had to remove our "valid users" stanza for our windows 2000 desktops to authenticate correctly with Samba 3. (Samba 3.0.28 on Solaris 10/64; Win2k3/64 DCs; Winbind; Kerberos) The "valid users" stanza apparently works fine for us on Samba 3.0.28 with Vista but not with Win2000 desktop Conversely, the "valid users" stanza works fine for us on Samba 2.x with Win2000 desktop We're in the midst of sorting out the whys and wherefores now that users have their files back. Andy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jay Libove Sent: Thursday, July 24, 2008 3:26 PM To: samba@lists.samba.org Subject: [Samba] The specified network name is no longer available Hello Samba people, I have been successfully using Samba for several years, across many minor versions of Samba across many minor versions of Linux kernel 2.4.x and 2.6.x, against a Windows 2000 and then in the past couple of years 2003 AD Domain. This morning, something broke... Setting the stage: RedHat Fedora based Linux box, FC8, updated over time using 'yum update'..., current kernel is 2.6.25.10-47.fc8 (released just a few days ago). Samba packages: samba-common-3.0.30-0.fc8 samba-client-3.0.30-0.fc8 samba-3.0.30-0.fc8 /etc/samba/smb.conf key configuration lines: (just ask if I've left out any important ones, please) workgroup = FELINESAD2 netbios name = PANTHER8 realm = ad2.felines.org password server = reset6.ad2.felines.org client use spnego = yes all trusted domains = yes security = ADS encrypt passwords = yes local master = no domain master = no preferred master = no domain logons = no wins support = no wins proxy = no dns proxy = no map to guest = never null passwords = no idmap uid = 16777216-33554431 idmap gid = 16777216-33554431 template shell = /bin/false winbind use default domain = no [homes] browseable = no writable = yes public = no valid users = libove, [EMAIL PROTECTED] available = yes In short, it should talk only secure Kerberos protocols and rely on my Domain Controller reset6.ad2.felines.org (the DC for my FELINESAD2 / ad2.felines.org Win2K3 Domain) for authentication. The one actual home share is "libove", which lives on the Linux box at /home/libove This all used to work just fine. Today, it doesn't anymore. Example: C:\>net use h: \\panther8.ad2.felines.org\libove System error 64 has occurred. The specified network name is no longer available. Note that this is different from the common case I found in searching the net for the "... no longer available" error message. That common case was where connecting to the network share worked fine, but large transfers broke in the middle. My case is that I can no longer connect to the network shares on the Samba server at all. What has changed recently? The aforementioned kernel upgrade, care of "yum update" a couple of days ago. And Domain default Policy updates I also made a few days ago, to turn on stronger security of Windows SMB / CIFS requests such as always signing and encrypting: Domain Member: Digitally encrypt of sign secure channel data (always) - Enabled Domain Member: Require strong (Windows 2000 or later) session key - Enabled Microsoft network client: Digitally sign communications (always) - Enabled Microsoft network client: Send unencrypted password to third-party SMB servers - Disabled Microsoft network client: Digitally sign communications (always) - Enabled Network access: Allow anonymous SID/Name translation - Disabled Network access: Do not allow anonymous enumeration of SAM accounts - Enabled Network access: Do not allow anonymous enumeration of SAM accounts and shares - Enabled Network access: Let Everyone permissions apply to anonymous users - Disabled Network security: Do not store LAN Manager hash value on next password change - Enabled Network security: LAN Manager authentication level - Send NTLMv2 response only, and refuse LM & NTLM Network security: Minimum session security for NTLM SSP based (including secure RPC) clients - Require message integrity Require message confidentiality Require NTLMv2 session security Require 128-bit encryption Network security: Minimum session security for NTLM SSP based (including secure RPC) servers - Require message integrity Require message confidentiality Require NTLMv2 session security Require 128-bit encryption The /var/log/samba/log.smb, log., and log. subset
[Samba] The specified network name is no longer available
Hello Samba people, I have been successfully using Samba for several years, across many minor versions of Samba across many minor versions of Linux kernel 2.4.x and 2.6.x, against a Windows 2000 and then in the past couple of years 2003 AD Domain. This morning, something broke... Setting the stage: RedHat Fedora based Linux box, FC8, updated over time using 'yum update'..., current kernel is 2.6.25.10-47.fc8 (released just a few days ago). Samba packages: samba-common-3.0.30-0.fc8 samba-client-3.0.30-0.fc8 samba-3.0.30-0.fc8 /etc/samba/smb.conf key configuration lines: (just ask if I've left out any important ones, please) workgroup = FELINESAD2 netbios name = PANTHER8 realm = ad2.felines.org password server = reset6.ad2.felines.org client use spnego = yes all trusted domains = yes security = ADS encrypt passwords = yes local master = no domain master = no preferred master = no domain logons = no wins support = no wins proxy = no dns proxy = no map to guest = never null passwords = no idmap uid = 16777216-33554431 idmap gid = 16777216-33554431 template shell = /bin/false winbind use default domain = no [homes] browseable = no writable = yes public = no valid users = libove, [EMAIL PROTECTED] available = yes In short, it should talk only secure Kerberos protocols and rely on my Domain Controller reset6.ad2.felines.org (the DC for my FELINESAD2 / ad2.felines.org Win2K3 Domain) for authentication. The one actual home share is "libove", which lives on the Linux box at /home/libove This all used to work just fine. Today, it doesn't anymore. Example: C:\>net use h: \\panther8.ad2.felines.org\libove System error 64 has occurred. The specified network name is no longer available. Note that this is different from the common case I found in searching the net for the "... no longer available" error message. That common case was where connecting to the network share worked fine, but large transfers broke in the middle. My case is that I can no longer connect to the network shares on the Samba server at all. What has changed recently? The aforementioned kernel upgrade, care of "yum update" a couple of days ago. And Domain default Policy updates I also made a few days ago, to turn on stronger security of Windows SMB / CIFS requests such as always signing and encrypting: Domain Member: Digitally encrypt of sign secure channel data (always) - Enabled Domain Member: Require strong (Windows 2000 or later) session key - Enabled Microsoft network client: Digitally sign communications (always) - Enabled Microsoft network client: Send unencrypted password to third-party SMB servers - Disabled Microsoft network client: Digitally sign communications (always) - Enabled Network access: Allow anonymous SID/Name translation - Disabled Network access: Do not allow anonymous enumeration of SAM accounts - Enabled Network access: Do not allow anonymous enumeration of SAM accounts and shares - Enabled Network access: Let Everyone permissions apply to anonymous users - Disabled Network security: Do not store LAN Manager hash value on next password change - Enabled Network security: LAN Manager authentication level - Send NTLMv2 response only, and refuse LM & NTLM Network security: Minimum session security for NTLM SSP based (including secure RPC) clients - Require message integrity Require message confidentiality Require NTLMv2 session security Require 128-bit encryption Network security: Minimum session security for NTLM SSP based (including secure RPC) servers - Require message integrity Require message confidentiality Require NTLMv2 session security Require 128-bit encryption The /var/log/samba/log.smb, log., and log. subsets [ at debug level 3 ] from a session demonstrating the error message above are posted at my web site at http://www.felines.org/Samba_logs.txt because they are too large to include in an email to the Samba mailing list. With apologies for asking for your help before I change back these things, reboot everything, and see if the problem goes away... does any of this ring any bells, has anyone experienced this before and just right away knows the answer? Thanks for your help, Jay Libove, CISSP, CIPP Atlanta, GA, US and Barcelona, Spain -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] The specified network name is no longer available 3.0.25 RHEL4
On Tue, 2008-05-20 at 17:35 +1000, adrian sender wrote: > I have a reproducible intermittent error large site - "The specified > network name is no longer available". https://bugzilla.redhat.com/show_bug.cgi?id=435316 Patches packages about to be released. Simo. -- Simo Sorce Samba Team GPL Compliance Officer <[EMAIL PROTECTED]> Senior Software Engineer at Red Hat Inc. <[EMAIL PROTECTED]> -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] The specified network name is no longer available 3.0.25 RHEL4
I have a reproducible intermittent error large site - "The specified network
name is no longer available".
This happens when copying large files. Below is part of log level 10 output &
strace. Sorry for the long posting. I will probably need to put the loglevel 10
attached to a bugzilla - but thought I would try the lists initially.
RHEL4
samba-3.0.25b-1.el4_6.4
openldap-2.2.13-8.el4_6.4
Sometime using pdbedit -Lv username reports "ldapsam_getgroup: Did not find
group" I am wondering if this could be related to the problem. In debug level
4 something that stands out to me is " string_to_sid: Sid adrians does not
start with 'S-'." This is intermittent.
smb.conf
[global]
unix charset = LOCALE
workgroup = workgroup
netbios aliases = netbios_name
server string = PDC
interfaces = bond0, lo
bind interfaces only = Yes
map to guest = Bad Password
passdb backend = ldapsam:ldap://localhost
username map = /etc/samba/smbusers
log level = 2
syslog = 0
max log size = 0
smb ports = 139
name resolve order = wins bcast hosts
time server = Yes
printcap name = cups
add user script = /opt/IDEALX/sbin/smbldap-useradd -m "%u"
delete user script = /opt/IDEALX/sbin/smbldap-userdel "%u"
add group script = /opt/IDEALX/sbin/smbldap-groupadd -p "%g"
delete group script = /opt/IDEALX/sbin/smbldap-groupdel "%g"
add user to group script = /opt/IDEALX/sbin/smbldap-groupmod -m "%u"
"%g"
delete user from group script = /opt/IDEALX/sbin/smbldap-groupmod -x
"%u" "%g"
set primary group script = /opt/IDEALX/sbin/smbldap-usermod -g "%g" "%u"
add machine script = /opt/IDEALX/sbin/smbldap-useradd -w "%u"
logon script = scripts\dynamic\%U.bat
logon path =
logon drive = H:
logon home = \\localhost\%U
domain logons = Yes
os level = 65
preferred master = Yes
domain master = Yes
wins server = winserver
ldap admin dn = cn=Manager,dc=something,dc=com
ldap group suffix = ou=Groups
ldap idmap suffix = ou=Idmap
ldap machine suffix = ou=People
ldap suffix = dc=something,dc=com
ldap ssl = no
ldap user suffix = ou=People
idmap backend = ldap:ldap://localhost
idmap uid = 4-5
idmap gid = 4-5
invalid users = roots, daemon, bin, sys, adm, uucp, nuucp, lpd, imnadm,
ipsec, lp, snapp,
[netlogon]
comment = Network Logon Service
path = /smbshare/netlogon
admin users = @wheel, "@Domain Admins"
read only = Yes
create mask = 0644
directory mask = 0755
browseable = No
locking = No
[homes]
comment = Home directory for %U
path = /smbshare/users/%S
valid users = %S
browseable = No
samba debug 10
I have the entire debug log; its difficult sifting out what is meaningful.
[2008/05/16 10:49:02, 10] smbd/notify_internal.c:notify_trigger(589)
notify_trigger called action=0x2, filter=0x1,
path=/smbshare/users/adrians/user_v7.exe
[2008/05/16 10:49:02, 3] smbd/sec_ctx.c:pop_sec_ctx(356)
pop_sec_ctx (1410, 513) - sec_ctx_stack_ndx = 0
[2008/05/16 10:49:02, 10] smbd/oplock_linux.c:linux_release_kernel_oplock(191)
linux_release_kernel_oplock: file user_v7.exe, dev = fd08, inode = 21205163
file_id = 55 has kernel oplock state of 1.
[2008/05/16 10:49:02, 10] locking/posix.c:get_windows_lock_ref_count(545)
get_windows_lock_count for file user_v7.exe = 0
[2008/05/16 10:49:02, 10] locking/posix.c:delete_windows_lock_ref_count(559)
delete_windows_lock_ref_count for file user_v7.exe
[2008/05/16 10:49:02, 4] smbd/dosmode.c:set_filetime(604)
set_filetime(user_v7.exe) failed: No such file or directory
[2008/05/16 10:49:02, 2] smbd/close.c:close_normal_file(399)
adrians closed file user_v7.exe (numopen=2) NT_STATUS_OK
Strace Output
utimes("Fedora-9-i386-DVD.iso", {1210211667, 0}) = 0
fcntl64(7, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=688, len=1},
0xbff91fa0) = 0
fcntl64(7, F_SETLKW64, {type=F_UNLCK, whence=SEEK_SET, start=688, len=1},
0xbff91fa0) = 0
geteuid32() = 1410
getuid32() = 1410
geteuid32() = 1410
setresuid32(0, 0, -1) = 0
geteuid32() = 0
kill(11697, SIGUSR1)= 0
--- SIGUSR1 (User defined signal 1) @ 0 (0) ---
write(24, "\n", 1) = 1
sigreturn() = ? (mask now [FPE USR2 PIPE])
setresuid32(1410, 1410, -1) = 0
geteuid32() = 1410
getuid32() = 1410
write(5, "\0\0\0/\377SMB/\0\0\0\0\210\1\310\0\0\0\0\0\0\0\0\0\0\0"..., 51) = 51
fcntl64(7, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, st
[Samba] The specified network name is no longer available
>> -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 XXX: 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-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] The specified network name is no longer available
-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 XXX: 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... -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] The specified network name is no longer available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 François Turcotte wrote: > 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 XXX: The specified network name is no > longer available. I would recommend checking the smbd logs for any panics. cheers, jerry = Samba--- http://www.samba.org Centeris --- http://www.centeris.com "What man is a man who does not make the world better?" --Balian -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFBVAoIR7qMdg1EfYRAm2KAJ9lJH+v6f96VNyEYSIUfllfwVt4SQCfeNUv DQvjuFz3xGTPLrKDNYms7jk= =yQr8 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] The specified network name is no longer available
-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 XXX: 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, - -- Felipe Augusto van de Wiel <[EMAIL PROTECTED]> Coordenadoria de Tecnologia da Informação (CTI) - SEDU/PARANACIDADE http://www.paranacidade.org.br/ Phone: (+55 41 3350 3300) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Debian - http://enigmail.mozdev.org iD8DBQFFBVDCCj65ZxU4gPQRAkz5AKCII6sAfEDZ2QU6WnkwUMRDT0yyaQCffeXi 48g1l1IR5B+JzinDRy+v7N8= =K5HF -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] The specified network name is no longer available
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 XXX: 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? thanks -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] The specified Network Name is no longer available
I have installed samba 3.0.1 on a Solaris 8 server. I can configure new shares using SWAT but when I try to connect to the share over our Windows 2000 network I get the following error: "The specified Network Name is no longer available" I have 5 or 6 other Solaris servers running samba 2.2.2 without any problems and I have tried using some of these smb.conf but that makes no difference. I'm guessing it is only something small that I have overlooked but any help would be much appreciated. Thanks Sean -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] The specified network name is no longer available
I am using Samba version 2.2.8a-0.1.ql.w on Debian 3.0. When copying a file with Win2K/SP2 I get an error message. A file is created but with zero size. If I try again the file is copied properly. I have disabled acl support and oplocks without success. On my 2.2.8a on RedHat 7.2 everything works fine and I have compared the smb.conf. E:\brol>dir 14/06/2003 17:381,474 a.py E:\brol>copy a.py b.py The specified network name is no longer available. 0 file(s) copied. E:\brol>dir 14/06/2003 17:381,474 a.py 02/09/2003 11:340 b.py E:\brol>copy a.py b.py Overwrite b.py? (Yes/No/All): y 1 file(s) copied. E:\brol>dir 14/06/2003 17:381,474 a.py 14/06/2003 17:381,474 b.py -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
