similar to: problem with smbclient access to NT4.0 WS share

Hi, I have a small problem with Samba in Debian 2.1 (Slink), kernel 2.0.36 and samba 2.0.5. I have a NT Server and a Linux client. I want to get some files from NT Server to the Linux client. They are in the same network and the IP's are: NT Server - 222.222.222.2 Linux Client - 222.222.222.40 Reading samba docs I discover two small utilities:

Hi: I'm using smbclient version 1.9.15p8 to do some printing from a Solaris 2.3 box to an NT 4.0 share of a remote Win95 box with a printer attached. Unix <-----> NT 4.0 printer share <---WAN---> Win95 printer share (NT is sharing a share...) About a year ago, I wrote a printer script that is used by the lp system to print to the printer using an lp command. As an error check,

Hi I am having some problems retrieving files from a particular share on an NT4.0 server using smbclient. Other files from shares on the same server transfer correctly. I first noticed the problem when my AMANDA backups stopped backing up this particular share just after xmas/new year. Some investigation revealed the problem was always with the same file/group of files. There is no problem

remove

I am getting the following level 5 logging for a Win95 PC under user-level sharing that is sharing to the user "backup" with "full-access". Can anyone help me get logged in via smbclient? shokk:/#> smbclient \\\\EOPORTO-DT\\DEPOT -U BACKUP doing parameter os level = 5 doing parameter domain controller = 137.202.xxx.xxx doing parameter wins proxy = yes doing parameter wins

Hi, I'm trying to share a machine that's on the other side of a gateway. The machine being shared is a Linux (kernel 2.2.1 (RedHat 5.2) and samba 2.0.3), and the box trying to access it is NT4.0 with SP5. It looks something like this ------- --------- ------ |Linux|-----------|Gateway|----------| NT | ------- --------- ------ 192.168.32.72

G'Day everyone, We are new to SAMBA and are having problems with initial configuration of SAMBA Version 1.9.18 on DigitalUnix 4.0B on a Digital AlphaServer 4100. If anyone can help us, we would be greatly appreciative. The installation and compilation all went OK. Following the points in DIAGNOSIS.TXT. Steps 1 to 6 all go OK. Step 7 says... TEST 7: -------

Ok, got a real interesting bug here (if it is a bug). I have 2 computers running samba, one is an HP, and the other is a Linux machine. The network looks something like this: HP9000 Linux Modem P5-200MMX HP-UX 10.20 <--> Gateway <-- PPP link --> Linux 2.0.29 Stable .16 release .17 release, no patches applied Everything is behind a firewall, so all traffic is

Hello to all. I have installed Samba-1.9.18p4 in a BSDI 2.1, operates enough well but have problems when trying to print in any printer connected to a PC with Win95 or WinNT. :-( Before Actualizar Samba-1.9.17 all worked well, there was config the printers as it indicate the file smbprint and could print perfectly in my Epson printer connected a Win95 and the Okidata printer connected WinNT.

Hi all, I am using Amanda and smbtar for backing up Windows machines. However, in addition to the errors I get on open files (which is to be expected), I am getting errors on files that should be fine to access. Here is a snippet from the Amanda log which contains smbclient errors: ? code 0 opening remote file \ebsco-1064\cueanalysisnew.zip (\ebsco-1064\) ? Expected SMBtrans2 response, got

Hello all, I have a printing problem with NT, Samba 1.9.18p8 and Debian Linux 1.3 (Kernel 2.0.32). I defined a printer share, which works fine with Win95, but it does not print with NT 4.0 SP3 and NT 3.51. After installing the "EnablePlainTextPassword" registry entry NT4.0 is able to browse, connect and use a file system share on the printserver, but it can not print to the same

Dear All, I've seen the PRINTER_DRIVER.txt doc on getting the PRINTER$ share set up to automatically add printer drivers to Win95 clients. It explicitly says that the procedure described does not work for NT4.0 clients. I can't find any other documentation on setting up a PRINTER$ share suitable for NT4.0 or NT2000 clients either in the distribution (2.0.5a) or the web site. Is this

I am seeing an odd behavior with NT4.0 SP3 workstations trying to rename files on Samba 1.9.18p2 shares on SunOS 4.1.3 servers. Rename, whether it is run from Explorer, winfile.exe, or command prompt fails with "Access Denied I don't see the problem from Win95 PCs at all, and I don't have the problem with shares from Samba 1.9.18p2 shares on Solaris 2.5.1 servers using identical

The r-base and r-cran packages are now officially a part of the released version of Debian GNU/Linux. They have been part of Debian 2.0 while it was in development. Debian 2.0 was released at 00:00 GMT July 24, 1998. ------- Start of forwarded message ------- Subject: Debian GNU/Linux 2.0 'Hamm' Released From: lohner at debian.org Date: Thu, 23 Jul 1998 20:01:46 -0400

Hi all, I am running SunOS 5.5.1 and am getting all sorts of problems. I am urgently in need of help. My Unix skills are limited. My first problem is starting the daemons. bind failed on port 139 socket_addr=0 (Address already in use) My second problem is the difference in the number of files dumped with either smbtar or smbclient. Here is the command that gives me the most problems. Notice

Hello everybody, I'm using Samba Version 1.9.17p3 on an IRIX 6.2-based workstation and because I still have the same problem with the shares on the PC-box (I'll send my report to samba-bugs too), I need workaround in order to get the smbtar process running. Here's my problem (I hope it's not too long): I can see what's being shared by the Win95 box where I want to make the

While I wait for an answer to my last question, allow me to ask another. When we upgraded a samba server from 2.x to 3.0.0-2mdk using LDAP, we managed to change the domain SID. Instead of fixing the SIDs on the sever, I re-added the hosts to the domain. Although it was a lot of work, it was successful on most of the systems on the network. However, we have one old NT4 box on the network

I've installed Samba 2.2.3a on a Debian Linux machine and am trying to mount a file directory from an NT machine. When I use smbclient as in smbclient //etbodnyk/work -U fciam/bbodnyk it prompts me for a password and I can get to my work directory. When I try to mount the directory using mount -t smbfs -o username=fciam/bbodnyk //etbodnyk/work /mnt I again get prompted for a password but

Hi, I'm having some problems with Samba 1.9.16p11 on a Sun3/60 running NetBSD 1.2. I have a Win95 client and a couple of DOS clients on a single ethernet segment (it's at home :-). I've set up a simple configuration, intention was just to serve files from the Sun to the PC's. Everything works perfectly except authentication from the Win95 client. I can connect to the Samba shares

Hello everyone, I used samba 1.9.x before and everything was fine. The samba server lived in some local network and I could see it from my NTbox as well as from Win95/98 clients. I upgraded to version 2.0.3 and now my server is gone though I use the same smb.conf file which is pretty basic. I can connect to it using the "\\server\share" convention and can also see it when I do a