similar to: Not browseable

Hello, We've had serious performance problems loading AutoCAD R14 .dwg files from a VAResearch VArServer 3000 (dual 400MHz PII, Red Hat 5.0, SAMBA 1.9.17p4, 256MB RAM, 36GB RAID5). The problem is that on first access, trying to read the .dwg file is very, very slow -- a 10MB .dwg file loaded from an NT4.0sp3 server using a win95 station using AutoCAD R14 and SoftDesk AutoArchitect takes in

Best Regards, Mike Garver _________________________ Marketing Associate Deerfield.com http://www.deerfield.com/ sales@deerfield.com ---------------------------------------------------------------------- Please download and try our other exciting software products: ---------------------------------------------------------------------- WinGate - http://www.wingate.com/ FTP Voyager -

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I had a working 2.0.6 samba on a RH6.2 system with a 2.4.14 kernel. Clients are all win98/win95 except a win/me laptop. I recently upgraded to 2.2.3a ( from source) and since then I cannot see any of the clients in the "network neighborhood". I cannot even see the workgroup under the "entire network". All clents are

We installed Samba 1.9.16p11 on our Solaris 2.5 Sparc server here and we are having some difficulty getting Windows 95 programs to access the Samba shares. Many of the programs work, and we are dedicated to using Samba, and we have a lot of stuff out there, and we are using it effectively. But we have a few problems with a few programs. One of the possible solutions to this problem is to upgrade

hello, Need advise I've been attempting to get a winXP system added into the network of win95/98 systems and a Samba 2.2.7 server (redhat 7.3) current version of Samba version 2.2.7a-security-rollup-fix the win95/98 systems work fine. the winXP has trouble .. 1) It can not see the samba server OR other systems in the network neighborhoods. (it CAN ping the IPs tho .. ) I've read

Okay, I found a SRPM of samba-1.9.18p3-51 which included smbmount. I did a rpm --rebuild on it on my RH5 PC. Now, apparently I can mount Win95 shares with: smbmount "\\\daisy\c" -c 'mount /daisy' -N This appears to work, but I get an error about not having enough backslashes if I use less than three. When I try to look into the now "mounted" filesystem with ls, I get

Hi, When I use the windows nt or Windows 2000 add printer Wizard (tool) and browse for the printers they are not listed as available. I have to select the Samba-host NETBIOS name before printers become browseable. What I want is to use The "Add printer Wizard", Browse, and find a list or printers available.. \\sambahost\printer1 \\sambahost\printer2 Please find my smb.conf

Hi All, Sorry if this is a re-post, I sent it in to gmane.network.samba.general yesterday and haven't seen it posted yet, so I decided to send it to the list. I am currently running samba 3.0.3 on Fedora Core 2 (Kernel 2.6.6). The samba server is running as the PDC for the domain, with no other servers and a handful of 98 and XP clients. The problem is that Windows XP clients will not show

I have been mounting a Windows machine with no problems whatsoever for the year. Suddenly this afternoon it won't mount any more. No recent changes have been made on the machine. The only thing I've done recently is load and get Thunderbird working. Most things are done as user not root in KDE xterms. My Linux machine is Slackware Linux 10.0. There is an iptables firewall that

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 After having upgraded my W2K clients with SP4, i'm unable to access the [netlogon] share. A look at the <machinename>.log file says: [2003/09/01 16:44:59, 0] smbd/service.c:make_connection(528) make_connection: connection to netlogon denied due to security descriptor. The netlogon share (if set browseable) is visible from clients, in

Hi, I'm experiencing some strange problems with SAMBA. I configured it, it's working but after a while the strangest thing happens. All the Windows machines in the network are unable to see each other in Network neighborhood. If I try to go from a Windows machine to \\OtherMachine\Share it works fine but I can not see anything in the network neighborhood. I'm running Red Hat Linux 6.1

>> Date: Sun, 9 May 1999 16:50:55 -0400 >> From: Wolfgang Albrecht <Wolfgang_Albrecht@compuserve.com> >> To: Samba <Samba@Samba.org> >> Subject: Problem mapping drive names on Win95 >> >> in my Office, I'm trying to replace a Novell-server by a Linux-server. On >> the Novell-server, there is the SYS: volume. On this volume is a

Okay... seems I still cannot get anything working right with this as far getting it to print. Here is the three different files which I would like all to look at and see what I have screwed up since it refuses to print. Here is the setup of the network: HP 5L connected to Win95 - 192.168.0.1 Linux - Zeus - 192.168.0.3 -----------SMB.CONF FILE------------ ; /etc/smb.conf [global] printing =

Hello All I have a Samba 2.2.7 on a RedHat9 system installed as a PDC. Domain logons work fine, I see the linux system in the network neighborhood, but the browsing of tha samba shares is very slow, especially on stepping up in the directory tree. Usually when reaching back to the first level of shares, the flashlight/folder icon appears in windows explorer, and in the top bar

Hi! I'm using Suse 9.0 with cups 1.1.19 and Samba 3.0. I'm trying to share my printer on the network. Testparm runs without errors and I can see my printer in the network neighborhood. So the smb.conf should be fine. But when I try to install the driver with cupsaddsmb I get the following error. zwobot:/usr/sbin # ./cupsaddsmb -U root -a -v Password for root required to access

Hello All, Could someone tell me why I can't see my linux box (nermal) in network neighborhood on my NT Workstation or 95/8 machines here is my smb.conf: #======================= Global Settings ===================================== [global] # netbios name = How machine will appear in network neighborhood netbios name = nermal # workgroup = NT-Domain-Name or Workgroup-Name, eg:

I have a few DOS and Win95 PC's connecting to our Linux 2.0.33 server running Samba v1.9.18p3. This weekend, I am installing a WinNT workstation on the LAN. I can't for the life of me connect the NT station to any of the SAMBA services. It keeps telling me I have the wrong username/password. My setup: Windows NT Workstation SP3 (with the registry set to disable encrypted passwords).

Hello- I am in the process of upgrading our NT 3.51 to NT 4.0 but have run into a problem: We have Samba 1.9.14 running on a UnixWare 2.1 machine. With the NT 3.51 machines the Samba Serveris not visible in the Network Neightborhood, but it can be easily accessed by specifying where one wants to connect. NT 4.0 doesn't seem to have this option. So, 1) can someone tell me HOW to make

I have a user who gets some random disconnects (well not exactly, it is more like her box goes insane randomly...explained better below). I was able to run a wireshark dump on her box and when the trigger action is performed I get a STATUS_INVALID_HANDLE. She is in MS Access an runs a report to trigger it (then she gets about a thousand "disk or network error" dialog boxes). The

I am running Version 1.9.18p7 and I have a win95 machine and an NT machine connecting via ethernet. I have, for security reasons, reorganized my network to reduce outside threats. The network is set up using RFC1918 addressing, and I am using Linux 2.0.33 to transparent proxy outside requests to the net via a dialup PPP session with a dedicated IP address. The global section of my smb.conf