similar to: "the specified network name no longer exists"

I don't know if this is a Samba question or an OS question. I'm working on an embedded project (microcontroller, limited RAM) that reads files from a FreeBSD/Samba (FreeNAS) box using TCP/IP transport on port 445. They're MP3 files so they're several MB at least. If I request 512 or 1024 bytes each time, I get 1024 bytes back from Samba every time. That's good. But, if I

I'm trying to get Samba 3.0.9-2.3 to work under Suse 9.2. This my very first Linux install and I'm a little at sea here. There are so many things that could be wrong I don't know where to start. The Windows machine I'm using as a client has TCP/IP, file/printer sharing, and Client for MS networks. He can't see the linux machine's ("Tolkien") shares, but he

It work's OK but. When I installed a wireless acces point Linksys it does not work. I disabled the firewall in the acces point but with no result. Can anybody help me??? Alejandro G. Schujman AGS Computaci?n y Sistemas contacto@ags.com.ar MSN agschujman@hotmail.com 0341 4219625 Movil 0341 15 5410122

I have a user w/ puzzling error. We have not been able to get a tcpdump or significant samba log, but I'm posting to see if anyone else has seen this. I did find some older posts that point to possible client issues. We're running samba 3.0.25b on RHEL4. The user reports: I am getting an error whenever I want to make a copy of a MS Excel file on my shared network drive: (From

Can anyone tell me what to do about the messages I'm getting, or should I ignore them? I think my SuSE 9.2 box is configured to expect a doman, and there isn't one, just a workgroup. Most things seem to be working ok, except for the messages: tolkien:/var/log # tail messages Apr 1 00:43:05 tolkien nmbd[3962]: Unable to sync browse lists in this workgroup. Apr 1 00:56:28 tolkien

Hi @all, are there any problems known with 3.0.21c and bigger video files (mpg and wmv greater than 700 MB)? Received the information that these files cannot copied from XP to Samba (W2K is okay). Error message is the well known: [2006/03/28 18:03:36, 0] lib/util_sock.c:get_peer_addr(1225)getpeername failed. Error was Transport endpoint is not connected To eleminate network problems the

I just recently installed a second hard drive in my Samba server with the hopes of sharing it with the rest of my home network. It seems like Samba can not get the correct permissions to the drive, however. I have the drive mounted under /media/public, and when I try to map a share directly to it and open the share with a client, I get an NT_STATUS_BAD_NETWORK_NAME error. When I map the

When i try to swap files between disks on my server using samba i get errors: then windows reports "The specified network name is no longer available". Sometimes the copies are fine other times files just wont copy. Hardware checks out fine. Ive even replaced the network cable between server and switch thinking that might be causing the problem. Ive included a ethereal cap of the

I did a make deinstall and a reinstall to upgrade samba from 3.0.9 to 3.0.11 last night at the office i work at and now i get this in the logs. I am sure this has been asswered 100 time on this list but no one can connect to the shared drives. This leave everyone point very angry fingers at me so please help here is the output of the logs. [2005/03/10 12:18:20, 1]

Hi Guys I am running two RHEL boxes, each day I am rsyncing some data from my primary server to my secondary server, the secondary server will be activated in a DR situation. I am rsyncing the entire /home partition. On my primary server there are about 8 samba shares for data that the clients can access all the samba shares point to various sub-directories within /home. My issue is

I have a couple of Linux directories that are being exported via Samba running under SuSE 10.0. On the Windows side, each of them is assigned a (mapped) drive letter. In the "My Computer" list they initially show up as "Disconnected Network Drive". If I attempt to access a file within one of them, the access fails with an indication that the drive does not exist. (For

I have a samba 3.2.3-0.1-1882 server running on Suse SL11.0. It's out of the box, just the way YAST builds it. Pardon the extremely basic level questions here. The intent for this server is basically just file and print services. (It's defined as a BDC, I think, because I didn't do that on a previous install and I couldn't get name service (wins) to work right. Wins works

Samba 3.0.9-2.3 on Suse 9.2 I'm still getting errors copying to my samba box: Often the first attempt to copy to it fails seemingly before it's copied anything. When this happens, there is a zero-length file created with the right name. If I retry the copy immediately and reply Yes to overwrite the zero-length file, it usually proceeds without problems. Many times the copy just goes

This might be a rube question; if so I apologize in advance. Someone asked me to help and I don't have much info, but I have a limited window and have to be forearmed with as much information as possible before I set foot in the door. The guy that asked for help runs a Red Hat 6.2 box with the version of Samba that came with RH 6.2. I asked him what version of Samba it was. He

I have Samba 3.0.9 on SuSE 9.2 on a P-III-500 with only 352mb of RAM. The share I'm copying to is on a SCSI RAID array handled by a Compaq Smart-2/P RAID Controller (rev 04) as identified by lspci. The RAID is all LVM and the share is ReiserFS-- maybe not the best choice for something which is so slow to write to. Anyhow, the problem is that when I copy to the share "movies" it

Well, I WAS puzzled by this persistent error. Then I stumbled onto something and I might have fixed it. It looks like with an XP client, XP might be trying to renegotiate which port to talk (445 or 139) over at the start of every transaction. Whichever one answers first is used for the rest of the transfer. I added this to smb.conf and restarted samba: smb ports = 139 I can't tell if

On 1/14/19 4:02 PM, Duncan Turnbull wrote: > > > Sent from my iPad > > On 15/01/2019, at 10:34 AM, Thomas Peters <TPeters at mcts.org > <mailto:TPeters at mcts.org>> wrote: > >> Duncan: >> >> You may have it right—I took one phone and set the ring time to 60 >> seconds. I now get about 4 rings on that one. >> >> I wonder how I

CentOS Errata and Security Advisory 2009:0161 https://rhn.redhat.com/errata/RHSA-2008-0161.html The following updated files have been uploaded and are currently syncing to the mirrors: i386: cups-1.1.22-0.rc1.9.20.2.el4_6.5.i386.rpm cups-devel-1.1.22-0.rc1.9.20.2.el4_6.5.i386.rpm cups-libs-1.1.22-0.rc1.9.20.2.el4_6.5.i386.rpm src: cups-1.1.22-0.rc1.9.20.2.el4_6.5.src.rpm -------------- next

CentOS Errata and Security Advisory 2009:0161 https://rhn.redhat.com/errata/RHSA-2008-0161.html The following updated files have been uploaded and are currently syncing to the mirrors: i386: cups-1.1.22-0.rc1.9.20.2.el4_6.5.i386.rpm cups-devel-1.1.22-0.rc1.9.20.2.el4_6.5.i386.rpm cups-libs-1.1.22-0.rc1.9.20.2.el4_6.5.i386.rpm src: cups-1.1.22-0.rc1.9.20.2.el4_6.5.src.rpm -------------- next

Switched from Asterisk 1.8 to 13.3.2. Now it logs to /var/log/asterisk/full (good) as well as /var/log/messages (not good). Anyone know why? # grep -v "^;" logger.conf [general] [logfiles] console => notice,warning,error messages => error full => notice,warning,error,debug,verbose,dtmf,fax Thankfully, the .../full logs are rotating properly now (thanks Dale) but we don't